Hi, Arrg.. I should have never updated our windows installations ;) Now one of our laptops has hit "this hanging in no IP-land" bliss. I see this issue mentioned in some trac tickets and here on the users list.
Here is what I see: after successfully passing through TLS hurdles, tun/tap open etc, openvpn says "Notified TAP-Windows driver to set a DHCP IP/netmask of ... " as expected. But that setting IP apparently fails. So test_route fails as well and tries the last resort of using route.exe. That obviously fails with "no adapter to reach that gateway" kind of error. Finally openvpn ends up in a CONNECTED with ERROR state and stays there. Restarting by SIGHUP, SIGTERM, or even resetting of the adapter, starting afresh, nothing helps.. The only cure appears to be to wait it out -- give it a few minutes before restarting! If that old adage of "time heals.." was my ridiculous solution I wouldn't have written this. There is a subtle error in the system logs --- a 0 byte memory allocation error by DNS for some sharedaccess_NAT whatever that is.. Of course we have a lot more than 0 bytes of free memory. But on this client, internet connection sharing (ICS) was enabled on the NIC and that appears to be the culprit. Somehow ICS tries to do some NAT setup for the new IP and never completes, or some such nonsense. I don't want to know what it is, so disabled ICS and all seems well. So, folks facing this no IP issue, could you please check whether any network adapter (most likely on the ethernet adapter) is shared and does disabling ICS solves this problem? I would love to hear other's experience on this. No ICS may not be an acceptable solution for many, but I don't know any work-around.. Thanks for listening, Selva
------------------------------------------------------------------------------
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
