- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
-
Follow this fix and see if it resolves your issue https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/troubleshooting.html#resolve-host-name
-
You can also manually enter your ISP DNS in your machine and test.
-
Check AWS VPN Client logs to get more more insight of what's happening https://docs.aws.amazon.com/vpn/latest/clientvpn-user/macos-troubleshooting.html#macos-troubleshooting-client-vpn-connect
We had the same experience. For us the issue was the client was not updating the DNS servers that it should use when you are VPN'ed in, so it couldn't reach internal resources.
It could be as simple as you manually adding DNS entries that won't resolve things that are internal to your private network. You can make sure that there are no entries in your network DNS settings. Set it to automatic.
However, we switched to the Viscosity Client (https://www.sparklabs.com/viscosity/) which has some additional capabilities like enforcing DNS changes etc.
Hope this helps.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 10 Monaten
- Wie verbinde ich verschiedene Zweigstellen mithilfe von AWS Site-to-Site VPN und AWS Direct Connect?AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 9 Monaten
Thanks for your response!