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

Similar Messages

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....

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 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

Users Cannot login to Network Accounts

Hello,
I have a newly built server, Mountain Lion, but am having issues with my users logging in; an error is received. I have not made the server Live Because of this issue of course. The Users Home folders are on a different external Hard Drive attached directly to the Server. I am able to see the the hard drive and its a shared drive. I received no errors (sudo changeip -checkhostname) showed success. No mThe computers are joined in the Network Server Account, and
But here is the kicker, If i create a user using the Local Home Folder, and not changing it to the external hard drive I am able to login.
Has anyone had this issue? If so, what was your resolution, how were you able to fix this issue with the login issue?
Any Assistance with this, would be great!
Thanks
B

an error is received.
umm... including the error message might have been useful...
In either case, you don't state whether you've explicitly shared the external drive as a home directory repository.
If your users home directories on on this external drive, then you need to share that external drive (typically via AFP) so that the client systems/workstations can connect to the share as part of the login process.
Have you verified that the drive is shared, and that the AFP service is running? Can you manually mount the sharepoint from a remote system on the LAN?

My account Cannot login and say account restricted...

My account Cannot login and say account restricted ! i Never make payment
and my history payment ( You haven't purchased anything yet. ) !!!
what it's doing ?
My Skype ID : [Removed for privacy]

Well if you were born and raised here in the US or Moved to US and got citizenship you should have a Social Security Card many businesses Like Verizon, or Credit Cards companies require having a S.S.C and require giving at least the Last 4 of the Card to Verify who you are + they'll probably ask a few other security credentials..
I'd say for now getting what you had is not going to be easy at least until you get and established S.S.C. and or if you can prove any other Information Verizon may ask you for..
Hope that Helps Good Luck b33

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.

Trying to connect IMac to Lion server (network account)

Hello,
     I have been trying to get this to work for a few weeks now. I have 2 Imacs and a Macbook, i am trying to login to a network account. I did the step by step to set up my server. I can screen share and see all the shared folders. I have a network user in the work group, and when i go to users on my macbook, and say join the server, i get host not found, but the server is active.
     My network is a DSL modem ( in bridge mode), then to a time capsule, that is hard wired to my server and one Imac, everthing else is wireless. My time capsule hands out the Ip's, and a DNS server is running on my lion server.
     Am I having a DNS problem, I am not sure what DNS has to go where starting with the time capsule. Should i have my time capsule just server one IP to my lion server and have the server hand out the other IP's over DHCP?
     My goal is to have network user account on my server, and no matter what computer you use, you can get the same information. Then set up mobile account for when my macbook is not on the network.
     I setup profile manager, and tried to push my settings to my account, but it also fails every time.
     I tried to follow apple's doc's on this but I have luck with some things, and now with others.
    I am running lion server on a mac mini server.
Thank you,
     Justin

HI,
my experience is as follows:
1. You have to setup a home folder for network/mobile users with Server.app
2. Create a group for network users with the workgroupmanagement.app from serveradmin tools
3. Create users with correct settings under "preferences" in workgroupmanagement.app, especially "rules"
4. Put the users in the group
4. Set the appropriate permissions to the home folder and share it over the network with server.app
After playing around I could login from a MacBook Pro and synchronize the users library and complete home folder. After testing and restarting the machines (Lion Server is on a Mac Mini) I could relogin with the network/mobile user.
My problem actually is, that I could not login from any other Mac. Everytime the system told me, that there is a fault with login.
Before I want to login with the network/moblle user on another MacBook i logout the user form the MacBook Pro.
No luck :-(
I test it with other users with same settings.
No luck :-(
I integrate the MacBooks in the Computer settings in the workgroupmanagement.app.
No luck :-(
I hope this thread give answers the next days, because I need a working synchronize and account management solution for different users and machines :-)
Cheers
Ishan

Cannot login to any accounts anymore...

I have my latest MacBook Pro for over 2 years on one user account. Every time I boot up I just enter my password and get started. Today, however, I received a login with my computer name and nothing in the user or password fields. I have tried every combination I can think of and nothing works.
I have a system disk from the purchase, but it's damaged. I used another system disk (10.4) from my prior macbook, and booted. Tried to change account password but doesn't see my HD, only the startup disk (my current os is 10.5). I does see the HD and allow disk utility, etc.
Very frustrated I cannot login at all even though I know my admin/master password (not sure what the login or short name was though).
I am contemplating re-installing the OS back to 10.4 but obviously fear losing my apps/data, etc.
Please offer suggestions!

HI,
Go to /Library/Preferences and move the com.apple.loginwindow.plist file to the Trash. Restart your MacBook. If the login window is still a problem....
I have a system disk from the purchase, but it's damaged. I used another system disk (10.4) from my prior macbook, and booted.
The disc(s) that come with your Mac(s) are machine specific meaning one won't work on another.
You can run Disk Utility by booting in Safe Mode You can Verify the startup disk in Safe Mode, but not repair it. You need the install disc that came with the Mac you are having problems with to do this.
What is Safe Mode
Carolyn

Cannot login with a account created with workgroup manager on local box

Hi my name is richard and i recentgly acqquired from one of ,y friends a macbook pro with leopard 10.5.7 and I downloaded the server tools to it because workgroup manager gives me more control over user creation and the like.there are three issues that i am facing right now:
1) I create an account for a user "VERONICA MARS" short name vmars with a password of apple. when I try to login using that account the login window just sits there and shakes its head at me like no no no wrong cridentials.
2) using the same account vmars i try to reset her password using wgm and it says that it cannot reset the password.
3) when i try to create the account it tells me that the home directory cannot be created.
oh and heres a bonus one:
most of the time in wgm it takes forever to get from one tab to the next and ill have to do a force quit to restore my mkac back to normal.
if anyone can help with these issues please respond
thanks in advanced
richard johnson
mac fan for life

Please let us know the username of the account that is giving you trouble.

Cannot Login with Guest Account

I cannot login to OS X using the guest account I have enabled. When I try to login with the guest account, the window shakes no. How do I fix this?

see this thread, will probably solve your issue
http://discussions.info.apple.com/thread.jspa?threadID=1521487

Cannot login with mobile account when server is switched off

Hello all,
First of all, my condolences to the Jobs family.
OK. On with my problem. I apologise in advance if this has been answered before. I've trawlled through various boards and I can't seem to find an answer.
I'll try to keep it brief.
I've set up a mac mini with lion server. Done all necessary updates.
I have a lion macbook which is the client.
On server, created an Open Directory etc..
I created 2 mobile network accounts on the server. Set preferences etc.. Added both to workgroup.
Added the client to the domain in system prefs login options.
Logged into the 2 accounts on the client. All working well. Can see my mounts. Mobile accounts created successfully and syncing working.
So, the problem I have is, when I shutdown the server, my mobile accounts on the client disappear. Also, the login screen states, 'Network accounts are unavailable.'
I've been looking at this for a week now and it's driving me mad. I must have missed something - can anyone shed any light on this please?
With thanks, Paul.

oh well - gave up and reinstalled lion server.
GROAN!

Cannot login to secondary accounts; can't fast user switch

I am on a Macbook, 2 GB RAM, 120 GB hard drive, 10.4.8. Today, I developed a strange problem with logging in. I have auto login set so I log in automatically to my main account, which (thank God) works. However, if I access Fast User Switching to switch to a secondary account I have set up, called Test, the transition starts (the cube rotates) , switching to a solid blue screen...and never goes any further. I cannot seem to find any way to bring up the login screen on startup, either; I must allow my main account to boot up, and then try to switch accounts. If I turn off auto-login, I get the login screen, but login to the other account still fails.
If I select, instead, the Login Window from the Fast User Switching menu, I get that screen. But when I select an account other than my main account, and try to log in, I get that blank blue screen. I've waited many minutes to see if something will eventually happen, but no go. The only way to get control of my Macbook back is to hold down the power button until it shuts down.
I have run Tech Tool diagnostics and have repaired permissions (no errors found). I deleted my Test account, and redefined it; I also defined a second test account, one with admin privs and one without. No problem creating the accounts. However, when I try to log in to those accounts, the computer hangs on the blue screen.
I'm not sure when this problem began because I have not been using my Test account for a couple of weeks. A lot has changed since then.
Any suggestions, anyone?

More info: I turned off auto-login, and was able to log in to my test account. Then, I was able to use fast user switching to switch to my main account. I will try again restarting into my main account and see if I can switch to Test. This failed consistently before I posted here. Perhaps the "sense Mac guru" circuit kicked in and cured the problem. I'm about ready to turn in so won't post a follow-up until tomorrow. Right now, I need to use my two accounts to get the job done (a writing job with screen shots of a new unaltered account). Then, I'll go back to trying to see if the problem still exists when I log in to the main account first.

One iMac cannot login to network accounts

Similar Messages

Maybe you are looking for