Troubleshooting TCP/IP
The methods employed to troubleshoot different TCP/IP network
connectivity problems which depend on
the type of network and the problem. User can manually troubleshoot TCP/IP. The
manual troubleshooting uses various diagnostic utilities.
To manually troubleshoot TCP/IP:
1. Verify the TCP/IP configuration using the Ipconfig command e.g. IP
address, subnet mask, default gateway and DNS address.
2. Check whether the computer can connect to other host computers on
the TCP/IP network using the Ping command.
3. Trace the path of the destination using the Tracert command.
4. Verify the route to the remote computer use the PathPing command.
5. Clear the ARP cache using the Arp command.
6. Ensure that the default gateway is a router and its address is
correct.
(The gateway address must be on the same network as the local
host. If it is not, then the messages from the host computer cannot be
forwarded outside the local network.)
7. Verify the Internet Protocol security in the IP Security Policy
Management snapin window. IPSec policies require secured communication on a
Windows XP Professional-based computer making it difficult to connect to a
remote host. By default IPSec policy management is not configured in all the
PCs as shown in the figure 14.3.
(IP Security Policy Management snap-in can be created using the
Microsoft Management Console (MMC). If you stop the IPSec services and the
problem is solved, the IPSec policy is either blocking the traffic or requires
security for the traffic. Administrator must modify the IPSec policy.)
8. Verify the packet filtering.
9. Verify the TCP/IP connection to a remote computer using the
Netstat command.
10. Examine the routing table
using the route command.
No comments:
Post a Comment