This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Newbie/RED phone sytem problem\

We have a 3com V3000 phone system. Our office network is DCHP'ed by the fire wall and has a .1.1 domain. The RED hardware has a .4.1 domain and DCHP's locally.

We have a  3com 3102 handset  that we configured in the office by auto discovery. We took it to the remote office and get the error message "wait for NCP M". System is set up for IP on the Fly.

We have the RED device set for "any" communication each direction with the "in office" system.

The phone is the only thing connected to the VPN device. Angry IP reports no ip address for any of the handsets when scanned from the .1.1 or .4.1 domain. The NBX Telephone configuration>Telephones>IP settings is not reporting an address for the remote phone.  I tried forcing setting an IP address, subnet and gateway at the correct domain to the hand set, but this did not work either.

The odd thing is if I plug in my laptop in the RED that has a soft phone installed, it works fine.  SBS communicates fine too.

Here is a traffic monitor that is going on at the VPN device with only the handset connected:

Proto Source IP Port Destination IP Port Bytes in Pkt in Bytes out Pkt out

udp 0.0.0.0 68 255.255.255.255 67 1146 3 0 0

icmp 192.168.4.1 - 192.168.4.254 - 48 1 0 0 (I am guessing this is the hand set)

Something that is troubling, is the udp 0.0.0.0 response on the packet monitor. Its always paired with the vpn device, 1628 times a day.

Another thing is I cant ping any of the known devices, laptop or handset on the RED from the office. Is this normal?

Any recommendations?

thanks in advance.

This thread was automatically locked due to age.

Parents

0 MikeSwann over 13 years ago

OK, follow up on the system.

After trying Brucekconvervgent's recommendations, the phone system now works fine.

In response to Scott Klassen's question about the NAS, it does appear to be a DNS problem. We could get to the folder we wanted by IP address. We have only one public folder in the NAS, the other is active directory for server back up. I double checked the NAS's settings, its fine and works fine in the internal network. We moved the internal DHCP back to the SBS on recommendation, but it did not help.

Another issue:

I cloned the ASG's mail, web-surfing and DNS network rules to the RED, but it did not allow the PC to go outside of RED's network to locally connect these types of services and the local printers. I wonder if I am misinterpreting the capability of the RED. I could bridge the wireless to the RED, via the PC, but that would make the security entirely dependent on the IPS protection, probably not a good idea.

This has been a great exercise, I learned a lot about networking over the last few weeks.

any comments?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 MikeSwann over 13 years ago

OK, follow up on the system.

After trying Brucekconvervgent's recommendations, the phone system now works fine.

In response to Scott Klassen's question about the NAS, it does appear to be a DNS problem. We could get to the folder we wanted by IP address. We have only one public folder in the NAS, the other is active directory for server back up. I double checked the NAS's settings, its fine and works fine in the internal network. We moved the internal DHCP back to the SBS on recommendation, but it did not help.

Another issue:

I cloned the ASG's mail, web-surfing and DNS network rules to the RED, but it did not allow the PC to go outside of RED's network to locally connect these types of services and the local printers. I wonder if I am misinterpreting the capability of the RED. I could bridge the wireless to the RED, via the PC, but that would make the security entirely dependent on the IPS protection, probably not a good idea.

This has been a great exercise, I learned a lot about networking over the last few weeks.

any comments?
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data