I had a interesting problem recently where a Windows 8 laptop connected to a domain over wireless would login, but then not load the profile as it couldn't authenticate with the domain controller. It would instead, pop up with a username and password box, which if you entered the users details again would sometimes connect and work and other times not.
Very strange, as the system was connected to the wireless without issue and I could ping the server and do everything would expect.
On close examination, i discovered that the wireless network had manged to get itself changed from a "domain" category to a "private".
In the network and sharing center I was unable to change it from a public back to domain so I resorted to using the registry.
The keys are located in:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
Each folder in the profile key is a different connection - click on them and look for the one called "Category".
The category field defines the connection type:
0 = public
1 = private
2 = domain
I changed it back to a 2 and reboot the laptop - and everything started working again. This solved the problem for 2 days, whereupon the connected then changed to a private network and the same issue occurred again.
This time, i used the wireless network list to forget the network totally and then reconnect from scratch. The system picked it up as a domain connect immediately and this seems to have solved the problem since.
A new one on me :)
Update:
the problem came back! And on further investigation I discovered that the client had managed to re-enable DHCP on their router (instead of their server). This was causing the laptop to automatically go into "public" profile mode. Disabled DHCP on the router and the issue went away. Guess I should have looked at the problem in more detail
Very strange, as the system was connected to the wireless without issue and I could ping the server and do everything would expect.
On close examination, i discovered that the wireless network had manged to get itself changed from a "domain" category to a "private".
In the network and sharing center I was unable to change it from a public back to domain so I resorted to using the registry.
The keys are located in:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
Each folder in the profile key is a different connection - click on them and look for the one called "Category".
The category field defines the connection type:
0 = public
1 = private
2 = domain
I changed it back to a 2 and reboot the laptop - and everything started working again. This solved the problem for 2 days, whereupon the connected then changed to a private network and the same issue occurred again.
This time, i used the wireless network list to forget the network totally and then reconnect from scratch. The system picked it up as a domain connect immediately and this seems to have solved the problem since.
A new one on me :)
Update:
the problem came back! And on further investigation I discovered that the client had managed to re-enable DHCP on their router (instead of their server). This was causing the laptop to automatically go into "public" profile mode. Disabled DHCP on the router and the issue went away. Guess I should have looked at the problem in more detail
No comments:
Post a Comment