Park Bo Gart Lv2Posted 02 Apr 2020 18:18
  
This is our current problem also. One thing that I have noticed given that I successfully logged in the SSL VPN:

1. Access to the resources that you defined (IP, IP Range) is working.
2. Access to FQDN is not working. You will notice that your workstation is trying to resolve the FQDN using the DNS IP configured on your primary physical NIC, not the DNS IP given by the virtual NIC of SSL VPN.

So RND created a patch for us that once you logged into the SSL VPN, the DNS IP config of your primary physical NIC will add the DNS IP you set in the SSL VPN Local DNS configuration. Once logged out, the DNS IP will be removed.

also, another problem related to SSL VPN but not related to DNS is that when you assign IP Range to the resources, checking out the routing table of your PC, you will see that it is populated by single IP with a mask of /32 instead of just the range that you defined.

I Can Help:

Change

Moderator on This Board

1
131
3

Started Topics

Followers

Follow

18
8
0

Started Topics

Followers

Follow

Board Leaders