When users (even me) connect via the SSL VPN client there are certain webapps that will not load without the fqdn.
Examples:
https://app1 = Fine
https://app2 = Not Fine
https://app2.domain.local.com = Fine
You can ping and tracert "app2" and it resolves properly to the IP address.
The difference is that app1 is on 192.168.2.x while app2 is on 192.168.3.x
Remote Access > SSL > Remote Access Profile lists access to the 192.168.0.0/16
Remote Access > Advanced - The DNS Servers are entered as well as the domain name for the DNS suffix (both DNS servers are on the 192.168.2.X) and I have verified that all of the non-working DNS names have their records properly mapped to the correct IP.
Network Services > DNS - "VPN Pool (SSL)" is allowed.
Network Services > DNS > Request Routing - 3.168.192.in-addr.arpa is there and pointed to our domain controller group.
Everything appears to be configured correctly. Looking an ipconfig /all on my home machine, connected to the SSL VPN shows the dns suffix is there, and again I can ping and tracert using the DNS name and that works properly.
We are using split tunnel and the IPv4 metric on the virtual adapter is set to 1.
I've been fighting this for quite some time and looking at similar issues posted on the forums but those appears to be issues with it not working at all. Ours DNS works...except for things on a different IP range.
This thread was automatically locked due to age.
