Microsoft KB Archive/157944

{|
 * width="100%"|

Domain Name Service in DUN Connection Does Not Work

 * }

Q157944

-

The information in this article applies to:


 * Microsoft Windows 95

-

SYMPTOMS
When multiple DNS (Domain Name Service) servers are configured on a single workstation with one DNS server for a Dial-Up Networking connection and another DNS server for a primary network adapter, the (DNS) configuration for the Dial-Up Networking connection does not work.

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

  WSOCK32.DLL  version 4.00.952  dated 9/26/96  67,072 bytes A version of this file which resolves this problem is included in the Windows Sockets 2.0 update for Windows 95. For information on 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
If you have a DNS server configured in the Dial-Up Networking connection in addition to a DNS server configured for the TCP/IP protocol in Network properties, only the configuration in Network properties is used. The setting in the Dial-Up Networking connection is ignored.

With the updated Wsock32.dll file installed, the DNS settings in Network properties are used when you are communicating over the LAN adapter, and the DNS settings in the Dial-Up Networking connection are used for that dial-up connection.

Additional Information
This fix has also been reported to resolve the following problem:

When a Token Ring and an Ethernet card are installed and the Ethernet card is not connected to a network, some IP packets (most commonly DNS requests on UDP port 53) are sent out the Token Ring interface with an IP source address from the Ethernet card. The source MAC address is that of the Token Ring card, but the source IP address is that of the Ethernet card.

This update changes the way Windows is resolving names, in that it no longer sends DNS requests (destination port 53) from NetBIOS (source port 137). It either uses DNS as normal or NetBIOS as configured (WINS, broadcasts, and so on). No incorrect source IP addresses have been seen with the patch applied.

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

Q170619 Windows 95 ServiceProvider Priority Values Not Applied

Q169035 Windows 95 WinSock Update to Improve Multihoming Support

Q163329 Fatal Exception 0E in WSIPX Using Windows Sockets Program

Q157930 Multiple DNS Server Addresses Not Assigned Properly with DHCP

Q141211 Memory Leak with Multithreaded Winsock Programs For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:

"Q161020 Implementing Windows 95 Updates" Additional query words: dun connectoid

Keywords : kbnetwork win95

Issue type :

Technology : kbWin95search kbWin95