Noticed something odd. In situations where:
- Direct Access client is offsite
- their Internet access is via WiFi
- they first have to enter their access credentials through a web-based captive portal before access is granted
then the Corporate Connectivity Check process malfunctions. Have seen cases where, after accessing the captive portal and being authenticated, Internet access works on the client. Direct Access then connects successfully. This is confirmed on the server console, showing the client connected and the user credentials used. The client is able to access internal resources just fine (e.g. network drives on file servers).
But on the client itself, it still says Corporate Connectivity is Not Working. The WiFi icon is showing an exclamation mark. My belief is that this is caused by the client's inability to access Microsoft NCSI servers in a timely fashion.
So it looks like the corporate connectivity checks are dependent on Microsoft NCSI checks.
Can someone at Microsoft please look into this, as it is confusing our users (not to mention us guys in IT who have only just discovered this odd behaviour!).