Can't network (ping) between vista and win2003, all other's ok

[PolishPaul]

SOLVED: Can't network (ping) between vista and win2003, all other's ok

SOLVED:

Rather embarrasing i should say - i installed vista 64 bit drivers and all is well! I figured that since everything else works... it couldn't be the drivers.. no no.. it could never be the drivers

--------------------------------------------------

So i'm having the weirdest problem ever and i can't seem to figure out what's wrong.

My problem is that i cannot ping or reach across network from my Vista -> Win2003 or vice versa. I end up with a destination host unreachable.

I have my PC which is dual boot winXP and Vista64 Ultimate. I have another PC which is Windows server2003 R2. Other PC's on the network include my lappy, friend's PC and others. I can ping to and from those PC's from any other PC in the house! The only 2 that are not able to talk to each other is the Vista/2003 boxes. Otherwise there are no problems whatsoever on the network, both the vista and 2003 PC's can reach the internet and the whole network.

The 2 PC's in question are on a basic netgear 5 port switch, which in turn is hooked up to a verizon router.

Here's a summary of my setup:
Router - 192.168.1.1
Vista64 - 192.168.1.4 (dhcp) P-dev.home
Win2003 - 192.168.1.11 (static) Atlas.home

Vista64----NetgearSwitch-----Server2003
                   |
                   |
 	Verizon router

After turning off the firewalls i get:
Pinging from Vista -> 2003: Destination host unreachable
Pinging from 2003 -> Vista: Request time out

I also uninstalled/disabled IPv6 on both systems.

Keep in mind that when the XP install which is on the same exact hardware as Vista works just fine. I've also confirmed that hosts on the switch can ping all PC's in question, as well as hosts that are above the switch (connected directly to verizon router) can do the same.

I've also logged into the router's user interface and can see all hosts as connected, with correct IP etc. Everything looks normal there.

Output from VistaPC (P-dev.home):

C:\Users\pczopowik>ping 192.168.1.11

Pinging 192.168.1.11 with 32 bytes of data:
Reply from 192.168.1.4: Destination host unreachable.
Reply from 192.168.1.4: Destination host unreachable.
Reply from 192.168.1.4: Destination host unreachable.
Reply from 192.168.1.4: Destination host unreachable.

Ping statistics for 192.168.1.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\pczopowik>tracert 192.168.1.11

Tracing route to atlas.home [192.168.1.11]
over a maximum of 30 hops:

  1  P-Dev.home [192.168.1.4]  reports: Destination host unreachable.

Trace complete.

C:\Users\pczopowik>netstat -r
===========================================================================
Interface List
 10 ...00 50 8d d3 7a a8 ...... VIA Networking Velocity Family Gigabit 
Ethernet Adapter
  1 ........................... Software Loopback Interface 1
 11 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
 13 ...00 00 00 00 00 00 00 e0  isatap.home
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1      192.168.1.4     20
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.1.0    255.255.255.0         On-link       192.168.1.4    276
      192.168.1.4  255.255.255.255         On-link       192.168.1.4    276
    192.168.1.255  255.255.255.255         On-link       192.168.1.4    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link       192.168.1.4    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link       192.168.1.4    276
===========================================================================

Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  1    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

C:\Users\pczopowik>ipconfig /all

Windows IP Configuration


   Host Name . . . . . . . . . . . . : P-Dev
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : home

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : home
   Description . . . . . . . . . . . : VIA Networking Velocity Family
 Gigabit Ethernet Adapter
   Physical Address. . . . . . . . . : 00-50-8D-D3-7A-A8
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, October 04, 2008 8:24:54 PM
   Lease Expires . . . . . . . . . . : Sunday, October 05, 2008 8:24:50 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : home
   Description . . . . . . . . . . . : isatap.home
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Output from Server2003 (Atlas):

C:\Documents and Settings\pczopowik>ping 192.168.1.4

Pinging 192.168.1.4 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.4:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\pczopowik>tracert 192.168.1.4

Tracing route to P-Dev.home [192.168.1.4]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *	and so on .. so on...
C:\Documents and Settings\pczopowik>netstat -r

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 17 31 44 e6 ed ...... SiS 900-Based PCI Fast Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.11     20
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
      192.168.1.0    255.255.255.0     192.168.1.11     192.168.1.11     20
     192.168.1.11  255.255.255.255        127.0.0.1        127.0.0.1     20
    192.168.1.255  255.255.255.255     192.168.1.11     192.168.1.11     20
        224.0.0.0        240.0.0.0     192.168.1.11     192.168.1.11     20
  255.255.255.255  255.255.255.255     192.168.1.11     192.168.1.11      1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None

C:\Documents and Settings\pczopowik>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : atlas
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
   Physical Address. . . . . . . . . : 00-17-31-44-E6-ED
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.11
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.1

I was able to mess with the routing table and get varioius other results, but honestly i'm not that familiar with the routing table. Everythign seems to be setup correctly! I can't seem to figure this one out.

 

[alehkcis]

does both machines have the same gateway?im not sure this will be an issue but its worth a try to check if they have the same.

 

[mikesgroovin]

There are a few things that I've seen fix these types of issues. Not all with Vista, but most cases recently have been. Typical culprits:

1) NIC Driver
2) Firewall
3) Winsock
4) IPv6

These are just a few, not in any particular order of course, just as they popped in my head.
Thanks a lot for running an insane amount of diagnostic and detail in the original post. It really paints a picture and gives people a good position to begin from .. not knowing anything about the problem.

Prior to the fix below, try assigning the IP to vista rather than trying to get one from the Verizon device. See if the problem remains. It probably will, but I'd hate to leave that step out.

You've done all of the things that I can think of, save the Winsock repair, so we will get to that now:


Source is from Microsoft at this site

Manual steps to recover from Winsock2 corruption for Windows Vista users
Winsock corruption can cause connectivity problems. To resolve this issue by using Network Diagnostics in Windows Vista, follow these steps:
1. Click "Start", Startand then click Network.
2. Click Network and Sharing Center.
3. In the Network and Sharing Center box, click Diagnose and Repair.
Note You may also access the Network and Sharing Center in Control Panel.

If the Network and Diagnostic tool was unable to find a problem, you can manually repair or reset Winsock.
Manual steps to repair or to reset Winsock for Windows Vista users
1. Click Start, type cmd in the Start Search box, right-click cmd.exe, click Run as administrator, and then press Continue.
2. Type netsh winsock reset at the command prompt, and then press ENTER.

Note If the command is typed incorrectly, you will receive an error message. Type the command again. When the command is completed successfully, a confirmation appears, followed by a new command prompt. Then, go to step 3.
3. Type exit, and then press ENTER.

If that doesn't help then perhaps you should try to reinstall/research drivers for the NIC you are using with Vista64

In my opinion, the problem is isolated to Vista, no question. I sort of have a biased opinion, but the analysis is pretty clear and the fact that the XP instance one the same machine works just fine.

I'm pretty tired, so if I missed something obvious, apologies

See if that helps and let us know.

 

[PolishPaul]

Dr. IP

1) NIC Driver
2) Firewall
3) Winsock
4) IPv6

1. I have the latest (according to windows) but i will search for manufacturer's drives, maybe its a 64 bit issue? The only reason i haven't done so before is everything else worked fine.

2. Turned off windows firewalls (unless vista has some secret ones). Still, i should at least be able to hit the server.

3. Tried, did not help.

4. Uninstalled on server 2003, could only disable in vista. I'm dealing with ipv4 scheme here as far as i know.


alehkcis:

does both machines have the same gateway?

yes they do, you can see it in the output of ipconfig

SOLVED:

Rather embarrasing i should say - i installed vista 64 bit drivers and all is well! I figured that since everything else works... it couldn't be the drivers.. no no.. it could never be the drivers

Dr. IP for the win!

 

[mikesgroovin]

does both machines have the same gateway?im not sure this will be an issue but its worth a try to check if they have the same.

It wouldn't be an issue with ICMP requests within a LAN. You could actually remove the default gateway address completely, still should get the same results.

 

[mikesgroovin]

Dr. IP
SOLVED:

Rather embarrasing i should say - i installed vista 64 bit drivers and all is well! I figured that since everything else works... it couldn't be the drivers.. no no.. it could never be the drivers

Dr. IP for the win!

Thats great, glad you got it working Yea, your box was responding to the ping results as if the ICMP packet never left the box. Not uncommon if your drivers are failing