I have had some problems with DirectAccess not starting to establish a connection when connecting through a WLAN which requires you to authenticate through a captive portal. Most of companies visitor wireless networks have an authentication based on these so it's a bit of a problem for my users.

Is there some settings that could be configured for DirectAccess to attempt a connection again after a certain time?

Other option that i've been wondering is that could i create shortcuts that would restart the ip helper and network connectivity assistant services as this has always fixed the DirectAcess connection after authenticating to these visitor networks.

It should connect as soon as you have authenticated and have "open" Internet access - what are you specifical

Hello,

We have the same problem with Direct Access and a Wireless AP in our company. When the captive portal appear, users enter their login and password and web is working. But Direct Access is not mounting, or sometimes after several minutes (10 or more). It normally checks connectivity each 30 seconds i think, but in this specific case, it doesn't work.

But if we close the user session or reboot computer, and re-open user session, as a token is yet present, the Direct Access connection is working after 10/15 seconds. So i can confirm that there is a really problem between Direct Access and Captive Portal and we don't know too how to fix it...

Can you try restarting IP helper service after getting connected to the internet using Captive portal ?

Can you try restarting IP helper service after getting connected to the internet using Captive portal ?

The Captive portal will initially block the IP HTTPS connections at the beginning till its authenticated then it will take it couple of minutes to connect. Alternatively you can restart the IP Helper service after getting connected.

• Edited by Ahmed Nabil MahmoudMVP, Moderator 22 hours 14 minutes ago
• Proposed as answer by Ahmed Nabil MahmoudMVP, Moderator 22 hours 14 minutes ago

Can you try restarting IP helper service after getting connected to the internet using Captive portal ?

The Captive portal will initially block the IP HTTPS connections at the beginning till its authenticated then it will take it couple of minutes to connect. Alternatively you can restart the IP Helper service after getting connected.

• Edited by Ahmed Nabil MahmoudMVP, Moderator Friday, April 24, 2015 9:09 AM
• Proposed as answer by Ahmed Nabil MahmoudMVP, Moderator Friday, April 24, 2015 9:09 AM

Can you try restarting IP helper service after getting connected to the internet using Captive portal ?

The Captive portal will initially block the IP HTTPS connections at the beginning till its authenticated then it will take it couple of minutes to connect. Alternatively you can restart the IP Helper service after getting connected.

• Edited by Ahmed Nabil MahmoudMVP, Moderator Friday, April 24, 2015 9:09 AM
• Proposed as answer by Ahmed Nabil MahmoudMVP, Moderator Friday, April 24, 2015 9:09 AM

There is a backoff algorithm that gets employed if IP-HTTPS cannot connect - this is increasing in backoff times and can prevent IP-HTTPS from retrying the connection for anything between 5-15 minutes...this is often triggered in captive portal scenarios...

More info here: https://msdn.microsoft.com/en-us/library/dd339950.aspx