We're testing SA8.0R1.1, and using the Windows 8.1 built-in client and everything else seems to work fine, except the system (ping, IE 11) loses name resolution. Looking up names via nslookup still works, as long as we add the final dot "www.cnn.com." instead of "www.cnn.com"
DNS appears only broken when the tunnel is active. The tunnel adapter does NOT show any DNS servers with ipconfig /all.
Obviously, this is a show stopper. Has anyone else run into this? Any clues? (Aside from adding IPv6, the connection profile hasn't changed from a working setup. DNS is handed to the client via DHCP server, and "DHCP DNS Settings" is selected in the connection profile.)
I mainly tested 8.0 version. In-box client is working. I am also facing problems with DNS. Haven't figured out yet what is causing this. Maybe it's time for JTAC.
Btw, do you know if it is possible to use sign-in pages for In-Box VPN like: https://some.site.com/inbox.
Customer confirmed only working scenario with default page like: https://some.site.com/ though.
Did you test any of SoH part? Classis HC is not supported.
We only tested with the https://ourvpn.ourdomain.ourtld URL, no differentiated sign-in pages.
We did not have any host checker or posture checking at this test. Authentication is basic password/RADIUS.
Amusingly, when using a web browser to log in, it still offers the standalone Pulse installation, despite having an in-box client. With the standalone client installed, it works.
I'll go ahead and open a JTAC case to figure it out, thanks.
thanks for quick answer
Let me know when you get some feedback from JTAC engineers.
I will also perform some further tests till the end of week and let you know if I find something new.
Btw, I am not sure right now. I also think that DNS is not assigned. I am using DHCP. Would be also nice to try out manual settings (disable DHCP).
Yes, that is correct you cannot do path-based logins with the in-box client.
For the DNS issue, yes, please open a case with JTAC.