Predefined Diagnostic: Linux Server with Windows Clients

Copyright (C) 1998 by Steve Litt. All rights reserved.


Path Traveled

  • Start
    • Server does not hang during boot
      • All other Windows clients display this symptom, or there are no other Windows Clients, or it's too difficult to test the other Windows clients
        • The Linux server can ping its own address from its console's command line
          • The Windows Client CANNOT ping the Linux server's IP address

Networking on the Linux server is working just fine, but the Windows machine cannot see it. Either there's a problem in the physical wiring (cables, hubs, etc), the subnetting (IP anded with netmask on each machine should yield an identical result), or the basic networking capability of the Windows machine. To rule out the latter, from the command line of the Windows machine, ping the IP address of the Windows machine. Or, if the Windows machine is assigned an IP address by Wins via dhcp, ping the Windows machine name as shown in the DNS configuration tab of the TCP/IP properties of the networking setup.


UNUSUAL FEATURE NOTE: The name to ping is the one in the DNS configuration tab of the TCP/IP properties of the networking setup, not the one in the Windows networking configuration, Identification tab, Computer name field. The latter has function in dhcp, and might have other function, but it is not self-pinging. It's always best to have these two fields match, to prevent any possible subtle problems. However, to my knowledge, Windows will not tell you about a mismatch in these two fields.
Can the Windows machine ping itself?