Intro
One of the components of the Internet connection on your computer is a built-in set of instructions called TCP/IP. TCP/IP can sometimes become damaged or corrupted. If you cannot connect to the Internet and you have tried all other methods to resolve the problem, TCP/IP might be causing it.
Because TCP/IP is a core component of Windows, you cannot remove it. However, you can reset TCP/IP to its original state by using the NetShell utility (netsh).
This article describes two ways to reset TCP/IP. You must be logged on to the computer as an administrator. Use a manual method to reset TCP/IP for Windows XP
The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually:
- To open a command prompt, click Start and then click Run. Copy and paste (or type) the following command in the Open box and then press ENTER:cmd
- At the command prompt, copy and paste (or type) the following command and then press ENTER:netsh int ip reset c:\resetlog.txtNote If you do not want to specify a directory path for the log file, use the following command:netsh int ip reset resetlog.txt
- Reboot the computer.
The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually:
- To open a command prompt, click Start and then type CMD in the Search programs and files.
- Right-click CMD.exe icon in Programs and choose Run as administrator.
- When the User Account Control box pop up, click Yes.
- At the command prompt, copy and paste (or type) the following command and then press ENTER:netsh int ip reset c:\resetlog.txtNote If you do not want to specify a directory path for the log file, use the following command:netsh int ip reset resetlog.txt
- Reboot the computer.
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
SYSTEM\CurrentControlSet\Services\DHCP\Parameters\
The first example, c:\resetlog.txt, creates a path where the log will reside. The second example, resetlog.txt, creates the log file in the current directory. In either case, if the specified log file already exists, the new log will be appended to the end of the existing file.
811259 How to determine and recover from Winsock2 corruption in Windows Server 2003, in Windows XP, and in Windows Vista
No comments:
Post a Comment