Diagnostics and Troubleshooting6-98000-A2-GB26-10 January 1999Client Cannot Reach Service NodeTable 6-4. Client-to-Service Node SegmentLayer SolutionLayer 1 –Physical1. Make sure the PWR LED on the front of the Service Node is lit. Use onlythe power adapter shipped with the unit.2. To verify connection to the client, make sure the ETHERNET LED on thefront of the Service Node is lit.3. Make sure there is a physical connection between the Service Node andthe Network Interface Card (NIC). If there is a LINK LED on the NICcard, make sure it is lit.4. If there is a hub, check its cables and LEDs.5. Make sure the correct type of cable is being used between the client andthe Service Node. A crossover cable should be used if the client is notconnected to a LAN hub.6. Make sure the NIC and drivers are correctly installed.7. Make sure the correct Service Node firmware is being used.Layer 2 –Network1. If static addressing is used, make sure the client has its correct IPaddress and subnet mask by entering the following:– Windows 95: winipcfg– Windows NT: ipconfig/allFor other operating systems, use help or see the appropriate manual.2. Restart the client after a static IP address has been added or changed.3. Make sure the client can Ping its own IP address. This confirms the IPaddress was successfully accepted by the computer.4. Check the PC’s default gateway to make sure it is functioning properly.1. If dynamic addressing is being used and the client cannot get an IPaddress from the Dynamic Host Configuration Protocol (DHCP) server,statically configure an IP address and then verify that the client can Pingthe DHCP server.2. After the client reaches the server, remove the IP address and return thesystem to dynamic (DHCP) addressing.Make sure there are 32 or fewer DHCP users active on the port at anygiven time. Only 32 users are entered into the host table.If the problem persists after the above items are checked, the client-to-servicenode segment of the network is functional.