To fix this, remove the company's domain from the DNS search list, and ask your company's administrators if they can specify this as a DHCP parameter.
|
|
|
A mobile user account can take forever to login if you are at a different location, but have an internet connection. To login a mobile account, OS X will first try to connect the Open Directory server. If you have a domain search list in your network preferences that lists your company's domain, this can cause long timeouts.
To fix this, remove the company's domain from the DNS search list, and ask your company's administrators if they can specify this as a DHCP parameter.
•
[11,091 views]
Hint Options
Fix slow mobile user logins
First of all, the Search Domains shouldn't be entered manually. It should always be provided by DHCP server -- centralized management and less headache.
Fix slow mobile user logins
"Therefore, your laptop won't be able to resolve server.123corp.com when it's outside of the office and won't cause any delay at logon."
Fix slow mobile user logins
I always set up internal domains without an extension so there's absolutely no possibility of conflict with external domains. Works perfectly fine to have your internal domain simply be company and is easy to set up - at least with OSX Server :).
As far as a conflict like the hinter is illustrating though, a better solution would be to get in the habit of creating locations for non-work sites - a Generic DHCP location without any directory bindings, domain prefs or DCHP specifics would speed things up quite a bit and is easy to switch to. Much easier than trying to get your rock-obstinate network admin to make any changes to his/her carefully crafted and delicately balanced server or router setup. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.15 seconds |
|