I am using the FQDN for the OD server in Directory Access, and the machines can resolve that address forward and backward just fine. Client login while connected to the network is very fast. The issue I am having is when I disconnect the client machines (laptops) from the network and try to login. The login process seems to stall at the login window and then takes about a minute before it finally finishes logging the user in?

Thanks for the fast response..

regards,
haxie

My Issue has mysteriously disappeared… Last night I was tyring to trouble shoot the issue, and it seemed that when the airport card was turned off and no cable was plugged into the built in enet port, that the login would hang for a minute. When i turned airport on (but didn’t connect to a wireless network – still with no network to the built in enet) the login worked just fine. This seemed to work consistently… Turn the airport off and have no other network connection to the machine, the login would take a minute to complete. Turn aiport back on (with or without connection to a wireless network) or plugin a cable to the built in port, login would work fine. I left it at that and then went to bed…

This morning, I have been trying the same tests (after a reboot) and it doesn’t seem to matter if airport is on or off, connected or not, the login works fine??? I haven’t changed anything, except I did disable and then re-enable the LDAP server profile in Directory Access of the client laptop…

I believe that it must be something to do with DNS as well, but for whatever reason, the problem has resolved itself (the type of solution I hate…)

Anyway, I will keep testing. If you have any ideas on this phenomenon, I would love to hear them. I will try the /etc/hosts trick if the problem returns.

Thanks
haxie