318
Chapter 6
Troubleshooting TCP/IP Connectivity
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 172.16.40.130
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 172.16.40.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :
C:\WINDOWS>
You can review similar information on Windows 95/NT clients and serv-
ers. Verify that the host is configured properly, and then you can eliminate
it as a suspect.
Depending on the traffic type transiting the router, you can check several
different configuration settings. If NetBEUI traffic is running across the
router, make sure that the router is properly configured for transparent or
source-route bridging (SRB). If Novell type 20 NetBIOS is being used, make
sure that the router has the command ipx type-20-propagation. If clients
reside on a network different from the server's network, IP helper addresses
and protocol forwarding must be enabled on the router.
Three elements need to be verified when troubleshooting Windows 95/
NT TCP/IP problems: the host, the router, and the server.
LAN Connectivity Problems
T
roubleshooting LAN connectivity was covered in part through the
discussion of troubleshooting Ethernet and Token Ring problems. Those are
LAN technologies. This section deals with host connectivity in relation to
Cisco routers.
Copyright ©2000 SYBEX , Inc., Alameda, CA
www.sybex.com