Article ID: 254715 - View products that this article applies to.
This article was previously published under Q254715
Client computers that use Remote Access Services (RAS) or a Virtual Private Network (VPN) to log on to a Windows 2000 domain controller may receive a DNS server address of 127.0.0.1. The clients may be unable to resolve host names to TCP/IP addresses, and they may receive error messages similar to the following examples:
This behavior can occur if the Windows 2000 domain controller did not have any DNS server addresses listed in TCP/IP properties when it was promoted to a domain controller.
To resolve this issue, either follow the server steps to fix this on the server that is running Windows 2000 Routing and Remote Access or use the Client steps if you do not have access to the RRAS server.
On the Server
On the Client
Microsoft Windows NT 4.0 or Windows 2000Statically configure the DNS server addresses in the phone book entry.
Microsoft Windows 95 or Microsoft Windows 98Windows 95/98 clients automatically use the DNS and Windows Internet Naming service (WINS) server addresses that the RAS server assigns, even if the phone book entry at the client computer is configured with statically assigned DNS and WINS server addresses.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/205247/EN-US/ )Overriding Automatic WINS and DNS Server Assignment for RAS/DUN
(https://support.microsoft.com/kb/233169/EN-US/ )Windows 95/98 RAS Client May Disregard the Name Server Addresses
For additional information about configuring a RAS server and client, click the article number below to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/232511/EN-US/ )Client Dialup, Authentication, Browsing Using TCPIP, IPX/SPX
Article ID: 254715 - Last Review: February 28, 2007 - Revision: 4.2