troubleshoot+a+connection+with+TCPIP+tools

http://support.microsoft.com/kb/314067


 * Basic tools**
 * **Network Diagnostics in Help and Support**
 * **Network Connections folder**
 * **IPConfig command**
 * **Ping command**


 * Advanced tools**


 * **Hostname command**
 * **Nbtstat command**
 * **PathPing command**
 * **Route command**
 * **Tracert command**


 * Windows XP Professional tools**


 * **Event viewer**
 * **Computer Management**


 * Automated troubleshooting**

For most issues that involve Internet connectivity, start by using the Network Diagnostics tool to identify the source of the issue. To use Network Diagnostics, follow these steps: You can either use that information to resolve the issue or you can provide the information to a network support professional for help. If you compare the tests that failed with the documentation in the Manual Troubleshooting section later in this article, you may be able to determine the source of the issue. To interpret the results for TCP/IP, expand the Network Adapters section of the results, and then expand the network adapter that failed the testing.
 * 1. || Click **Start**, and then click **Help and Support**. ||
 * 2. || Click the link to **Use Tools to view your computer information and diagnose problems**, and then click **Network Diagnostics** in the list on the left. ||
 * 3. || When you click **Scan your system**, Network Diagnostics gathers configuration information and performs automated troubleshooting of the network connection. ||
 * 4. || When the process is completed, look for any items that are marked "FAILED" in red, expand those categories, and then view the additional details about what the testing showed. ||

You can also start the Network Diagnostics interface directly by using the following command: netsh diag gui


 * Manual troubleshooting**

Use the Ping tool to test your connectivity

Type in command Prompt //ping// then pick a web site like //ping creepcolony.com// Then you will get ether
 * H:\>ping creepcolony.com

Pinging creepcolony.com [75.126.140.58] with 32 bytes of data:

Reply from 75.126.140.58: bytes=32 time=36ms TTL=50 Reply from 75.126.140.58: bytes=32 time=53ms TTL=50 Reply from 75.126.140.58: bytes=32 time=38ms TTL=50 Reply from 75.126.140.58: bytes=32 time=49ms TTL=50

Ping statistics for 75.126.140.58: Packets: Sent 4, Received 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum 36ms, Maximum 53ms, Average = 44ms

H:\>**

or
 * H:\>ping shirt.woot.com

Pinging shirt.woot.com [66.165.70.8] with 32 bytes of data:

Request timed out. Request timed out. Request timed out. Request timed out.

Ping statistics for 66.165.70.8: Packets: Sent 4, Received 0, Lost = 4 (100% loss),**


 * H:\>**