Logging into AD when the computers are wireless and need to login to the wireless first?

[videopuppy]

How (if) can these machines I have in a wireless room access AD while on wireless? Here is the stumper….. the computers in this room are pointed to an access point that uses BLUESOCKET, meaning that they have to login into the wireless before they can access the network to even login to Active Directory.

Thank you
Dave

[Patrick Gallagher]

I’m not sure about Bluesocket, but here’s instructions on joining an 802.1x network on login.
[url]http://adminselfhelp.com/?p=50[/url]

—
Patrick Gallagher
ACSA, RHCT, A+, Network+

[macinandy]

Hi Dave, we have the setup mentioned in the above post for our staff Macbooks and it works well. Our staff wireless is a BlueSocket 802.1X-secured network and exporting to the login window presents few issues. Our student wireless is unsecured and they need to authenticate to the controller via a web browser to access anything on the network , but they are not bound to AD yet, as the staff are.

If there is something I can help you with, let me know.

Cheers

[schilled]

Dave,
I don’t think this is a sollution but we have a similar set up but our wireless doesn’t connect to the domains. We have to have the make a mobile account for everyone on initial log in. This allows the person to authenticate with the cached credentials. This may be a problem for you though when it comes time to change passwords. We were having issues with people taking for ever to log in off campus and part of it is our DNS configuration allows for the computers to discover the domain controllers but they can not talk to them so people were getting the beach ball for 5 minutes and then they would log in. We worked around this by changing the setting in Airport Options that disconnects the wireless on log out. I know this isn’t the answer you want but it may be a temporary work around.

Doug

[mooching]

Hi Dave,

I dont know if you have a solution for this yet, I just came accross it. We are using Bluesocket for our wireless solution. We came up with three solutions so far. The one we are currently using is MAC authentication, we collect the wireless MAC for all our Mac clients and register them in the Bluesocket Controller. You do run the risk of a MAC spoof attack though. Our Windows clients are authenticated when they log on via transparent NTLM Another solution is Admitmac and use transparent NTLM authentication, it was very cost prohivitave for us. The other is 802.1x which is what we will probably impliment when we have time to research it.

[Author]

Posts