Hello,
I am fishing to see if anyone has had this issue and resolved it...
I have at the moment 40 users (and I bought a surface pro f2 or testing this) with problems using surface pro, surface pro 2, and surface 2 on WiFi.
The devices complete 802.11 auth and assoc, complete 802.1x auth, always start the dhcp process (messages are seen on the dhcp server and replies sent), sometimes complete the dhcp process (get an ip).
They then stop transmiting on wireless.
Through testing I have uncovered a few details that can make the devices work (but I cannot enact those changes as they cause other issues)
With MPDU Aggregation DISABLED on our wireless subnet ( /16 ) ; the surface pro completes the 802.11 auth and assoc, completes the 802.1X auth, starts the DHCP process and usually gets an IP and then stops working.
With MPDU Aggregation ENABLED on our wireless subnet ( /16 ) ; the surface pro works fine. ---- I cannot enable MPDU aggregation as almost all our linux users will no longer be able to use our 802.1X eduroam network if I do. (and there are a lot more linux users than surface users)
With MPDU Aggregation DISABLED on a test wireless subnet ( /27 ) ; the surface pro works fine. ---- We made the change to large flat subnet from vlan pools and do not want to go back. (I also don't know at what size of subnet the surface pro will stop working at)
I called microsoft customer support for my surface, I was told to just try updating every 2 weeks to see if it works, if it doesn't I roll back to a good working driver. (14.69.17064.93)
This doesn't help the surface RT 2 which suffers the same issue.
I have opened an Aruba support ticket, but it hasn't gotten results thus far (they also have not said it's a MS problem yet either)
I have not contacted MS premier support yet.
We are running 6.3.1.2 on 7240's.
Access points are a mix of 105's, 93h's, 125's, 124's, and a few 61's, 65's, 70's that have yet to be repalced.
I am wondering if anyone else has had this issue and resolved it.
Thanks,
Matt
#7240