DriftGrant Posted March 30, 2010 Posted March 30, 2010 Hi Guys, I've got a issue with a win7 laptop on a 2003 domain (using RSAT for policies) but i cant seem to get the laptop to log on from boot over wireless! driving me mad! and yes the wireless switch is on! Just doesnt make any sence, i can logon locally and if i have a network cable attached but the wireless doesnt auto connect :-( please help! Thanks in advance Grant
Psymon Posted March 31, 2010 Posted March 31, 2010 Anything in event viewer on machine? And Server is using RADIUS? Psy
Michael Posted March 31, 2010 Posted March 31, 2010 What type of authentication are you using? I recently found that Windows 7 doesn't like 64bit WEP, even if I enter the correct information. To be honest I would never recommend it anyway, but that's how a new Sky router was delivered to a customer I helped recently! Only until I changed the router to WPA did Windows 7 connect successfully.
centurio Posted March 31, 2010 Posted March 31, 2010 if using roaming profiles, you need to add admin permissions in the profile. i couldnt find any other way round it. thats the problem of using 2003 with windows 7.
_Adam_ Posted April 3, 2010 Posted April 3, 2010 I use Windows NPS to authenticate EAP-TLS against a computer certificate. Students are users with mandatory profiles. It works fine. Driftgant really needs to post more information of his setup but Event Viewer is extremely helpful in these circumstances.
macdaddy Posted April 8, 2010 Posted April 8, 2010 We are using WPA TKIP with Cisco controller. Until recently been working flawlessly with XP and Win 7. Now Win 7 is not working but XP is. What is odd is looking at the radius the user does log in, goes to our "wireless temporary IP vlan" and never makes it to its correct IP vlan. It is communicating with AD and authenticating the user because it does allow the login and in radius it does show the correct vlan for the user. But that is where it breaks down. Since it does not get onto its correct vlan the user does not get their Group Policy's. Even more odd you run a repair and/or disable reenable the wireless nic and it grabs the correct vlan IP. Restart or log off/in and same problem. We are scratching our heads trying to see what has changed.
macdaddy Posted April 8, 2010 Posted April 8, 2010 Sted, no wsus/win has not. This is also happening on at least two different platforms using different nic manufacturers. But I did update the nic driver on one the other day to be sure with no change in the results. I will be checking the win updates to see what has been recently applied since we do use wsus.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now