Thanks Chris. Your last e-mail gave me the proper terms to search for
Specifically this info:
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 the following registry subkey:
In the right pane, double-click
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
On Thu, 2005-07-07 at 15:44 -0400, Chris Buechler wrote:
> On 7/7/05, Andy Choi <andy dash choi at infinitelabs dot net> wrote:
> > the TCP/IP properties stuff: That doesn't do anything.
> > m0n0wall is the VPN not a box internally. m0n0wall is already dishing out DNS servers to VPN
clients that connect. I need to know how to force windows to use the DNS settings it has been
provided in the VPN connection instead of the wireless/ethernet/dialup connection.
> good question.... usually adapter binding order takes care of issues
> with different connections trying to take over, but moving "remote
> access connections" to the top of the binding order had no effect (and
> I'm not even sure if Windows includes PPTP in "remote access
> connections", or only dial up stuff). My Cisco VPN client puts the
> DNS servers handed out by the other side on top of the priority list,
> but the Windows client doesn't seem to do nor permit that, from what I
> can see.
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch