5 Replies Latest reply on Oct 27, 2016 11:36 AM by evanh

    Windows 10 Surface Pro 3 Unable to Connect

    cathompson New Member

      We are experiencing an issue with Windows 10 on Surface Pro 3's where after attempting to authenticate with the Bluesocket vWLAN captive portal the network adapter receives an APIP (169.254.x.x) address. This issue is only present on Surface Pro 3's with Windows 10 at this time. No issues on Surface Pro 3 with Windows 8.1. No issues with Windows 10 on other platforms.

      We have tried logging in with other browsers. All OS and firmware updates have been installed. No issues when connecting to SSIDs configured to use WPA2-PSK. No issues when using MAC authentication.


      When the issue was first discovered we were running vWLAN version V2_5_1_07. We have upgraded to and are currently running V2_6_1_06.


      The only fix we have found for now is to stop the "time broker server". When the time broker service is not running we can successfully authenticate with the captive portal.


      Anyone else experiencing this issue? Any thoughts?




      Charles Thompson

        • Re: Windows 10 Surface Pro 3 Unable to Connect
          ms.m New Member

          We have had a similar experience with Windows 10 laptops and services. The solution that we found was to not allow wifi-sense to automatically log users in.



          Here are the steps and the FAQ I pulled them from.




          Can I use Wi‑Fi without using Wi‑Fi Sense?


          Yes, you can still connect to a Wi‑Fi network on your own.


          If you don't want to use Wi‑Fi Sense, you can go to Settings > Network & Internet > Wi‑Fi > Manage Wi‑Fi settings, and then turn off Connect to suggested open hotspots and Connect to networks shared by my contacts.




          There is also an option to configure the ssid name with _optout but we would prefer to not have to either add and ssid or offer one with a confusing term that could worry our users.


          We have a ticket in to look at this issue with adtran.

          • Re: Windows 10 Surface Pro 3 Unable to Connect
            cathompson New Member



            After working with Adtran support we have determined that the issue is related to the fact that Surface Pro 3's will not renew their DHCP lease halfway through the 10 second lease time when in the unregistered role. This causes them to flop between a NAC assigned IP address (10.252.x.x) and a self assigned IP address (169.254.x.x). My research hasn't turned up much on why this would occur especially only on this particular hardware/software configuration. Any ideas out there?



            • Re: Windows 10 Surface Pro 3 Unable to Connect
              evanh Employee



              As Charles Thompson helpfully posted, ADTRAN Support has identified an issue in the Microsoft Surface Pro that causes it to release its IP address before the lease is up. BlueSocket devices use a NAC IP transition system within the Captive Portal to allow customers the unique freedom to effectively quarantine their devices when they have not logged in within a network that only exists inside the BlueSocket APs (The Un-registered Role and NAC Location).


              Unfortunately the transition of IP is difficult for many new devices because of a lack of strict standards on DHCP functionality. In the Surface Pro case, it releases the IP address at exactly half the lease time instead of when the lease is up. If the user is successful at logging in before this happens, the transition happens normally. This is why the issue may be sporadic to some users. Other vendors do not experience the issue because their effective role placement occurs before authentication. (This sacrifices a large amount of Role Based Access Control functionality that BlueSocket provides, but resolves the use-ability issues with some devices.)


              In version 2.9.0 which will be available shortly (you can sign up for Software Notifications here) we have added an option for a Relaxed NAC Lease which when used with the Surface Pro is successful at mitigating this issue in our internal testing.


              In the near future, we are planning on adding an option for a Walled Garden Captive Portal approach which will resolve this issue fully. This will be an option along with the original NAC method so that configurations are maintained and users have the ability to use either scenario.



              Evan Hudson

              ADTRAN BlueSocket Product Support Manager