Network accounts freeze at login

I have a lab with a mix of 10.4 and 10.5 machines connected to a leapord server. Thought the day when users login the login screen locks up and users are forced to restart the computer. After they restart the computer they are able to login. The machines are connected to a server that is set to open directory master.

Hi There,
We still have that problem with 10.5 clients only. See my previous post
http://discussions.apple.com/message.jspa?messageID=8613415#8613415
Let me know if you find a fix, i have almost given up o this one.
Kevin

Similar Messages

ApacheDS (LDAP) Network Accounts Never Can Login

I have been fighting with LDAP via ApacheDS for days attempting to get Mavericks to actually authenticate against the LDAP server.
Here is the path that I have taken:
ApacheDS is setup with simple authentication (disabled everything else for the moment after attempting to login every which way).
Here is an example of the LDAP setup:
dc=example,dc=com
ou=usersuid=username
cn=Full Name
sn=Name
displayName=FullName
userPassword=hash
uid=username
ou=groups
cn=Users
cn=Administrators
Then I went to Users and Groups, Allow network users to login is checked
Joined a Network Account Server
(When looking at edit, it shows a green indicator)
I setup a custom mapping under LDAPv3 which contains:
Seach Base: ou=users,dc=example,dc=com
Users: inetOrgPerson
AuthenticationAuthority: uid
NFSHomeDirectory: #/Users/$uid$
PrimaryGroupID: #20
RealName: cn
RecordName: uid
UniqueID: uid
UserShell: #/bin/bash
I can see the information in the Directory Editor from the LDAP server, Search Policy has the network accounts right after the local accounts.
When attempting to login, it just shakes... Here is the only items that I can see in the opendirectoryd.log:
2014-01-04 10:26:50.785452 CST - Loaded bundle at path '/System/Library/OpenDirectory/Modules/ldap.bundle'
2014-01-04 10:27:06.734300 CST - 22.805 - Client: opendirectoryd, UID: 0, EUID: 0, GID: 0, EGID: 0
2014-01-04 10:27:06.734300 CST - 22.805, Module: ldap - failed to retrieve LDAP server schema - LDAP error - 50
2014-01-04 10:27:07.031977 CST - 22.823.826 - Client: opendirectoryd, UID: 0, EUID: 0, GID: 0, EGID: 0
2014-01-04 10:27:07.031977 CST - 22.823.826, Node: /LDAPv3/example.com, Module: ldap - __odnode_copy_record_block_invoke: 4101 No predicates provided
Anyone have any ideas?

I was able to activate the debug log in the Leopard client machine, but I don't know how to look from another machine via SSH... Could you explain a bit the procedure? Is it possible to try to log in as a network user and then, after failure, log in as an admin account and check the log with Console?
Today I found out that Snow Leopard clients are also not able to log in... Similar problem in Directory Utility:
This is what I found in the log for this machine (tried to log in with two different accounts):
25/04/12 20:09:17          SecurityAgent[321]          User info context values set for XXX
25/04/12 20:09:18          authorizationhost[320]          Failed to authenticate user <XXX> (tDirStatus: -14103).
25/04/12 20:09:25          SecurityAgent[321]          User info context values set for YYY
25/04/12 20:09:25          authorizationhost[320]          Failed to authenticate user <YYY> (tDirStatus: -14103).
Couldn't find much about this in Google.
I'm starting to feel really disappointed about this!
(sorry for the delay in answering, been abroad...)

Network accounts do not login in

Hi everyone,
last month our Xserve G5 with Leopard Server which controlled user accounts in our computer labs died. We replaced it with a Mac mini server (that includes Lion Server) –by the way, this is the first server that I ever setup–.During initial configuration, the server was fully updated to Lion server 10.7.3, and stablished as an OD Master. I didn't import anything from the old server, so all accounts and groups and preferences and everything have been defined from scratch.
Everything was working good until I finish the setup and try to connect from one of our Leopard client machines. I configure that machine with Directory Utility with settings from the server, and the server responds just fine, the client sets everything up automatically for authentication and contacts. Everything seems to be normal until I log out and try to connect with one of the network accounts.The account will not login, the login window just shakes and does nothing. Odd enough, the login window tells that network accounts are available (captures are in Spanish).
When I login again as a local admin account, I check Directory Utility and when I look at the LDAP configuration, in the search & maps tab of the window, I find these two red registers (UserAuthenticationData and OLCLDIFConfig). I don't know if this is related to the problem, but this is where I get stuck and don't know where else to go...
Any ideas?

I was able to activate the debug log in the Leopard client machine, but I don't know how to look from another machine via SSH... Could you explain a bit the procedure? Is it possible to try to log in as a network user and then, after failure, log in as an admin account and check the log with Console?
Today I found out that Snow Leopard clients are also not able to log in... Similar problem in Directory Utility:
This is what I found in the log for this machine (tried to log in with two different accounts):
25/04/12 20:09:17          SecurityAgent[321]          User info context values set for XXX
25/04/12 20:09:18          authorizationhost[320]          Failed to authenticate user <XXX> (tDirStatus: -14103).
25/04/12 20:09:25          SecurityAgent[321]          User info context values set for YYY
25/04/12 20:09:25          authorizationhost[320]          Failed to authenticate user <YYY> (tDirStatus: -14103).
Couldn't find much about this in Google.
I'm starting to feel really disappointed about this!
(sorry for the delay in answering, been abroad...)

Cannot login with Network account.

Hi,
I am an experimented Mac user, but quite new with Snow Leopard Server.
I've just purchased the brand new MacMini Server.
I have configured my server with the name server.local and installed OpenDirectory as Master.
I wanted to try the network login, so I created a Test1 account in Open Directory. Then from my iMac I joined my server.local through System Preferences/Accounts/Options/... then I log off and try to use the newly created account test1.... I asked the system to change the password from first loggin... which works, but then I receive a message saying that I cannot log in for the moment... I tried everything but I just can't use the network account.
Any hints?
Cheers.

You should avoid .local at all costs when configuring an OS X Server.
.local is reserved for zeroconfig/Bonjour, and will cause conflicts.
There's an excellent tutorial for new users here
http://www.wazmac.com/serversnetwork/fileservers/osxserver_setup/osxserver106setup.htm
Jeff

Cannot login to network account (leopard client and server)

Up until now, I have used local accounts on my leopard server. I want to start experimenting with OD prior to implementing. I created a new user account in the /LDAPv3/127.0.0.1 domain, and have bound my leopard client to the server using directory utility. On the login screen, "Network Accounts Available" has a green button to the left of it. When I try and login to the server account, the login window just shakes. At first, I could enter the password and then it would prompt me for a new password. Trying to enter a new password would not allow me to login. I went back to server admin and disabled the "require new password" setting, (as well as the other good security policies)...
I have also reset the password in WGM, and made sure to disable all the security stuff there too...
Lastly, I have deleted the server in directory utility, rebooted, then added it back in, and rebooted again...
I still cannot login to the server account, the login screen just shakes
Does anyone have an idea of what settings and or logs I can check to try and narrow down what is going on?
Thanks in advance....

to close out the thread, I have working dns on my network, but I did not have dns enabled on my server. I enabled the dns service and entered just the info for my server, then assigned my server and client to use the server's ip addy as the primary dns server. Next, I created the home directory.
Once both steps were done, I was able to log in from my client to my server based account...
FYI-I found a document on afp548.com called "leopard server: advanced setup, rsync backup and automated reporting" that walks you right thru the process...Here is the link, it's a very useful doc....
http://www.afp548.com/filemgmt_data/files/Leopard%20Server%20Quickstart%20Guide. pdf
thanks again boomboom_uk and woVi, your suggestions were spot on....

One iMac cannot login to network accounts

We have a small network with Lion (10.7.5) Server running on a Mac Pro and a variety of 8 iMacs and Mac minis that use the server for file sharing and network accounts. The client Macs are running a mix of Mountain Lion (10.8) and Mavericks (10.9). They have all 'joined' the 'Network Account Server' using the 'Login Options' section of the Users & Groups preference pane. And, except for one iMac, all the clients can log into network (or mobile) accounts from the server -- both ones that have previously been logged into on that machine and ones that haven't. However, one of the iMacs will not log into a network account. There are a few local accounts and logging into them is no problem. But every time we try to log into a network account on this iMac, the login dialogue just does the 'invalid login' shake. It seems not to check the login credentials with the server.
As far as I can tell, this iMac is set up the same as all the others. It is certainly joined the Network Account Server and there is a green dot by the server name in the Users & Groups preference pane. I have removed and re-added the server from there a few times, and I've even reinstalled Mavericks on this iMac (it is running 10.9.2). I haven't been able to find anything that has helped to solve this problem. Does anyone know why one iMac would refuse to use the network logins from the server when the others work? Or what I can do to gain further information?
Many thanks.

On your client machine login screen, type in ">console" (without quotes) in the username field and hit enter. Try and login with your network account username and password. What error messages do you get in console?
Taylor

Cannot login to network accounts from client computer

Hi. I'm setting up my first OS X Server setup for home use...I'm not creating a very complicated setup, but I've been working through the setup one step at a time.
Right now, I'm just running the DNS, File Sharing, and Open Directory services. I setup a couple of Network User accounts, and I wanted to try using one of the accounts to log in to a Mac client (running Mountain Lion) on the network. When the machine first comes up, I get a message that says 'Network Accounts Unavailable,' and if I try to log in, I get the error message saying 'You are unable to log in to the user account "xxxxx" at this time. Logging in to the account failed because an error occurred.'
If I stop and restart the Open Directory service, I get the following messages in the Open Directory Log:
2013-02-15 09:11:01.017801 EST - Unregistered node with name '/LDAPv3/127.0.0.1'
2013-02-15 09:16:19.139744 EST - Registered subnode with name '/LDAPv3/127.0.0.1'
Not sure if this is the source of the problem, but these are the only messages that are coming up if I turn the Open Directory off and then on again.
If anyone has any experience with this, or any suggestions, I'd greatly appreciate it!
Thanks!
If it helps:
Running OS X Mountain Lion (10.8.2) with Server (v2.2.1)
Client Machine is a VMWare Fusion VM Running Mountain Lion (10.8.2)

On your client machine login screen, type in ">console" (without quotes) in the username field and hit enter. Try and login with your network account username and password. What error messages do you get in console?
Taylor

Cannot login into network accounts when there is no network connectivity

Hey guys
quick question here if anyone can help.
What has been done: backuped user's home folder, binded the mac to AD, logged in as the user's AD name, copied everything from the backup into the new user's home folder, users can work flawlessly.
What is wrong is when they leave the office, after a few hours they cannot login anymore to their AD username. Is there something i missed?
The network accounts do not appear in system preferences.
Thanks

On your client machine login screen, type in ">console" (without quotes) in the username field and hit enter. Try and login with your network account username and password. What error messages do you get in console?
Taylor

Can't Login With Network Account After Upgrade To Yosemite Server 4

I've been putting off this troubleshooting for a while now, and after trying everything I could find, decided to post.
- After upgrading my server to Yosemite with Server 4, and my MacBook to Yosemite, I can no longer login with any network accounts.
- I was on clean installs of Mavericks before the upgrade.
- I'm using SSL for the OD, with a GoDaddy cert, the same one that was working on Mavericks.
- I've tried removing the laptop's binding using the Users and Groups preferences dialog, which does not remove the laptop's entry from Open Directory, so I manually deleted the record on the server.
- I then choose to Join again, and it looks as though everything goes through, but I still cannot login with a network account. Also, when rejoining, it does not create a binding on the server.
- If I use the Directory Utility->Services->LDAPv3, and add it that way, entering the FQDN and checking Encrypt..., Use for auth and Use for contacts, it asks me for the directory admin username and password, and does in fact create the binding on the server, but I still cannot login. What's strange about that method, is that it forces the use of the IP address of the server, rather than the FQDN, like I entered it, which would of course have problems, because the certificate's common name is the server's FQDN. It does not allow me to change from using the IP address, graying out that field.
- I've also tried destroying the OD and restoring from archive to no avail.
It looks like many users have hit dead ends with this, with some having success by completely formatting and setting up a new iteration of the server, but I will not be doing that. However, I'll be happy to try any other suggestions.
Thanks for your time,
   -- Mike

     Okay, I've finally resolved the issue, thanks to the Apple Enterprise tech support team. I'm thinking they wouldn't mind if I share this information, but I can't guarantee that this will work on your system or, worse yet, degrade your system further. However, that's fairly unlikely, just make sure you have plenty of backups before you begin any troubleshooting session.
     So I was told to perform the following instructions, which I did, line for line. The part about closing Server.app seems a given, but I'm not sure why they want you to open Server.app at the the end (maybe taken out of context from some other instructions?). I did it anyway, but you should be able to begin testing, on a client workstation, right after rekerberizing is complete. I did, however, need to reboot my client, login as local admin, and then binding would proceed, and network users are able to login again. The engineer also let me know to expect an error, something like the following: "2015-03-11 21:58:38 +0000 Error synchronizing removal of attribute draft-krbPrincipalACL from record 72519e4c-7ac7-15e4-bd42-10adb1944cbc: 77013 result: 16 No such attribute" - this is apparently normal, and did in fact happen in my experience.
So here's the fix:
- Quit Server.app (don’t just close the window)
- On the Open Directory Server, execute these Terminal commands:
- sudo mkdir /var/db/openldap/migration/
- sudo touch /var/db/openldap/migration/.rekerberize
- sudo slapconfig -firstboot
- Open Server.app
And that's it. I did nothing else on my OD server, just logged out. Immediately tried binding on my MacBook client, it failed, I rebooted, tried again, it worked quickly, and I'm able to login with network user accounts again.

Cant login multiple network accounts on the same client?

Setup:
I have created a simple Lion Server on a new i7 Mac Mini. I have configured Open Directory in Master mode and have setup 4 user accounts. I have enabled the File Sharing service and checked the "Make available for home directories" option on the "Users" file share. I have configured each of the 4 user accounts to use this location as the home folder. I have connected my client machines (all OSX Lion) to the Network Account Server.
Problem:
I can log one user into the client machine, but when using "Fast User Switching" and logging on as the second user I get the following error:
"You are unable to log in to the user account "guestaccount" at this time. Loggin to the account failed because an error occured"
In the console if I search for that user account the related error message is:
11-07-31 12:30:54.993 PM authorizationhost: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] | PremountHomeDirectoryWithAuthentication( url=afp://inntaserver01.local/Users, homedir=/Network/Servers/inntaserver01.local/Users/guestaccount, name=guestaccount ) returned 16
Any thoughts as to why the Home Folder "mounter" failed in this scenario?

Historically you have never been allowed to use Fast User Switching to log in multiple network logins on the same client machine. This certainly applied with Tiger, Leopard, and Snow Leopard. I have not yet personally tried this with Lion.
I believe that the underlying reason for this not being allowed is down to how AFP volumes are mounted. The AFP mount becomes 'owned' by the user that triggers the login. With a network login the first user becomes the owner and this means subsequent attempted network logins are denied access to that share and hence cannot access their home directories.
With Tiger, Leopard, and Snow Leopard servers, one could configure network home directories to be shared via NFS instead of AFP. NFS gets treated a lot different in terms of mounting, and is done more at a system level than a user level. While again I have not personally tried Fast User Switching with NFS shared home directories, this approach is specifically recommended by the authors of AquaConnect (a Macintosh Terminal Server solution) in order to allow multiple logins on the same Terminal Server. This seems to be for the same underlying reason. Using NFS does certainly work for use with AquaConnect and also works for the competing iRAPP Terminal Server product as well.
Unfortunately, Lion Server while it can be made to run an NFS server, will not let you configure using NFS for sharing home directories. I have actually reported this as a 'bug' in Lion server.
Neither the authors of AquaConnect or iRAPP have actually tested this scenario with Lion server yet, but AquaConnect do plan to investigate it. It could make it considerably more difficult to use their products.
So in summary, using NFS to share network home directories in theory would avoid the problem and can be done with a Tiger/Leopard/Snow Leopard server, but cannot be done with a Lion server. It is possible however to mix Lion with older server versions. This might for some people be a possible workaround.
PS. A bonus side-effect of using NFS shared home directories was that this allowed badly written software like Adobe's applications which are otherwise notorious for having major issues with network logins and home directories to work without errors. As an example Adobe Acrobat Pro introduced a bug in version 7.0 which prevented it being able to print-to-PDF (one of the major reasons to buy Acrobat Pro). It tooks two years for them to eventually fix this in Acrobat Pro 8.1 (I know because I spent that two years nagging them to fix it and was a beta tester). Unfortunately they then reintroduced the bug in Acrobat Pro 9.0. Fortunately I discovered this side-effect got round the issue although a clunkier workaround was also possible for Snow Leopard clients by redirecting certain folder paths.

Can't login on iMac to Local Network accounts on server

I'm a volunteer at the Marjorie P Lee retirement community. We had two iMacs that were available for residents to use. We recently bought two more iMacs and a Mac Mini Server. The goal is to make it possible for residents to use any of the computers and have their files available.
I have set up the server and did the updates so the machine is running 10.9.4 and the latest update of the server software. I have enabled Open Directory and created a couple of Local Network User accounts for testing. I also enabled file sharing and Time Machine backups.
One of our older iMacs is running OS X 10.6.8. On this iMac, I went to the Users & Groups pane and under Login Options I connected to the Network Account Server. I got the green dot indicating that the connection was successful. I then enabled network logins. This worked; I am now able to login on this iMac to the local network accounts on the server.
I did exactly the same thing on one of our brand new iMacs. Again I got the green dot indicating a successful connection to the server. Unfortunately I have been unable to login to the local network accounts from this machine. When I try to login, the password shakes as though I had entered the wrong password.
What do I need to do to fix this?
Thanks for any help you can provide.
~~Dan

Most likely your Imac is using g or n to broadcast wirelessly while your router is using b. Solution update your router.
Greetings from Northern Ontario, Canada

Login with a network account in offline, possible?

Hello,
I have a question, since I had before snow leopard server. So the questions now belongs to the Lion Server, the dedicated server. And this is not a issue, but few questions to you and need to plan to setup to the dedicated server if there is a or few way to do!
Before I could login in with a network account from Snow Leopard server from my MacBook PRO. I think there is still possible to do it. But now today I just wonder is there a possible to login in with a network account in offline too, also no internet require? And what is the name for that? True, I don't know a lot of VPN and never used this, can you explain bit about it? But I know when I logged in, I used a Open Directory account and this was "virtual screen", no need to open the screen sharing program or whatever. It just was from the Login Window, also when you are turn on the computer. Do you know what name and know how to could use a network account in offline on my mac?
I just want to give you an example:
If I am sitting in a flight to Vancouver from London, then there I have no internet access in flight trip, so I just login the network account and this had before "cache". Of course need to login in internet first to get all informations and files in computer, so these are stored in my computer. Then I am working with a presentation during the trip. When I am arrived in Vancouver, then I am connecting to a internet, so the computer, also the network account will update to the server with these new files etc or of these what I did in during the flight trip.
Here is few question sticks from the text above:
1. Can I use a network account in offline?
2. Do you know any name for this method in Mac?
3. I don't know VPN, so what do this mean and containing what?

Hi
"1. Can I use a network account in offline?"
If I've understood you correctly, yes.
"2. Do you know any name for this method in Mac?"
There are several: Portable Home Directories, Mobility, Mobile Accounts etc:
http://manuals.info.apple.com/en_US/UserMgmt_v10.6.pdf
Page 215 onwards. Additionally Page 163 if Active Directory is involved.
"3. I don't know VPN, so what do this mean and containing what?"
You could have googled this yourself but here you go:
http://www.howstuffworks.com/vpn.htm
Essentially it's a means of providing a secure connection from remote networks such as your home or possibly a hotel to a specific location - such as your office or place of work - which allows you to access Servers and/or Services as if you were at that location itself.
". . . so the computer, also the network account will update to the server with these new files etc or of these what I did in during the flight trip."
Depending on where you are and the size of the files this may be a doutftul/painful experience and possibly not worth undertaking? However only you would really know? IMO it would make more sense to sync these files once you were back on the Server's network. It's possible you may benefit by signing up for MobileMe or iCloud?
HTH?
Tony

Can't login after Mountain Lion upgrade (Network accounts are unavailable)

I performed a Mountain Lion upgrade on a 2011 MBP running Lion this weekend. The Mac may have been set up to connect to an AD server with my user account, but I thought I had disabled that months ago... aparently not. I performed the upgrade at home not on the corporate network.
On first bootup after the Mountain Lion upgrade I'm stuck at the login screen unable to login with my local account or the admin account. I get the "red dot" next to the username field with the "Network accounts are unavailable" pop up. I'm plugged in to the ethernet network at work now... no luck.
I tried booting into the repair disk and repairing disk permissions. Still no luck.
Any ideas? I'd happily do a fresh install but I need to get a handful of files off the machine first.

No worries with the basic questions... it's important to cover all the bases. Thanks so much for the input.
- I'm trying to log in with the same username I would use to ssh in... so yes.
- I don't know if the account was a mobile account. The Mac was given to me configured about a year ago, configured to be on the domain. I since have used it on and off many networks without considering it was set up to be on a domain.
- Never had a problem logging into the machine before the mountain lion install, although to be honest it was very very rarely ever rebooted.
- I've plugged it into ethernet and let it sit for quite some time. It's still telling me Network accounts are unavailable and I'm unable to login with my personal or admin account.

Network account logins hang and spinning ball in Mavericks

Hello,
All of a sudden on Monday, 11/3/14, I started getting reports from Mac users that they were running into the spinning ball of death (SBOD) during login. The Macs in question are all running OS X 10.9 (between 10.9.3 and 10.9.5), and bound to active directory through directory utility, and the accounts being used to login are active directory/network accounts. The hardware is identical for all users as well (15" Macbook Pro, 16GB RAM, 2.0GHz Core i7 CPU)
I haven't been able to come up with much rhyme or reason to this yet as not all of my Mac users have been affected, and some are having to wait longer than others. I'm suspecting it is something with my Active Directory setup, but have not been able to find much useful information the the Windows Event Log. However, I'm not completely sure that's where the issue lies either because some of the MB Pros will sit at the login screen with the SBOD before the user has even tried typing their username.
What I'm trying to figure out is where should I be looking in Console for any hints at what might be going on or hanging up the boot process? I seem to have a lot of entries being created during the login process, but I'm not as familiar with Console as I should be for troubleshooting this so I'm hoping for some community guidance.
One thing I did find that didn't help was removing one of the search paths. That path does not exist on our machines so that isn't the issue.
Thank you in advance for your assistance

So I've done some snooping with Wireshark and the Mac is sending IGMP requests like crazy while it appears to be hung up. Almost non-stop outbound to port 11111. This only seems to happen with Macs that are joined to the domain. I'm using a Thunderbolt Ethernet adapter. It seems to have problems over Wifi though too, but haven't analyzed that traffic yet to verify it's the same IGMP requests. If I disable wifi and remove the Thunderbolt Ethernet from Network in System Preferences, then reboot, then the system seems to boot quickly.
I found another topic about Thunderbolt Ethernet and IGMP kernel panics, but I don't seem to be having any panics. It's just that the system will hang for 10 minutes before going to the desktop, and then possibly longer before it will show any icons.
Anyone have any ideas?

Can not login to a network account.

I dont typically support macs, but I have a client with an odd issue that I can not solve.
He has a Macbook Pro with OSX 10.6.
He logs in using his network account, authenticating against an OSX 10.5 server.
When he tries to to login, it appears as if he has a bad password.
His account is able to login just fine on other Macbooks in the company. (So I'm assuming his network account and password are fine)
Other users are able to log into HIS Macbook just fine, inclusing new accounts that have never before logged into this Macbook. (So I assume his macbook is communicating just fine with the OSX server)
When I go into the accounts list in the Macbook, his account is not there. It's missing.
If I try to create an account with his name, I'm told the account already exists.
We ran diskutility to repair the permissions on the drive, but this did not fix the issue.
Any ideas?
On the windows support side I would simply rebuild the users profile.. I'm not sure what the equivilent is on the mac side.

I'm having a similar problem. Could you let me know how to eliminate the mobile account using the command line?
Thanks!

Network accounts freeze at login

Similar Messages

Maybe you are looking for