Adjusting registry parameters without careful study may reduce your computer's performance. This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.
For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
The Name value in these keys provides the friendly name for a network connection that is used in the Network Connections folder. Values under these keys are specific to each adapter. Parameters that have a DHCP configured value and a statically configured value may or may not exist. Their existence depends on whether the computer or the adapter is DHCP configured and whether static override values are specified. You must restart the computer for a change to take effect. You can use Registry Editor to modify them.
Generally, these parameters do not exist in the registry. This is also known as the "2MSL" state. According to RFC, the value should be two times the maximum segment lifetime on the network. See RFC for more information. In Microsoft Windows , the default value is seconds.
The default value for the IPv6 stack is seconds. The following parameters are created and modified automatically by the connection properties interface through user-supplied information.
You do not have to configure them directly in the registry. They should never be modified by using Registry Editor. They are listed here for reference only. The Name value in these keys provides the name that is used for a network connection used in the Network Connections folder.
Values under the latter keys are specific to each adapter. If we reuse that information inside of the two minutes, the information is kept for ten minutes. After ten minutes, information is purged form cache. There are several tools that we can use to troubleshoot connectivity problems in Windows XP. The first tool is ipconfig utility. To use ipconfig, first we have to open command prompt.
Then we can type in ipconfig. If we see an IP address of This tool allows us to send small packets to particular machine to see if it will respond back to us. Microsoft recommends the following order for using the PING. First we should test the Loopback Address which is The next address to ping is the local IP address assigned to the machine.
This ensures that the communication to our NIC is possible. If we have done ipconfig, and if it was successful, the ipconfig already did the same two steps that we mentioned. The next step is to check the communication with local hosts. To do that, we can ping the Default Gateway since it is also on the local network.
By pinging Default Gateway we check that our local network is up and running. The next ting to do is to ping remote hosts. In this case we are checking the connectivity between the Default Gateway and the remote host. If this is was not successful, we know that we have problem with our Router. Another tool we can use is tracert trace route. By typing in tracert and then the destination IP address or host name, we can see the route that our computer will take in order to communicate with the destination.
We will see all the Routers that we will use in order to get to destination, and also we will see the the responsiveness from all those particular Routers. We will also be able to see the entire route taken from our computer to the destination computer. Using these tools we can see which Router is causing problems.
In the example above, we can see that our Internet Service Provider is using firewall to prevent pathping requests being made. We can use PING tools to check connectivity with another host.
0コメント