Windows 7 Networking

[kevnich2]

Ok, been wrestling with this issue for a little bit now and can't seem to get around it. Here's my setup: I have a sonicwall firewall that is connected with a T1 through a cisco router. On our XP system's - everything works fine. I recently brought in my Windows 7 laptop and hooked it up and can't get on the internet at all. I know the problem is with our cisco router. The cisco router has interfaces for both our voice and data network. The data interface goes to the WAN port of our sonicwall and the voice goes to a small 5 port switch. The small switch has an uplink cable to both our VOIP phone system as well as to a LAN port on our sonicwall so other remote users VOIP phone works through the internet. If I unplug the voice interface ethernet cable from the 5 port switch - internet on the windows 7 laptop works fine. If I have it plugged in - no internet.

If I try to ping the sonicwall IP - it works fine. If I try to ping an internet IP it says "Reply from 172.16.0.1 - destination host unreachable" - mind you our local subnet is a 192.168.x.x so the windows 7 is able to communicate with a 172.x subnet is beyond me at this point. I have confirmed this on other Windows 7 computers - all have the same result. From the windows 7 I can also ping directly the 172.16.0.1 and it replies back. If I unplug the cisco router's voice interface, the pings time out. If I do a traceroute to 172.16.0.1 - the first hop is the sonicwall also.

I have two questions - how am I able to access the 172.x subnet from our local 192.x subnet? Secondly - what configuration error do I have in the cisco router that could be causing this?

 

[drebo]

More info is needed. What is the outside subnet of the SonicWall?

Can you paste the relevant portions of the Cisco's config (sh ip route, interface configs, and ACLs that are applied to interfaces)? What does a traceroute to 4.2.2.1 look like from a working machine? What's it look like from a non-working machine?

My main recommendation would be to get rid of the SonicWall. The Cisco can do everything it can, but better. You also wouldn't need to employ hokey connections to get VoIP traffic in from the outside. SonicWalls are known to have issues with VoIP, and your setup is needlessly complicated by trying to circumvent it.

 

[Emulex]

disable ipv6 on any win7 box before plugging it into the network
disable flow control on any win7 box before plugging it into the network.

^^ 99% of the issues

 

[kevnich2]

Emulex - thanks, I'll try that when I get to the office tomorrow and see if that helps any.

 

[kevnich2]

Emulex - just an FYI - fixed this issue this morning. It was a config issue in our cisco router.