Comments

  • Thanks for the replies. Steve, sounds like my situation is the same as yours - I also have local DCs serving as DNS servers specified in the SSLVPN setup and have FQDN in the domain name. Is your problem resolved or still going on?
  • Hi, just checking in to see if anyone has a different solution for this problem. I recently had to change my SSLVPN to route all traffic through the VPN (we were previously split tunneling). With that I had to create a policy to allow SSLVPN Users access to all trusted and optional networks. However, like Steve, AD U&C now…