Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 3739 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSL VPN client DNS fails to resolve

alehman
After connecting with the Astaro SSL remote access client on XP and Windows 7 systems, frequently DNS resolution does not work. The problem varies between systems. Some do it every time, others only occasionally or not at all.

I found that it can usually be corrected by manually restarting the DNS client service, but this is an inconvenience for all of my users.

Apparently this is a known issue. I found these discussions:

NSLookup can resolve domain names, Ping can not resolve. Can ping IP.

Openvpn-users - DNS Resolution on 2.1.3 on Windows XP

On one of my XP systems that does it consistently I tried uninstalling KB951748 and KB952287, and that seemed to work for a few days, but it's back to it's old tricks. Windows updates automatically reinstalled those patches.

Has anyone else seen this or have any ideas?


This thread was automatically locked due to age.
Parents
  • 0
    I did not have these parameters so I updated the client. New install has:
    ip-win32 dynamic
    route-delay 4

    No joy with that. I played with route-delay and found that a setting of 8 seems to fix the problem on one of the more problematic clients. Will post back if I find anything else useful.

    Thanks for your help!
Reply
  • 0
    I did not have these parameters so I updated the client. New install has:
    ip-win32 dynamic
    route-delay 4

    No joy with that. I played with route-delay and found that a setting of 8 seems to fix the problem on one of the more problematic clients. Will post back if I find anything else useful.

    Thanks for your help!
Children
No Data