![]() ![]() If I disconnect/reconnect it manually everything returns back to life - for several minutes. ![]() pings stop reaching my work computers, but connection itself reports "connected" state. "On one of my home PCs (Windows 7 Professional 64BIT, wired connection) I have problem with VPN - after 2-5 minutes after connection to my workplace it "freezes" - i.e. I found a person having a very similar issue, however no replies to that thread: The settings for the VPN are identical to Computer A. When I disable the VPN connection on Computer B, it works indefinitely, which says to me it's clearly an issue with the VPN connection. My VPN provider has tried to assist but the only responses I've had are :Ī) Your router must not work with multiple devices and VPN.ī) I am doing this next, but what alternative ports can I use for a VPN? I have tried using default blank DNS in IPV4 config, Open DNS servers via the IPV4 configuration, DNS via the VPN itself or completely no DNS at all. VPN is still connected(in a connected state) and internal network is ok.Ĭomputer C (Android, Open VPN for Android client, ethernet) device runs fine, no problems using VPN. I am running Open VPN on three devices over Netgear DG834GV4 ( have also tried this on a Sagem 2504).Ĭomputer A (Windows 7, Viscosity VPN client, ethernet) runs fine, no problems using VPN.Ĭomputer B (Windows 7, Viscosity VPN client, Linksys wireless adapter)runs fine for about ten minutes or so, then all websites fail. My VPN client gui had this a simple check box - though there are script commands that can do it as well. AWS VPN Client version is 3.3.Solution was to force all traffic over VPN.I also got into the log directory and did a grep -R "DNS" and I got this. Same thing if I execute in the terminal networksetup -setdnsservers "Wi-Fi" 8.8.8.8 ![]() I want to understand what is going on and find a correct solution. Of course, if I go to the Network settings on the Mac, I go to the Wifi connection, then to the DNS section and change 192.168.7.1 (my correct DNS before connecting to the VPN) to 8.8.8.8 (Google's DNS), then everything works. I tried adding 10.0.0.2 as the DNS server. I also tried adding DNS servers on the VPN Client endpoint. The command nslookup answers: connection timed out no servers could be reached It keeps the original value before connecting to the VPN. In that other coworker on Mac where it works, the /etc/nf is not changed at all. For example, once I got 10.0.0.1 as well. Notice that it is not even the same IP every time I connect to the VPN. If I run scutil -dns I can see something like: DNS configuration So there is something in particular with my machine. Another co-worker, also on Mac and it works. I have a co-worker using the Windows client and it works for him. The problem is that the DNS on my MacOS stopped working. I can perfectly ping external IPs, so I do have connection. Basically, I can connect to the AWS VPN using the AWS VPN Client, but as soon as I connect, the DNS stops working and I cannot resolve anymore. I had this setup working for a couple of weeks but now suddently it stopped working. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |