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 cannot ping its own IP address

There is a fundimental networking problem on the Linux box, unrelated to the Windows clients, wiring, hubs, etc. As a matter of fact, a properly configured Linux server can ping itself with its network cable disconnected. Although it is possible there may be additional problems, this basic problem must be solved before others can be attacked.

To save time, unless rebooting the server presents a large problem to the user base, power the machine off for 15 seconds, then back on. See if now you can ping the server's IP address from the server's command line. If so, you have an event which may not happen again, or an intermittent to watch out for. However, if rebooting doesn't do the trick, continue.

Start by editing all the files in /root/setserv.pl (this is a Troubleshooters.Com proprietary file). Make sure all network addresses, netmasks, host addresses are compatible with each other.

Make sure the network's running. Get into the /etc/rc.d/rc3.d directory, and do these 2 commands:
./S10network stop
./S10network start
On the start command, notice any error messages. These are good clues. After starting the network, try pinging again. If the ping succeeds, you need to find out why networking wasn't enabled at boot time, or if it was, what killed it.

If nothing is obvious, you'll need to get off road and make your own diagnostic tests. This concludes
this branch of the predefined diagnostic.