Help - Search - Members - Calendar
Full Version: Can't Network (ping) Between Vista And Win2003, All Other's Ok
Suggest A Fix PC Support Forums > General Computing > PC Networking and Lan Support
PolishPaul
SOLVED:

Rather embarrasing i should say - i installed vista 64 bit drivers and all is well!

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

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

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

CODE
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):
CODE
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):
CODE

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.
Surfer
what happens if the 2003 box is set to 192.168.1.11 rather than 192.138.1.11? or is 192.138.1.11 a typo?
PolishPaul
QUOTE(Surfer @ Oct 4 2008, 10:17 PM) *

what happens if the 2003 box is set to 192.168.1.11 rather than 192.138.1.11? or is 192.138.1.11 a typo?


Typos corrected . You can also see the correct IP's assigned in the output of ipconfig.
Surfer
firewalls, both have client for ms networks, both have file and printer sharing, both in the same workgroup, both have shares? looks to me like something in vista is blocking access.
PolishPaul
QUOTE(Surfer @ Oct 5 2008, 04:37 AM) *

firewalls, both have client for ms networks, both have file and printer sharing, both in the same workgroup, both have shares? looks to me like something in vista is blocking access.


windows firewalls off on both systems, ms network, firle and printer sharing, workgroup etc is setup, but the problem exists before those apply - i don't even have a network connection, before i can talk about shares etc.

I'm going to attempt a 64 bit OEM driver.
PolishPaul
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 tongue.gif
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.