Active Directory: Extremely slow mobile account login

MacFixIt reader Michael Eldrige reports issues with abnormally slow login to Active Directory services when using mobile login (i.e. logging in from outside the network hosting the Active Directory services).

Michael writes:

"I have several Apple laptops (PowerBooks and MacBooks) running 10.4.6 bound to my companies Active Directory running on a Windows 2000 domain controller. The 'Create mobile account at login' option in the Active Directory plugin of Directory Access is checked, networks users have logged in and their credentials have been cached. Our domain controller is behind a FireWall and runs a subdomain which is only accessible in the building or via a VPN connection.

"When I log into any of the laptops with a valid network account, while connected to the companies network, the log in works. If I turn off AirPort and unplug the ethernet cable the log in works. So at this point logging in works either when connected to the companies network or when all network interfaces have no connectivity. The fact that logging in works with all network interfaces down tells me that the caching of the network account is okay.

"Now here's the problem. If I'm connected to an external network (i.e. cable modem, DSL, etc) either wirelessly or wired it takes anywhere from 2 to 10 minutes to log in. If the connection is wireless I have to turn off the wireless router for the log in to work. If the connection is wired I have to unplug the ethernet cable for the log in to work (this is of course assuming that AirPort is disabled because if it hasn't been I have to turn off the wireless router as mentioned previously)."

So, when connected from outside the network, Michael is only able to login to cached Active Directory services -- it will not work when there is an active network connection.

If you are experiencing a similar issue, please let us know.

For more information on troubleshooting Active Directory issues, see our recently published tutorial "Resolving problems with connecting to Windows servers/clients."

Resources