Microsoft KB Archive/141514

{|
 * width="100%"|

Wrong IP Address Chosen from WINS Server

 * }

Q141514

-

The information in this article applies to:


 * Microsoft Windows 95

-

SYMPTOMS
When a Windows 95-based computer using the Microsoft Client for Microsoft Networks attempts to connect to a multihomed server with the TCP/IP protocol using WINS to find the most accessible IP address to make the connection, an IP address may be chosen that is not in fact the most accessible address.

The Windows 95 client may not connect, or may connect to an IP address that does not have the best performance.

CAUSE
When a server using the TCP/IP protocol is multihomed (meaning that it uses multiple IP addresses), the WINS server lists all of these address for clients to use to connect to the server. The client chooses the address that is the most accessible, typically favoring an address that is local (not on a different subnet).

In Windows 95, there is an error in the algorithm used to determine which of these addresses is the most accessible, so that the client often does not choose the local IP address. Sometimes, the client cannot connect using the chosen address.

RESOLUTION
This issue is resolved by the following updated file for Windows 95, and later versions of this file:

  VNBT.386  version 4.00.954  dated 7/1/96  95,481 bytes A version of this file that resolves this problem is included in the Windows Sockets 2.0 update for Windows 95. For information about obtaining this update, see the following article in the Microsoft Knowledge Base:

"Q182108 Availability of Windows Sockets 2.0 for Windows 95"

STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 95. An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.

This issue is resolved in Microsoft Windows 98.

MORE INFORMATION
A server using the TCP/IP protocol is said to be multihomed if it has multiple network adapters, either on the same network or on separate subnets, each with its own IP address.

Some customers may use systems that bill users for network usage, identifying users by which network they connect from. This problem would create inaccurate billing information for such customers.

For additional information about issues with multi-homed servers and WINS, please see the following article in the Microsoft Knowledge Base:

"Q139985 WINS Client Fails to Reach a Multi-homed Server"

For additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base:

Q168747 Update to Windows 95 TCP/IP to Address Out-of-Band Issue

Q163770 Cannot Log On to Windows NT Domain w/ DNS Name Resolution Only

Q152791 Error Message: No Domain Server Was Available... "Q154434 Err Msg: No Domain Controller Was Available to Validate..."

For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:

"Q161020 Implementing Windows 95 Updates" Keywords : kbnetwork win95

Issue type : kbprb

Technology : kbWin95search kbWin95