Major Network Impact Question

[[email protected]]

Hello, Had to think about an issue that I’ve never had to before. The schools that I support have decided to use Active Directory for authentification. Not an issue via ethernet, but wireless connectivity is where the problem enters. Here is where the new thoughts enter. If we are wired, authenticating via an Active Directory Server works fine at the login screen without having to login via a local account on the computer. But if we are wireless, (using Apple hardware for the wireless cards and Cisco for the wireless routers and switches, latest Panther OS, iBooks, eMac’s G5’s, etc.) authentification doesn’t work at the login screen for Active Directory. If we login to a local account on the computer, then connect via “Connect to Server,” this works fine. User’s home directory is mounted and data can be saved… which is what we are trying to do. Questions are: Is there a way to make wireless give an ip address the same way that wired does at the OS login level without having to login locally first? Is this the way wireless was meant to work for ??? reasons? Is there a startup script that can be ran to force a wireless ip address the same way that wired seems to do?
This is causing huge frustrations at every campus from middle school to high schools. Thanks in advance for any insight and information.

[MDhaliwal]

I do have that happen every once in a while in my environment, but in the newer Panther builds I don’t see to have this issue very often at all. What version of the OS are you using? Do you have caching enabled for your mobile users as well?

[Author]

Posts