|
|
> > > At first tunnel didn't work (couldn't get ip from DHCP). Then I
> > > uninstalled QOS and suddenly tunnel worked. Then I rebooted
> > > and it didn't work.
> > What I see in this log is that Windows is not bringing up the
> > TAP adapter within the 30 seconds that OpenVPN waits for it.
> >
> > The TAP adapter is brought up like this:
> >
> > (1) OpenVPN tells the TAP adapter to inform windows that it
> > is "plugged in"
> >
> > (2) Windows begins a DHCP negotiation on the TAP adapter,
> > looking for a DHCP server which will tell it the appropriate
> > TCP/IP properties to assign to the TAP adapter. The TAP
> > adapter itself responds to the DHCP server messages.
> >
> > (3) OpenVPN scans the adapter list for up to 30 seconds
> > waiting for the TAP adapter properties to transition from
> > 0.0.0.0/0.0.0.0 to something meaningful.
> >
> > (4) OpenVPN adds routes once the TAP adapter is up.
> >
> > Basically what I am seeing in the log file is that step (3)
> > is stalling out because either Windows is not initiating the
> > DHCP client handshake or the DHCP handshake is failing for
> > whatever reason.
> >
>
> I found a work-around.
>
> If I go to adapter properties, uncheck TCP/IP, accept changes, go to
> properties again, check TCP/IP and accept then it works. This
> has to be done
> to every adapter to make them work.
One more thing for the work-around. After TCP/IP has been unchecked you have
to run openvpn and after that recheck TCP/IP.
> There are some changes to registry in
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\Parameters. I
have
> to look further if there are some simple changes.
After some testing I found out that work-around makes just one change to
registry
HKLM\SYSTEM\CurrentControlSet\Network\{4D36E972-...}\{3CBE...}\Connection
new keys:
"ShowIcon"=dword:0
"IpCheckingEnabled"=dword:1
Working tap #1 adapter doesn't have those keys and removing keys from #2
afterwards doesn't change anything (both still work).
I didn't reboot my computer, so I don't know how that might mess up things
even more.
This looks like a weird bug in Windows TCP/IP, maybe Microsoft will fix it
in SP3 :)
Anssi Kolehmainen
|