none
Cannot ping a file server from a Windows 7 machine or Windows Server 2008 R2 but can ping it from XP or Windows Server 2003

    Question

  • In our network that has XP with Windows Server 2003 or Server 2003R2 we can ping from any xp machine to any server including our file server that is a Win 2k3 R2 server. We are trying Windows 7 and have found that we can ping succesfully any server except the file server. We have try to ping this file server from different Windows 7 machines and also from a Windows Server 2008 R2 and they all fail.

    Strangely the first ping generally will sucess and the rest will fail. We have try ping to the IP address or Servername with the same results. We can ping the Windows XP or Windows 7 machines between them without problems. We have try to ping with the firewall in off without success. Windows XP pings the same file server without problems or any other server 2003. From the file server we can ping any Win 7 machine sucessfully.

    I will appreciate any suggestion or ideas to solve this.
    Tuesday, February 09, 2010 12:35 AM

Answers

All replies

  • Please post the results of ipconfig /all from one of the affected computers and from the domain controller that is the DNS server.

    Thanks

    Kerry Brown MS-MVP - Windows Desktop Experience
    Tuesday, February 09, 2010 1:47 AM
  • Ipconfig/all results:

    Domain & DNS server:
    Windows IP Configuration

       Host Name . . . . . . . . . . . . : xxxxdc2
       Primary Dns Suffix  . . . . . . . : abc.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : abc.com

    Ethernet adapter Local Area Connection 3:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC7781 Gigabit Server Adapter
       Physical Address. . . . . . . . . : 00-11-0A-9E-18-2F
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 172.22.200.52
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 172.22.202.250
       DNS Servers . . . . . . . . . . . : 172.22.200.51
                                           172.21.200.11
                                           172.16.200.11
                                           172.22.200.52
       Primary WINS Server . . . . . . . : 172.21.200.11
       Secondary WINS Server . . . . . . : 172.22.200.51


    Windows 7 machine:
    Windows IP Configuration

       Host Name . . . . . . . . . . . . : xxxx0295
       Primary Dns Suffix  . . . . . . . : abc.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : abc.com

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : abc.com
       Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connecti
    on
       Physical Address. . . . . . . . . : 18-A9-05-49-5C-E1
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::149:36b8:3e6:e293%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 172.22.2.133(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Lease Obtained. . . . . . . . . . : Monday, February 08, 2010 11:45:42 AM
       Lease Expires . . . . . . . . . . : Thursday, February 11, 2010 8:00:35 PM
       Default Gateway . . . . . . . . . : 172.22.202.250
       DHCP Server . . . . . . . . . . . : 172.22.200.51
       DHCPv6 IAID . . . . . . . . . . . : 236497157
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-FA-CE-20-18-A9-05-49-5C-E1

       DNS Servers . . . . . . . . . . . : 172.22.200.51
                                           172.22.200.52
                                           172.21.200.11
                                           172.16.200.11
       Primary WINS Server . . . . . . . : 172.22.200.51
       Secondary WINS Server . . . . . . : 172.21.200.11
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tuesday, February 09, 2010 2:09 AM
  • What are the results of

    nslookup fileserver

    where fileserver = the name of the fileserver you can't ping? Even though you can't ping the file server can you access shares on it?

    Kerry Brown MS-MVP - Windows Desktop Experience
    Tuesday, February 09, 2010 3:28 PM
  • The nslookup gives the correct answer, that is the IP number assigned to this server.

    We cannot access any shares in the fileserver or do a remote connection to it.
    Tuesday, February 09, 2010 5:57 PM
  • I was more interested in what DNS server gave you the answer. I guess as long as you get the correct result it's not that important. I was thinking this may be a DNS problem but it appears that's not the issue.

    Have you tried a Vista or Server 2008 computer. I wonder if the problem is something to do with the new network features introduced with Vista and Server 2008. Try these settings on a workstation.

    http://silverstr.ufies.org/blog/archives/001035.html

    If any of them fix the issue I'd suspect a switch or router that doesn't support this or possibly the NIC on the server. Broadcom NICs in particular seem to have problems. If the server has a broadcom NIC it's very important to make sure you use the latest driver and there's a registry change you may need.

    http://forums.techarena.in/server-networking/748637.htm

    If the file server is in a different domain it may also be the way the DNS search suffix list is used.

    http://blogs.technet.com/networking/archive/2009/04/16/dns-client-name-resolution-behavior-in-windows-vista-vs-windows-xp.aspx


    Kerry Brown MS-MVP - Windows Desktop Experience
    • Marked as answer by Novak Wu Monday, February 15, 2010 7:23 AM
    Wednesday, February 10, 2010 12:28 AM
  • Sorry for the big delay in replying but I was on vacations without access to email or web.

    We have tried a to ping this file server from a Windows 2008 R2 server with exactly the same results.

    We have tried the recommended settings without sucess, any connection to this server fails.

    We have updated this file server with all the know patches from Windows and HP with the same results. We also replaced the network cable, change switch port and put a new network card and always the ping and any other connection fails.

    The file server and the Windows 7 machines are in the same domain and in the same location.

    All ideas or suggestions are welcome.
    Thursday, February 25, 2010 5:44 PM
  • I having the same similar issue.  Here is what is going on.

    Server A = Windows 2003 R2 64bit, DC, DNS, DHCP.  10.1.1.29 (real machine has all FSMO roles)
    Server B = Windows 2003 R2 64bit, DC, DNS, DHCP, 10.1.1.28 (vmware)
    Server C = Windows 2008 R2 64bit, member server 10.1.1.33 (vmware)
    Client X = Windows 7 Pro, 32bit, in the domain, on the 10.1.1.x subnet for testing purposes. (parallels VM on a Mac)

    I went to promote Server C to a domain controller.  I got part of the way through and then got a RID master offline error (RID master is 10.1.1.29), followed by a RPC error.

    So I pinged 10.1.1.29 from Server C and I got 1 reply and then 3 failures?  I tried to RDP to the IP 10.1.1.29 and that failed.  From Server C I tried to ping 10.1.1.28 and it works?  RDP works as well.

    Pinging from Client X to 10.1.1.29 fails as well.  All other Windows 2003 servers on 10.1.1.x can ping 10.1.1.29.  Only Windows 2008 R2 and Windows 7 cant ping it?  Looking at their ARP cache they are getting a bogus Mac (mac from our Cisco ASA on the same subnet).  I can clear the arp cache arp -d on Server C and then ping from 10.1.1.29 to Server C and then the arp cache on Server C is correct and pings from it to 10.1.1.29 work.

    If I move Server C or Client X to say our 10.3.x.x subnet and force the ping through a router is works fine.

    So any Windows 7/2008R2 client on the same subnet cant ping 10.1.1.29.  Or can once then fail.  I have searched Google and there are lots of the same thing out there.  Single ping then failure.  It seems like something in Windows 7/2008R2 is messed up when on the same subnet.....sometimes.
    Thursday, February 25, 2010 10:35 PM
  • Similar to report here I'm afraid.  Issue was highlighted when I tried to VNC from an XP machine to one of my Windows 7 PCs at home.

    Internet access from Windows 7 64bit machine works just fine but local network access seems sporadic.

    e.g. XP machine is 192.168.123.53 - if I try to ping it from the Windows 7 box (192.168.123.62) I get the following :

    Pinging 192.168.123.53 with 32 bytes of data:
    Reply from 192.168.123.62: Destination host unreachable.

    I have a NAS at 192.168.123.101 and that pings back just fine.

    Everything was working a week or so ago on two windows 7 machines.  Today it's not working.

    Is it anything to do with the routing table?

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0  192.168.123.254   192.168.123.62    281
            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.123.0    255.255.255.0         On-link    192.168.123.62    281
       192.168.123.62  255.255.255.255         On-link    192.168.123.62    281
      192.168.123.255  255.255.255.255         On-link    192.168.123.62    281
            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.123.62    281
      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.123.62    281
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
              0.0.0.0          0.0.0.0  192.168.123.254  Default

    IP Config :
    Windows 7 Source machine 192.168.123.62
    Gateway / BT Router 192.168.123.254
    NAS box: 192.168.123.101
    XP machine: 192.168.123.53

    Have also tried switching off firewalls on both XP and Windows 7 machines to no avail

    Help! :)

    Friday, February 26, 2010 3:19 PM
  •  

    We are having the same issue. We have just purchased 10 new Lenovo desktops with Win7 pro.

    After adding the machine to the AD Domain, we cannot access our Mail server (2003 Server R2 SP2 Standard).The Mail Server NIC is an Intel 82566DM-2.

    NSLookup resolves to the machine IP,  and Ping to machine name and IP returns 1 response and then no connection.

    interestingly, the machine browses the WEB fine, except it will not connect to the outside IP of the mail server either, including WEBMAIL address and port or the WEBADMIN address or port.  All of these connections work on our XP Pro machines(internally and externally) .

    The route Print looks the same as above.. the Lenovo's have Marvell Yukon 88E8057 Nics.

    Another note: One of the 10 Lenovo's came preloaded with XP pro (downgrade) and it connects correctly.

    From the Win 7 machine, I can ping our domain controller (2003 Server R2 SP2 Standard). and 2nd DC (2003 Server R2 SP2 Standard). and browse our public directories, on the File Server (2003 Server R2 SP2 Standard).

    Has anyone found a solution?
    Friday, April 30, 2010 5:55 PM