long login times

[kray]

I have an opendirectroy server and a client connecting through LDAP, and using portable home directories. When the client is connected to the network via en0 (network card), login takes about 10 seconds. However, when the client is not connected to the network (through en0) login takes about a minute and a half. There is a network connection through the wireless card however (en1). Could the client be trying to connect to the server through the wireless connection and that is what is talking so long?

Is there anything I can do about this?

Thanks

[InfraredAD]

If there’s no connection through the ethernet port but there is through Airport (en1 I assume), then absolutely. Unless you’ve disabled airport on the client it’s going to look for a connection on that port. You can change the priority of the airport card over other NIC’s or completely disable it, but if Airport’s the only one that has a valid network connection and you haven’t already disabled it, then it will in fact look for a connection.

I also think that connecting via a wireless connection is explicitly unsupported by Apple in their OD documentation. Good luck.

[Anonymous]

I have simular problems.

What if the DNSserver is not available because I _am_ offline.
In that case my “mobile” user on the laptop is logging in forever (more than 90secs) as well.

[AaronAdams]

For what it’s worth…

I’ve had this same problem when a DNS server was hardcoded in the network properties and it was unavailable when the mobile machine was connected to another network. Removing the DNS from the network properties and using the DHCP assigned address fixed the problem.

[Anonymous]

Thanks, but nope, didn’t help in my case.

And even if. I need this hardcoded dns address the next time i want to authenticate against the od-server.

[Anonymous]

I have this same problem when I leave the office. My university requires a vpn connection to use the network from outside. Every time I log into my laptop from outside the network, it takes forever for the wirelss card to realize that it can not resolve the DNS name. An absurdly simple solution is to tell the client user to not leave the wireless card “turned on”. If wireless is turned off before the user logs out, then when the user logs back in, everything comes up quick as can be. The user can then turn wireless back on.

[Author]

Posts