Article ID: 311218
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Professional
This article was previously published under Q311218
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
You may experience a problem after you change the binding order for [Remote Access connections] by moving it to the top of the connections list. You would do so in the Advanced Settings dialog box of the Network and Dial-up Connections tool. After you do so, network utilities that resolve host names by using the Domain Name Service (DNS) server that is associated with a dial-up networking connection, do not default to the DNS server that is associated with the dial-up connection. NSLookup is an example of a network utility that resolves host names by using the Domain Name Service (DNS) server that is associated with a dial-up networking connection.
This symptom occurs although you expect the network utility to use as the default DNS server that is associated with the network device that has the highest binding order in the list of network connections.
Note This symptom may also occur with Virtual Private Networking (VPN) connections. A client computer may not use the DNS server from a VPN connection if the default gateway is set to the remote connection.
WORKAROUND
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To work around this problem, edit the registry to move the Remote Access Services connection to the top of the binding order:
- Click Start, click Run, type regedit32 in the Open box, and then click OK.
- Click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage - In the right pane, double-click Bind.
- In the Value data box, select the "\Device\NdisWanIp" item, press CTRL+X, click the top of the list of devices, and then press CTRL+V.
- Click OK, and then quit Registry Editor.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Keywords: kbprb KB311218
