The Methods to Determine the Name Server Assignments May Be Different for Remote Access Clients with Windows XP (299062)
The information in this article applies to:
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Professional
This article was previously published under Q299062 SYMPTOMS
Prior to Windows XP, remote access client computers obtained their Windows Internet Name Service (WINS) and Domain Name System (DNS) address information by using either of the following two methods:
- WINS and DNS addresses had been manually configured on the remote access client by means of its Transmission Control Protocol/Internet Protocol (TCP/IP) properties.
- WINS and DNS addresses had been obtained by means of Internet Protocol Control Protocol (IPCP). In this scenario, clients had been assigned the same name server addresses that had been configured on the remote access server.
When you attempt to combine the two preceding methods (by configuring either WINS or DNS, which means one of them is not configured), you may not achieve the result that you wanted.
For example, if you manually configure the remote access client with a WINS server address, but you configure the DNS setting to "Obtain an IP address automatically", the remote access client is only configured with a WINS server address after the Point-to-Point Protocol (PPP) negotiation has completed. This result occurs whether or not the remote access server is configured with a valid DNS server address.
CAUSE
This behavior can occur because in versions of Windows prior to Windows XP, if either a WINS or DNS had been manually configured on a remote access client, the IPCP negotiation of name server addresses cannot occur.
RESOLUTION
To resolve this behavior, Windows XP remote access clients are able to negotiate WINS and DNS server addresses independently. For example, a Windows XP remote access client can set WINS addresses manually, and obtain DNS server addresses from the remote access server by means of IPCP.
Modification Type: | Minor | Last Reviewed: | 1/15/2006 |
---|
Keywords: | kbprb KB299062 |
---|
|