Win7 with multiple domains and a wireless logon
Hello, I have a domain that my users log on to that is different then what my computers domain is. I have setup the system to allow users to log on to the systems with the domain accounts they use for all other systems. my problem is that when the system is wired to the network a user can just type in the account information. when connecting to the network wireless they must type in domain\account for the wireless settings to log them onto the wireless. it works its just not pretty any suggestions?
November 3rd, 2010 7:02pm

The domain login prompt should not be affected in any way with regard to how you are connected to the network via media. By default Windows 7 shows you which domain you are logging into by default. Unlike previous OS (XP and older), it does not provide a dropdown list of domains. Visit: anITKB.com, an IT Knowledge Base.
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2010 8:16pm

my problem is that our wireless network is set to wpa2-ent and uses the users log on info to connect to it. When the machine is set to the users domain(via the GPO on the system) a user cannot authenticate to the wireless. im not sure if the system just does not pass the default domain set in the GPO to the wireless or not. Example: Computer is joined to domain A. User accounts are in domain B. Group policy has set computers in domain A to default domain B for user log on. When the computer is wired to the network the user just types in "username" and the password. the account is found and the user is logged onto the computer. When the computer is not connected to the domain the system attempts to log on to the wireless first, The system are set to use the log on information from the windows 7 log on screen, But the only way this works is when the user types B\"username" even though the default domain in the GPO is set to B the user must still type it in for it to pass that to the wireless log on. My question is how do i get they system to pass the default domain to the wireless so users do not need to type that information in.
November 4th, 2010 4:54pm

It sounds like, if I understand correctly, the Domain B is set to default via a GPO. The GPO settings have to be applied first (they do when connected via wire because the computer settings are applied). When its not connected the GPO has not applied yet so the default doesnt become B. For you WPA2-ENT settings, it sounds like you are doing PEAP authentication, I assume, since you are depending on the logon credentials. Well, the PEAP settings by default, will take the user's logged on credentials to connect. Of course, putting these PCs in domain B would probably resolve the issue. Also, creating a Local Policy on the workstations to default to B for the logon would work, but you would need to go around and configure a bunch of machines until you can include this in an image. Other than that, you could change the default settings for PEAP and force it to prompt the user to connect to wireless and provide credentials via a balloon in the task bar. Out of other ideas at the moment.. Visit: anITKB.com, an IT Knowledge Base.
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2010 7:03pm

Yes the WIFI system is using PEAP sorry for forgetting that. I wish i could put all the systems into the same domain. Sadly each area has its own subdomain as IT was decentralized. so in reality there would be domains a - g (or something around that). each area takes care of its systems and domain. The network is taken care of the head IT department along with the users log on domain. I know they have this working but for whatever reason they do not want to share. Thanks for your help.
November 5th, 2010 3:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics