When setting up the Unified Access Gateway (UAG) for the first time you might run into network issues or trying to prove to your network team that a port is not open. The options you have when doing this troubleshooting include 5 tools (Ping, nslookup, tracepath, curl, and tcpdump) from the UAG console interface. Another tool that might help is wireshark to run on your connection servers or VDI desktops. Using nslookup to check DNS: First make sure that DNS is working by using nslookup command from the UAG console. This should be tested on the following items. Connection Server FQDN Load Balanced VIP for Internal Connection servers Should also check that your External URL can be resolved on public DNS. Using Ping to troubleshoot UAG network issues: Next check basic network connectivity with ping by running the ping command from the UAG console. This should be tested for the following items. Ping each internal connection server Ping the load balanced VIP for Internal
EUC and Other Technology Topics