Close
Q: Mobile User Slow Login Off Network
Previous
Page
2
of 8
last
Next
-
May 18, 2010 3:07 AMby Codeus,I have a work around that seems to help, you need to add a few lines to a boot script that runs from a launchd job and to a login-hook script.
It works by checking if it can see your OD server at boot time (try by hostname or ip address and see which works best). If it can find the server fine, otherwise disable Bonjour until we have passed the loginwindow, then re-enable it for internet etc.
In your boot.sh add: -
#!/bin/bash
if [ $(host odserver.mynet.com | grep -ic "not found") -gt 0 ]; then
launchctl unload /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
else
launchctl load /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
fi
Then, in your login.sh just add: -
#!/bin/bash
launchctl load /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
The obvious caveat is that a reboot is needed to disable Bonjour and thus skip the login delay. Just logging out and in wont do the trick.
Hope this helps until we get a proper fix, or preferably a WGM managable timeout.... oh its nice to dream.... -
May 18, 2010 4:57 AMby Codeus,following on from the above, I had some issues accessing the web from home so modified the login hook. I also added a logout hook which re-DISables bonjour if the OD server is still unavailable. These are still in testing and might have undesirable side effects so use with caution.
boot.sh
#!/bin/bash
if [ $(/usr/bin/host 172.18.10.1 | grep -ic "not found:") > 0 ]; then
launchctl unload /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
fi
login.sh
#!/bin/bash
if [ $(host 172.18.10.1 | grep -ic "not found:") > 0 ]; then
launchctl unload /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
sleep 1
launchctl load /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
fi
logout.sh
#!/bin/bash
if [ $(host 172.18.10.1 | grep -ic "not found:") > 0 ]; then
launchctl unload /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
fi -
May 19, 2010 6:55 AMby jimmayl,I am having this same issue -- I'd be curious to hear if anyone who's using an offline AD "mobile account" isn't having this problem.
In any case, I can confirm that Codeus' fix works, but only for the loginwindow authentication. Any subsequent local-admin authentications (e.g. unlocking a System Preference pane) will have the same painful lag time, because Bonjour has been re-enabled with login.sh.
If I modify login.sh to keep Bonjour disabled, then the lag time goes away, but my networking is crippled: Bonjour seems to be pretty essential to Mac OS networking these days.
It sounds like this could be a Bonjour bug, which hopefully Apple will fix sometime in the not-too-distant future. -
May 27, 2010 7:14 AMby bingocaller,I just wanted to chime in that I have the same problem. Mobile AD account on a .local AD domain in 10.6.3, dreadfully long login delay away from the AD network, typically about 3.5 minutes. A mobile AD account in 10.5.8 takes about 15 seconds to log in away from the AD network.
In 10.6.3, I also have a 2 minute delay when logging in to a local admin account when away from the AD network. Unbinding from AD "fixes" the login delay for both types of account. -
Jun 9, 2010 1:01 AMby Codeus,LoginHooks (and Logout) are a standard feature of OS X and can be modified using the 'defaults' command:-
sudo defaults write com.apple.loginwindow LoginHook "/path/to/script/login.sh"
sudo defaults write com.apple.loginwindow LogoutHook "/path/to/script/logout.sh"
You can check whats there already or that they look right with: -
sudo defaults read com.apple.loginwindow
They're actually really useful as the loginwindow passes the user's shortname to the script as variable $1 so you can do all kinds of cool stuff for the user who is logging in/out. Well worth reading up on. -
Jun 10, 2010 11:29 AMby Jonathan mergy,I am seeing this too with our network. Perhaps it is an issue with 10.6.x clients and 10.5.x server (which we have too.) Would love to go to 10.6.x server, but Symantec has their head up their ... and doesn't have a native 10.6 client yet for BackupExec.
The login delays off the network are crazy. Tried all the LDAP timeouts and un-binded and re-binded to no avail. UGH
