Microsoft KB Archive/816533

= Firewall Clients Cannot Connect to the Internet After You Upgrade an ISA Server to Windows Server 2003 =

Article ID: 816533

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Internet Security and Acceleration Server 2000 Service Pack 1
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
After you upgrade your Microsoft Windows 2000-based server that is running Microsoft Internet Security and Acceleration (ISA) Server 2000 Service Pack 1 (SP1) to Windows Server 2003, client computers that are running the Microsoft Firewall Client program can no longer connect to the Internet.

If you update the ISA server in the Microsoft Firewall Client program, the server is updated successfully, but the client computer still cannot connect to the Internet.



CAUSE
This problem occurs because the W3proxy service stops responding while it initializes the listening sockets.



RESOLUTION
To resolve this problem, disable backlog monitoring in Windows Server 2003. To do so, follow these steps. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.  Click Start, click Run, type regedit, and then click OK. Locate the following registry subkey:

 Right-click the Parameters subkey, point to New, and then click DWORD Value. In the New Value #1 box, type DisableBacklogMonitor, and then press ENTER. Right-click DisableBacklogMonitor, and then click Modify. In the Value data box, type 1 (one), and then click OK.</li> Quit Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in Windows Server 2003.

Keywords: kbpending kbbug KB816533

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.