Chapter 23: Ten Steps to Networking Nirvana with Windows Server 2003

Windows Server 2003 without a network is like a bicycle without wheels or chips without salsa (our apologies in advance to the unicyclist and fat-free members of our audience).

Because Windows Server 2003 and networking go together like gangbusters, your gang (of users) may try to bust you when the network stops working. Try as you may to avoid it, it does happen from time to time. When the network goes on vacation, but you're still in the office, read over these tips and tricks to get things shipshape again.

Never Overlook the Obvious

The number one cause for failed networks is you guessed it loose connections. Always check a server's network interface cards (NICs) to make sure that the cables are still plugged in or otherwise attached. Also, be sure to check all hubs, the routers, the Integrated Services Digital Network (ISDN) box, the modem, and anywhere else the cables go (such as the client machines).

Networking experts often talk about a troubleshooting pyramid that follows the progression of network capabilities up from the hardware and cables, through the protocol stack, to the applications that request network services. In this analogy, the base of the pyramid is far bigger than the top. This pyramid illustrates that problems are most likely to occur at the physical level of networking. Why? Because that's where the cables and connections are. Go ahead check them again.