Cannot Change the Binding Order for Remote Access Connections
This article was previously published under Q311218
This article has been archived. It is offered "as is" and will no longer be updated.
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.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in WindowsTo 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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Article ID: 311218 - Last Review: 12/07/2015 08:04:52 - Revision: 3.5
Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows XP Home Edition, Microsoft Windows XP Professional
- kbnosurvey kbarchive kbprb KB311218