|
|
On Tue, 3 Jan 2006, James Yonan wrote: Among other changes, this release improves the "ip-win32 adaptive" option and makes it the default. The goal is to automatically work around issues with third-party Windows firewalls that block the TAP-Win32 adapter DHCP negotiation, by falling back to netsh when DHCP-mode fails. In this release, the OpenVPN Windows client knows how to set DNS/WINS addresses (as well as the primary adapter IP/netmask) using netsh, if DHCP-mode fails. It will be interesting to see if this really fixes the problems with 3rd party firewalls. In the cases I've seen having this problem it didn't help to manually set an IP on the adapter. I recall some error message reported by Windows when trying to ping a remote host, but hopefully I'm wrong! However the last month I've had alot of problems where my TAP interface does not get any IP address from the TAP driver DHCP server after I've had the machine suspended. Shuting down OpenVPN and restarting it ususally solves it. Sometimes a simple ipconfig /release, ipconfig /renew helps, but not always. In this case the new beta will probably solve the problem as this seems to be a pure DHCP problem. I don't know why these problems has suddenly started, but I blame it on Mr Gates, a re-install of Windows and I'm sure it would work like a charm again. -- _____________________________________________________________ Mathias Sundman (^) ASCII Ribbon Campaign OpenVPN GUI for Windows X NO HTML/RTF in e-mail http://openvpn.se/ / \ NO Word docs in e-mail |