[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

Re: [Openvpn-users] Beta11 - client-to-client


  • Subject: Re: [Openvpn-users] Beta11 - client-to-client
  • From: "Adam Pavelec" <apavelec@xxxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 4 Nov 2004 09:24:44 -0500

On Tuesday, November 02, 2004 3:56 PM [GMT-5=EST], I wrote:

If the problem is due to netbios resolution, you should check the
netbios node type on the windows client with 'ipconfig /all' and try
to setup someone different by checking this document:
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

Aha!  On most other clients I have checked, the node type was
'unknown'. The laptop in question shows 'mixed'.  From what I read in
the KB article, the node type is handed out by the DHCP server.  I
highly doubt that my OpenVPN server was the culprit, but it's
important to mention that I've been using this same laptop to
configure my new DSL Modem as well as configuring a few routers and
such, all of which have handed out IP addresses.  My guess is that
somewhere down the line, one of them changed its node type to mixed.
On the laptop:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\DhcpNodeType

...exists, and is hex value '4'

On the other workstations I have checked, this key does not exist.
Hopefully removing this key will be the solution.  I'll submit an
update later, for I am unable to bounce the laptop with the lid
closed...

Well, deleting the above key returned the node type to 'unknown', but I've been continuing to experience local routing through the VPN tunnel.


Here's another thing to consider: since my move, the laptop's Wi-Fi connection has been flaky at best -- this is probably due to the 100+ year old home that I'm now living in having plaster/lathe walls. It seems that when the Wi-Fi connection is interrupted, the OpenVPN tunnel remains connected until it times out, which is after the Wi-Fi connection is re-established. I think that it is at this point that the routing decides to switch from local to VPN. It seems that a ipconfig /flushdns will return things back to normal, at least until the next wireless interruption. Ultimately, using an LMHOSTS file seems to be the best solution, but it still irks me why this only recently became an issue.

-Adam




____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users