Testing and Trouble Shooting Client Connection

Download Report

Transcript Testing and Trouble Shooting Client Connection

Testing and Trouble Shooting
Client Connection
By Nanda Ganesan, Ph.D.
© Nanda Ganesan, All Rights
Reserved
Possible Causes
• Incorrect IP settings
• DHCP server, DNS server and/or
WINS server not being present on the
network or incorrect settings for the
respective servers
• NIC not working properly
Connection Troubleshooting
• Checking for proper IP address settings
Sequence of Steps
• Invoke web Browser
• Ping localhoast
• Ping gateway
• Ping last router
• Ping a known website
Checking for Connectivity
• Invoke the web browser and attempt
connecting to a website such as
www.msn.com
Entering the Command Mode for
Pinging
• Run cmd from start menu
Pinging the Client
• Ping 127.0.0.1
– Reserved for loop-back test
• Ping localhost
Pinging the Gateway
• Ping the gateway at 130.182.215.25
• Calstatela convention
– .25 is the gateway for a subnet
– Example: for the subnet 130.182.219.0, the
gateway is 130.182.219.25
Pinging the Last Router
• Ping the last router at 130.182.11.254
Testing the Client Connectivity
• Access the network neighborhood
– Click on My Network Places on the
desktop
Nearby Computers
• First check the computers near the
client
– Computers in the same workgroup or
domain often appear on this screen
Troubleshooting Network
Interface Card Drivers
• Check for NIC status
• Most probable cause for incorrect
operation
– The correct driver may not be installed
Upgrading the Driver
• The NIC card properties must be
accessed for upgrading the driver
• There are several ways of accessing the
NIC properties
– Once the properties window is accessed,
the updating procedure remains the same
Location of the New Driver
• Floppy disk or a CD provided by the
NIC vendor
• An updated driver downloaded to a
folder
• Default driver that is provided by
Microsoft
Summary
• Incorrect IP settings
– Ping a machine in the same subnet preferably the
gateway
• DHCP server, DNS server and/or WINS
server not being present on the network or
incorrect settings for the respective servers
– Check the respective addresses
• NIC not working properly
– Check to see whether the
End of Chapter