- Le plus récent
- Le plus de votes
- La plupart des commentaires
-
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.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- Comment connecter différentes succursales à l'aide de AWS Site-to-Site VPN et d'AWS Direct Connect ?AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
Thanks for your response!