"Network accounts un available"

Hello Please, am stuck i have added my mybook pro to our windows domain, Now i cannot login. Be using the domain account or the local administrator accounts. The error generated is "Network Accounts un available" Pleeeaaaaseee help

I've looked at my system logs, and the difference between logging in connected to a wired and wireless network.
I seem to have an issue with keys on the wireless network.
Aug 7 08:46:24 MSM52 /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: SecKeychainItemCopyAttributesAndData() = -25308 (User interaction is not allowed.)
Aug 7 08:46:24 MSM52 /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: SecKeychainItemCopyAttributesAndData() = -25308 (User interaction is not allowed.)
Aug 7 08:51:07 MSM52 /System/Library/CoreServices/mcxd.app/Contents/MacOS/mcxd: DSOpenNode(): dsOpenDirNode("/LDAPv3/10.10.10.23") == -14002
Aug 7 08:51:11 MSM52 kernel[0]: AirPort: Link Active: "mywireless" - 000d54a07d1c - chan 4
Aug 7 08:51:11 MSM52 configd[42]: SecKeychainFindGenericPassword err= -25308 ( =0xffff9d24, secErrStr=User interaction is not allowed. ) (current= mywirelessnet)
Aug 7 08:51:24 MSM52 /usr/sbin/AppleFileServer: TIME-CHECK: NSLXStandardRegisterService took 1.851997 seconds!\n
Since the key piece of information, well in English anyway, seems to be "User interaction not allowed." Any ideas how to resolve this?
I've opened Keychain Access, there does not appear to be anything bad about the entry for my wireless network. As a test, I changed "access control" to be unrestricted, but still no luck.
I then deleted the entry the entry in Keyword Access, and still see the same behavior.

Similar Messages

Log in shows 'network accounts not available'

on my desktop my login window has a red radio button and a tag that says 'network accounts not available'
Anyone know what this means?

It thinks it's supposed to be booting from a Server, have you ever used that?
Might you have pressed Option+n?
http://support.apple.com/kb/HT1533
Try rebooting & hold just the Option/alt key to see if you can select your boot drive.

Lion Server network accounts not available after 10.7.4 update

I installed the incremental update for Server 10.7.3 to 10.7.4, and now my network accounts can't log in. That would be all users of the machine then. How can I fix this?
Unimpressed!

Exact same thing happened to me on my 2010 MacBook Pro, running Lion as well. Updated to 10.7.4 and whammo, no more DVD drive. Tried numerous discs and the computer just mulled over whether it was going to play the discs for a few attempts then spat them out. All the discs I tried were in perfectly good working order.
Just saw this thread, but created one of my own before (https://discussions.apple.com/thread/4026857). Still waiting for some help....

Network Accounts - Red Dot disappeared?

Afternoon all
We have 12x iMacs on an Active Directory network. We have the usual 1-2 minute wait after boot before network accounts are available - however 10.8 gave us that red dot that clears once accounts are available, but in Mavericks there's a pop-up warning that disappears, but no red dot, so you can't tell when the problem has cleared and when you are able to log on.
Is this an option or has it been removed entirely?
Thanks, Tom

I do believe it's fairly normal... one of the crazy things about a fully cooperative multitasking OS, it can try to connect before the Interfaces are up & ready.
Found a work-around. This command adds a delay, in this case 45 seconds, before displaying the Login Window.
defaults write /Library/Preferences/com.apple.loginwindow StartupDelay -int 45
If the Login Window UI detects that the network servers are available when it starts, it will skip the delay, also if network servers become available before the delay expires, the Login Window UI cancels the delay and displays.
Kent
http://discussions.apple.com/thread.jspa?messageID=10338123#10338123

Slow network accounts

setup:
Mac Pro
10.5.6
Active Directory - accounts
Open Directory - group settings
Problem:
When I boot up my machine it takes a while before all netowrk accounts are available. It sits with a yellow ball stating "Some network accounts available" for about 15-30 seconds before switching to green and stating all network accounts are available.
Anyone else see this? Why might it be slow? There isn't anything logged that can help point me in the right direction to optimize things unfortunately.

Make sure you are using the same DNS & NTP server on the Mac as the Active Directory server.

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

Network Accounts Available Indicator

I need to better understand the "Network Accounts Available" indicator light. We have eMacs and put in new Cisco GB switches. When we start from a cold boot, it usually takes about 3 -4 minutes for this indicator light to turn from red to green. If I turn AFP off on the XServe, it still takes the same amount of time for this indicator light to change but if you try to log in, you cannot do it because AFP is turned off. I understand that the users cannot login because AFP is disabled. We tried to force the switch and the workstation to 100baseTX / full-duplex and there were not any consistent changes in time.
So my question is, what exactly is it telling us? Is it the time it takes to establish a connection from the eMac to the server? Is it the amount of time it takes to auto-negotiate to the first switch that it is connected? Is it an issue that the NIC card is having trying to auto-negotiate with a Gigabit switch? I really need some input because we are starting to put more Gigabit switches in our schools and we still have a lot of eMacs.
All responses are more than welcome.
Our hardware is:
eMacs - OS 10.4.6 - 10.4.11, 256 or 512 MB RAM, 1GB PPC processor
Switches - Cisco 3560, 4500, & 6500
Server - OS 10.4.11, 2 GB RAM, PowerPC G4 processor

Is the Ethernet Interface dragged to the top of Network>Show:>Network Port Configurations? That is the search order for connections.
Do you have proper DNS Servers & Search Domain entered in the Network>TCP/IP tab for Ethernet?

Lion 10.7.3 and Kanaka 2.7 "no network accounts available"

Server is OES2SP3 on SLES10.4. Kanaka 2.7 installed and configured,
OS10.6 clients have no trouble authenticating via plugin and all
expected volumes mount.
On iMacs running OS X 10.7.3, installing the plug-in and configuring
it results in a succesful authentication test in the directory utiliy.
However, on bootup the login screen shows a red flag next to the
username and the message "network accounts are not available".
If we authenticate as a local user, command-k will successfully
connect to the server and mount volumes as desired. I have checked
afptcpd.conf on the server and verified that AUTH_NAM is set to DHX2
Any suggestions on where to look next?
Thanks,
DG

DeVern,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Some Network Accounts Available

I am having 50 Mac Pro with 10.4.11 and 2 OD servers with 10.4.11
The server is bind to the AD of the company for a single login, I can see the users name at the login window but when users key in the password it just doesn't login. But out of the 50 only one mac pro is able to login with the users password, the rest it just shake and return to login screen. The status from the login screen is a yellow dot - Some Network Accounts Available. On eof the server is also getting it . I have try to unbind and rebind it but no luck.
Please help!! urgent

Hi Lookout,
Try to change the following 3 configurations:
1. Turn off IPv6 under TCP/IP of the Network Preferences
2. Change the Search Policy under Directory Utility. Make the Active Directory come first before the LDAPv3
3. Also under Directory Utility, go to Services tab, open up the LDAPv3, add the OD server by using IP address instead of server name.
I can't say the above will fix the problem. But this is what the Apple engineer told me to change. And after all these changes it seems to be working fine. I am still randomly rebooting, logging in and out to test it to see if it works constantly. The Apple engineer is also working on her end to research more. So there is no final solution yet. But if you could, please do the same as I did and see if that helps. Let me know so I can forward your status to the engineer also. Thanks and write more soon.
Message was edited by: RabbitSF

Network accounts no longer available after server reboot

Mac OS Server 10.4.10
Open Directory Master running DNS. DNS is working properly and the system had been up and running for about 4 months without any problems and it had been restarted periodically for software updates, etc. I restarted the server the other day just to do so, and when it came back up, none of my network accounts were able to log into the server. The "Other" option at the login screen is actually missing from the client. I am able to log in locally to the client machines and access network shares with OD accounts, so the usernames and passwords are still functioning as they should, I just can't use them to log onto the client computers. I have the following errors in my ldap log when I start up a client machine:
Sep 8 11:40:19 macserver slapd[55]: SASL [conn=20] Failure: GSSAPI Error: Miscellaneous failure (No principal in keytab matches desired name)\n
Sep 8 11:40:19 macserver slapd[55]: SASL [conn=20] Failure: no user in database\n
Sep 8 11:40:29 macserver slapd[55]: SASL [conn=24] Failure: GSSAPI Error: Miscellaneous failure (No principal in keytab matches desired name)\n
Sep 8 11:40:29 macserver slapd[55]: SASL [conn=24] Failure: no user in database\n
Sep 8 11:40:30 macserver slapd[55]: SASL [conn=28] Failure: GSSAPI Error: Miscellaneous failure (No principal in keytab matches desired name)\n
Sep 8 11:40:30 macserver slapd[55]: SASL [conn=28] Failure: no user in database\n
The fix for this is to restore my OD database from the archive backup that I make every other day, but I shouldn't have to be doing that every time I may need to reboot my server. I did not make any configuration changes to the server before this started happening, so I can't point to any one thing that would lead to this type of behavior. Any help would be greatly appreciated.
Thanks

Hi… I don’t think there should be any such limitation for the file transfer wirelessly. However it can be issue, as you wired is connect at a speed of 100 Mbps and wireless connects to the max at 54 Mbps. Try to upgrade the firmware. Also try reducing Fragmentation Threshold and RTS threshold by 40 each under advance wireless settings on the router. Go to www.speedguide.net, and download the TCP optimizer. Try reducing the MTU of your wireless adapter. Please Revert Back, even if this resolves your issue.

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

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

Lion Server network accounts not working on some computers.

Hello all -
I'm currently having an issue with network accounts working on some Macs but not others. I have a Mac Mini and a MacBook Pro. The Mac Mini works fine and I can login and sync my network account with the server just fine. However, I cannot connect to it from my MBP.
When I try and connect I get an error that says "You are unable to log in to the user account "xxxx" at this time. Logging in to the account failed because an error occurred."
If I login through console (by typing in ">console" in the username field) I get an error that says the user does not have a home directory...
I have searched numourous other forums but I have not found a solution that seems to solve this problem. I have unbound and re-bound my client to the open directory and I have restarted file sharing. Neither has solved the problem. I have a feeling the issue originates somewhere on the MBP since I can log in to the Mac Mini without any problems.
Anymore suggestions?

Thanks for your suggestion, SolidWood. Unfortunately it didn't help.
After a 90 minute phone call with AppleCare, this issue has finally been resolved. Here is what the solution was. Turns out it was pretty simple but it took a while to find it.
First we created a test user and left the home folder set to Local Only in the Server App. I was successfully able to login with the test user on both clients but since there were no mobility preferences set, it was pretty basic.
Then, we removed the Users sharepoint from file sharing, turned off file sharing to disconnect any users, and restarted the server. Then we created a new folder on the Server HD with a random name. We chose Darron. We created a new sharepoint in file sharing (with it still turned off), and shared the new folder called Darron. Double click on the sharepoint and scroll to the bottom and check the box that says "Make available for home directories over AFP". Then we restarted file sharing.
Then we opened Workgroup Manager, clicked on the problem user in the left sidebar, clicked on the Home option at the top, and there were three things listed:
     (None)
     afp://servername.com/Users
     afp://servername.com/Darron
Then we removed the Darron sharepoint from file sharing, and found that it was still listed as a home directory under the problem user.
This was the root of the problem. The system didn't know which path to use as the home directory.
Sooooo...
In the server app, we opened the Directory Utility (Tools in the menubar, Directory Utility). Clicked on Directory Editor. Authenticate to the directory using the diradmin login. Changed view settings to match this below:
In the left column, there were two paths listed for home mounts. We deleted both of them, saved changes, and closed directory editor.
Then, we restarted workgroup manager and both paths had been deleted from the users home listings. This was begining to solve the problem.
In the Server App, we recreated the users sharepoint, made it available for home directories, and restarted file sharing and workgroup manager. Now only one path is listed for the home folder for all the users.
This solved my problem of not being able to login on the MBP. The system synced the home folder and all was well. On the Mac Mini, I had to delete the problem account, un-bind from the network server, re-bind, and recreate the account. Now both clients are sycning perfectly and all is well.
Thank God I bought AppleCare! Thanks to everyone else for their help and suggestions.
As a recap, the problem of not being able to login to the MacBook Pro was caused by having multiple paths to the multiple home folders. These rogue paths were added somewhere in the troubleshooting process to try and recreate the home directories before I called AppleCare. To solve this, we had to remove the directory listings from accounts using Directory Editor, remove and recreate the users sharepoint in file sharing. The syncing problem on the Mac Mini was also created when multiple paths were introduced. The system didn't know which files to use.
Taylor

"Network accounts un available"

Similar Messages

Maybe you are looking for