Some TCP/IP parameters in the registry are changed to incorrect values when you use the NETSH command to modify TCP/IP global parameters on a computer that is running Windows Server 2008 or Windows Vista
When you use the netsh command to modify TCP/IP global parameters on a computer that is running Windows Server 2008 or Windows Vista, some TCP/IP parameters in the registry are changed to incorrect values.
Note: These parameters are saved in the location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
This issue may affect the following items:
- DisableTaskOffload
- EnablePMTUBHDetect
- EnablePMTUDiscovery
- KeepAliveInterval
- KeepAliveTime
- Tcp1323Opts
- TcpFinWait2Delay
- TcpMaxDataRetransmissions
- TcpTimedWaitDelay
- TcpUseRFC1122UrgentPointer
For example, you run the following command to change a TCP/IP global parameter:
netsh in tcp set global autotuninglevel=normal
After you run the command, the values of some unrelated settings below are changed to 0xFFFFFFFF:
- KeepAliveInterval
- KeepAliveTime
- TcpMaxDataRetransmissions
- TcpTimedWaitDelay
For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB967224.

Start
About
FAQ
Blogroll
Shop
Tips and Tricks
Windows Updates
Hotfixes
Fix It
Keyboard Shortcuts
Vista's Services
Vista's Commands
Product Reviews
Glossary
Videos
Web Links

Comments
There are no comments yet...Come on, share your thoughts!
Leave a Comment