To resolve this problem, configure Windows to use smaller ICMP ping packets for fast-link detection. The hotfix described here enables configuring a custom ICMP ping packet size.
Important 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, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
Windows Server 2003
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Windows XP
Service pack information
To resolve this problem, obtain the latest service pack for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Restart requirement
You must restart your computer after you install this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|
Windowsxp-kb816045-v3-x86-symbols-enu.exe | 3.0.0.0 | 660,208 | 05-Jul-2005 | 08:25 | x86 | None | Not Applicable |
Userenv.dll | 5.1.2600.1714 | 683,520 | 05-Jul-2005 | 08:06 | x86 | SP1 | SP1QFE |
Userenv.dll | 5.1.2600.2713 | 723,968 | 05-Jul-2005 | 07:58 | x86 | SP2 | SP2QFE |
Windows 2000
Service pack information
To resolve this problem, obtain the latest service pack for Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
File name | File version | File size | Date | Time | Platform | Service branch |
---|
Basesrv.dll | 5.0.2195.6688 | 42,256 | 08-Apr-2003 | 16:22 | x86 | Not Applicable |
Cmd.exe | 5.0.2195.6656 | 236,304 | 17-Jan-2003 | 16:06 | x86 | Not Applicable |
Gdi32.dll | 5.0.2195.6660 | 233,232 | 08-Apr-2003 | 16:22 | x86 | Not Applicable |
Kernel32.dll | 5.0.2195.6688 | 710,928 | 08-Apr-2003 | 16:22 | x86 | Not Applicable |
Msgina.dll | 5.0.2195.6669 | 333,584 | 08-Apr-2003 | 16:22 | x86 | Not Applicable |
Rdpwd.sys | 5.0.2195.6701 | 90,232 | 08-Apr-2003 | 05:54 | x86 | Not Applicable |
User32.dll | 5.0.2195.6688 | 403,216 | 08-Apr-2003 | 16:22 | x86 | Not Applicable |
Userenv.dll | 5.0.2195.6701 | 386,320 | 08-Apr-2003 | 16:22 | x86 | Not Applicable |
Win32k.sys | 5.0.2195.6697 | 1,717,808 | 05-Apr-2003 | 00:16 | x86 | Not Applicable |
Winlogon.exe | 5.0.2195.6701 | 181,008 | 08-Apr-2003 | 05:48 | x86 | Not Applicable |
Winsrv.dll | 5.0.2195.6699 | 252,176 | 08-Apr-2003 | 16:22 | x86 | Not Applicable |
Rdpwd.sys | 5.0.2195.6701 | 90,200 | 08-Apr-2003 | 05:54 | x86 | Not Applicable |
Kernel32.dll | 5.0.2195.6688 | 710,928 | 08-Apr-2003 | 16:22 | x86 | UNIPROC |
Win32k.sys | 5.0.2195.6697 | 1,717,808 | 08-Apr-2003 | 16:22 | x86 | UNIPROC |
Winsrv.dll | 5.0.2195.6699 | 252,176 | 08-Apr-2003 | 16:22 | x86 | UNIPROC |
Installation notes
After you install this hotfix, you can resolve the symptom that is described in this article by configuring Windows to use a smaller ICMP ping packet size. To manually change the ICMP ping packet size, create the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Value name:
PingBufferSizeValue type: DWORD (decimal)
Value range: 500 - 2048
Default Value: 2048
Note If you do not set this registry subkey or if you set the value out of range, the default ICMP ping packet size of 2048 is used. You can view the packet size in the Userenv.log
file. If your network routers are configured to ignore large ICMP packets, be sure to reduce the PingBufferSize to a smaller value.