Troubleshooting Procedures
191
SMCD3GNV Wireless Cable Modem Gateway User Manual
Unable to Access Networked Devices
If you are on a network, but cannot connect to any resources on the network:
1. The Ethernet cable may be worn. Replace the cable if it is worn.
2. The Ethernet cable may not be firmly connected at both ends. Secure the cable at both
ends. Often, just reseating the cable into a connector is all that is required.
3. The port on the Gateway may be bad. Plug the network cable into a different port on the
Gateway.
4. The NIC may be bad or the cable connected to the NIC may be the wrong kind of network
cable (for example, you may be using a straight-through cable when a crossover cable is
required). If you have another NIC available, try using it instead of the one currently used.
5. Ping the IP address of other computers and devices on your network.
6. For Windows operating systems:
– Try connecting to a computer on the network using
Start \ Run
and enter
\\PCname
,
where
PCname
is the name of the computer you want to connect to.
– Add the computer and its IP address to the
LMHOSTS
file. This is a text file that
resides in the
Windows\System32\drivers\etc
directory (for Windows2000 or
XP) and has the format
IP_Address Computer_Name
.
Tip:
Browsing is fairly complicated issue and has a lot of places for failure. If you need to
have resources available, create shortcuts on your desktop instead.
Using the Ping Utility to Troubleshoot
You can use your computer’s ping utility to test the path from the computer to the Gateway
and from your computer to the Internet.
Testing the Path from a Computer to the Gateway
You can ping the Gateway to verify that the LAN path from your computer to the Gateway is
set up correctly. To ping the Gateway from a Windows computer:
1. From the Windows task bar, click
Start
and select Run
.
2. In the
Open
field, type
ping
followed by the IP address of the Gateway.
3. Click
OK
. A message similar to the following appears (in this example,
192.168.0.1
is the
IP address entered as part of the
ping
command):
Pinging 192.168.0.1 with 32 bytes of data
If the destination IP address was contacted successfully, a message similar to the following
appears: