L
louislee
this problem have bug me for past 2 years... and i have search and
search and never find a solution...
solution that is a temp fix is:
be it just putting a /etc/host entry ..
putting the intranet dns into remote site LAN's setting
those are all unclean solution.. here is a fix after reading for 4
hours on various site and finally a solution that is incorrect describe
at support.microsoft.com:
http://support.microsoft.com/kb/311218/en-us
Hope this help for everybody. I can't reply to post from May.. so that
is why i write this article so other people can search later
-Louis
here is the body of the article:
Cannot Change the Binding Order for Remote Access Connections
View products that this article applies to.
Article ID : 311218
Last Review : June 6, 2003
Revision : 3.0
This article was previously published under Q311218
I
256986 (http://support.microsoft.com/kb/256986/EN-US/) 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.
Back to the top
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: 1. Click
Start, click Run, type regedit32 in the Open box, and then click OK.
2. Click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage
3. In the right pane, double-click Bind.
4. 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.
5. Click OK, and then quit Registry Editor.
Back to the top
STATUS
Microsoft has confirmed that this is a problem in the Microsoft
products that are listed at the beginning of this article
search and never find a solution...
solution that is a temp fix is:
be it just putting a /etc/host entry ..
putting the intranet dns into remote site LAN's setting
those are all unclean solution.. here is a fix after reading for 4
hours on various site and finally a solution that is incorrect describe
at support.microsoft.com:
http://support.microsoft.com/kb/311218/en-us
Hope this help for everybody. I can't reply to post from May.. so that
is why i write this article so other people can search later
-Louis
here is the body of the article:
Cannot Change the Binding Order for Remote Access Connections
View products that this article applies to.
Article ID : 311218
Last Review : June 6, 2003
Revision : 3.0
This article was previously published under Q311218
I
256986 (http://support.microsoft.com/kb/256986/EN-US/) 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.
Back to the top
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: 1. Click
Start, click Run, type regedit32 in the Open box, and then click OK.
2. Click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage
3. In the right pane, double-click Bind.
4. 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.
5. Click OK, and then quit Registry Editor.
Back to the top
STATUS
Microsoft has confirmed that this is a problem in the Microsoft
products that are listed at the beginning of this article