Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-08 Thread Marcel Pennewiß
On Thursday 08 April 2010 08:03:54 Johan Ymerson wrote: > I have tried different values for route-delay and tap-sleep, but it doesn't > help. AFAIR our clients use: route-method exe route-delay 2 ip-win32 dynamic No one of our win7-users complained about this problem until now. Marcel

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-08 Thread Heiko Hund
On Wednesday 07 April 2010 22:52:22 Jan Just Keijser wrote: > this could be a timing issue, which could be caused by changes to the > userspace openvpn part; did you try playing with the > route-delay > tap-sleep > dhcp-renew > flags ? did that have any affect? We've tried all of those with

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-08 Thread Johan Ymerson
Jan Just Keijser wrote on 2010-04-07 22:52:22: > what exactly do you mean with 'nslookup always works' ? nslookup always seem to use the correct dns server. For example, we have an internal website called 'intranet'. I can do `nslookup intrnet`, and it will return the

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-07 Thread Johan Ymerson
Heiko Hund wrote on 2010-04-07 15:26:05: > > Then I don't think we see the same problem. We have been using 2.0.9 on > > ~100 machines for a couple of years now without these problems. We > > upgraded 3 of them to 2.1.1, and they all instantly got this problem. We > > downgraded

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-07 Thread Heiko Hund
On Wednesday 07 April 2010 14:04:18 Johan Ymerson wrote: > "Heiko Hund" wrote on 2010-04-07 09:59:08: > > We also tried 2.0.9 but were able to reproduce the bug with it as well, > > so it has nothing to do with the openvpn driver version involved. I came > > to the conclusion

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-07 Thread Heiko Hund
On Wednesday 07 April 2010 13:52:22 Jan Just Keijser wrote: > > We've contacted Microsoft tech support about this issue. If anything > > like a > > fix comes out of that I'll post an update here. If not we'll have to > > consider > > a workaround of some kind, but let's wait with that discussion

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-07 Thread Johan Ymerson
Jan Just Keijser wrote on 2010-04-07 13:52:22: > isn't > ipconfig /flushdns No, doesn't help in this case. > or > net stop dnscache > net start dnscache I hadn't tested this before, but yes, it does seem to help (only done limited testing so far). > enough? This

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-07 Thread Johan Ymerson
"Heiko Hund" wrote on 2010-04-07 09:59:08: > > Hi, > On Tuesday 06 April 2010 22:36:31 Johan Ymerson wrote: > > I have tested on 3 PC's with Windows XP, all 3 show the same problem, at > > almost 100% of my connection attempts. OpenVPN 2.0.9 does not have this > > issue (ie.

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-07 Thread Jan Just Keijser
Heiko Hund wrote: Hi, On Tuesday 06 April 2010 22:36:31 Johan Ymerson wrote: > I have tested on 3 PC's with Windows XP, all 3 show the same problem, at > almost 100% of my connection attempts. OpenVPN 2.0.9 does not have this > issue (ie. reverting back to 2.0.9 on the same machines with the

Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-07 Thread Heiko Hund
Title: Re: [Openvpn-devel] DNS problems with openvpn 2.1 on Windows Hi, On Tuesday 06 April 2010 22:36:31 Johan Ymerson wrote: > I have tested on 3 PC's with Windows XP, all 3 show the same problem, at > almost 100% of my connection attempts. OpenVPN 2.0.9 does not have this >

[Openvpn-devel] DNS problems with openvpn 2.1 on Windows

2010-04-06 Thread Johan Ymerson
Hi, I have been testing OpenVPN 2.1.1 for a while and have came across a strange DNS problem. Other people seem to have seen the same problem (ex. http://www.astaro.org/astaro-gateway-products/vpn-site-site-remote-access/21387-new-sslvpn-client-dns-problems.html), and a work-around is