Article ID: 239086 - Last Review: December 2, 2005 - Revision: 1.1

Proxy Server 2.0 Cannot Detect Local IP Range with Windows NT 4.0 SP4 Installed

This article was previously published under Q239086
Expand all | Collapse all

SYMPTOMS

When Microsoft Windows NT 4.0 Service Pack 4 (SP4) is installed, Proxy Server 2.0 may not detect the local Internet Protocol (IP) addresses and properly insert them in the local address table (LAT). Also, when constructing the Local Address Table (LAT) in Proxy Server 2.0, selecting "Load known address ranges from all IP interface cards" yields incorrect entries. Specifically, the entries will include the following:

0.0.0.0255.255.255.254
0.0.0.10.0.0.1

Having these entries in the LAT will cause all traffic to be destined for the local network, hence denying the use of WinSock Proxy between the Proxy Client and the Proxy Server.

RESOLUTION

To resolve this problem, obtain and install Microsoft Proxy Server 2.0 Service Pack 1. For additional information about Proxy Server 2.0 Service Pack 1, click the article number below to view the article in the Microsoft Knowledge Base:
238375  (http://support.microsoft.com/kb/238375/EN-US/ ) Proxy Server 2.0 Service Pack 1: List of Fixes

STATUS

Microsoft has confirmed this to be a problem in Proxy Server version 2.0. The problem is corrected by Microsoft Proxy Server 2.0 Service Pack 1.

REFERENCES

For additional information, visit the Microsoft Proxy Web site:
http://www.microsoft.com/isaserver/evaluation/previousversions/default.mspx (http://www.microsoft.com/isaserver/evaluation/previousversions/default.mspx)

APPLIES TO
  • Microsoft Proxy Server 2.0 Standard Edition
Keywords: 
kbbug kbenv kbfix KB239086
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
 

Article Translations