"network accounts are unavailable"

Hi,
I just upgraded to Lion and now I cannot log in to my mac using my network account.  I checked and the computer is still joined to our windows domain.
Any ideas?  Nothing has changed on our network so I am assuming it's a Lion issue. Thank you for any help you can provide.

Okay, some more information from my side - I am running a W2008 R2 PDC where:
I am able to bind any 10.6 based machine and use the network login
It was the same for a 10.7 machine which was upgraded from 10.6 (AD was already configured on 10.6)
Having my first machine installed from scratch with 10.7.1, I am not anymore able to get the network login working. I read several articles describing this issue offering different solutions - without luck!
Here is what I tried:
Configure AD with standard Mac OS X tools:
- Joining the domain works without any issue
- Network Account Server in System Preferences shows green
- Login after restart displays 'network accounts are unavailable'
Did try to add custom Search path, static IP address, verified DNS settings and search domains, reboot after each step, un-/rebind to domain several times w/o 'create home directory' and 'allow administration'
Also downloaded CentrifyDC Express for Mac: it also did join well to the domain but as well as the standard Mac OS X procedure it does not let me login (ADCheck verifying the global parameters if the conditions are fine to be able to find the DC in the DNS etc. reports no issues)
From what I learned so far, it must be the configuration which is being written. Most probably I would guess it works fine if you once have created the setup under SL?
Personally I was not able to find such issues as "sometimes it's working, sometimes not...".
This is really annoying !
Any more ideas on that???

Similar Messages

  • Lion Clients 10.7.4 show network accounts are unavailable and server is not responding when binding to Snow Leopard server 10.6.8

    Hello,
    I am running Snow Leopard Server 10.6.8 and my clients are Lion 10.7.4.  While testing I had no issues binding 10.7.4 to our 10.6.8 server's OD.  I created a 10.7.4 image to push to all of our machines and in the beginning of last week I was able to push the image and get the machines to bind with OD and apply preferences on these machines through workgroup manager.  Towards the end of the week though this stopped working.  Now any time I bind a 10.7.4 client to OD it allows me to perform an authenticated bind and the machine shows up in workgroup manager but immediatley after binding the client the status jelly next to the OD server in the directory list is red and says "This server is not responding".  If I reboot the client I get a notification that "Network accounts are unavailable" at the login screen.  My preferences from workgroup manager are also not applying, which is my main concern because without workgroup manager my mac server is somewhat pointless as we use it for very little else. 
    I've since tried to bind a snow leopard machine (10.6.8) and this still is working with a green status jelly.  I've also built a lion machine from scratch, updated to the 10.7.4 combined update and am still getting the same issue where it shows the server is not responding when binding to OD.  I then applied the subsiquent OS update after the 10.7.4 combined update but the problem still persists.
    Is anyone else having this issue?  Any help would help me keep my sanity.
    Thanks,
    Dane

    Have you had any luck finding a solution to this?  The only thing I have found was to unbind and then bind without authentication.  Any help with progress on your end would be appreciated!
    Nick.

  • WPA2 Enterprise Network Accounts are unavailable

    I'm going to admit upfront that I am a Windows admin. I have attempted Google searches, Apple support searches, and I'm coming up without answers that are working. It's possible that I'm overlooking the answers in front of my face, but any help would be appreciated.
    Our network is WPA2 Enterprsie Authentication (LEAP) is with AD Username and password.
    I have bound OS X to AD.
    I can authenticate to the WPA2 network after local login.
    I have created IPCU profiles to include the WPA2 certificate and network ID.
    I have created OS X Lion "Server" profiles with the WPA2 information.
    I have set the directory utility Active Directory configuration to Create mobile account at login, do not require confirmation. Use UNC path to derive home drive location. Map UID, User GID, and Group GID to AD attributes. Allow authentication from any domain in the forest.
    I have set wireless to prefer only our WPA2 network.
    At the logon prompt, I am told "Network accounts are unavailable"
    Is it possible to setup so that at the logon prompt it can take the username and password and attempt to authenticate to our WPA 2 and process the AD account login (the parts applicable to OS X)?
    We have great success setting up the OS X machines with a local account "linked" to an AD account, but I'd rather have it function semi-close to the way our Windows machines authenticate, as network endpoints. I do realize this is sort-of against the grain of the Apple perspective, but these are not personal computers, so I'd like them to play nice with the business network.
    Anyhow, I'm probably missing something obvious, but would appreciate anyone being willing to show me the way.
    Thanks!

    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

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

  • 10.7.3 Network accounts are unavailable.

    I installed Lion on my work computer yesterday from a USB drive and I got the message that "Network accounts are unavailable".  Today I updated to 10.7.3 hoping that might do the trick and still get the same message.  Any ideas of how I should deal with this?

    Well then you will need to Log back into the networked resources. How you go about that I'm not sure.
    Look in Users & Groups, Login Options, Network Account server. you will have to unlock that section and type in your local password.

  • Network accounts are unavailable - OS X Lion 10.7.4

    My OS X Lion 10.7.4 Mac is successfully binded to my MS DC. However, every time doing reboot I keep receiving "Network accounts are unavailable" with red dot color and after few seconds it goes away.
    Can anyone experienced this kind of behavior and how to resolved this? I have searched around in google but no luck to get rid this annoying message.
    I hope anyone would share their knowledge.
    Thanks.

    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

  • "network accounts are unavailable" when not on the network

    Hello,
    I've just got a new Macbook Air via my work. I'm not at home, and when I boot up, I'm getting "Network accounts are unavailable". Does this mean that I need to be on the work network to login ?? I can't seem to log in.
    Cheers,
    Marc.

    It sounds like your company has a domain that they set your computer up on without creating you a mobile user account.  You wont be able to use your work credentials as you don't have access to the domain from home.  Do you know a local user that you can log in as?  If not you will need to wait until you get back to work. 

  • Mountain lion server network accounts are not mounting network home directory, rather its creating a blank local directory

    I have set up a scratch mountain lion server with open directory.  copied over old user account directories and added my users that match the directory ids.  Currently if a networked user logs into a networked computer, instead of mounting the network home directory, its creating a local home directory.  suggestions?
    thanks,
    Dave

    Additional info: it appears that certificates are not working either: setting up ical: "the certificate for this server was signed by an unknown certifying authority."...

  • Network Account Unavailable

    On login window it tells me network accounts are unavailable. I can log in to local accounts and the computer is connected to our network but I just can't login to the network accounts. I repaired permissions and ran Disk Warrior to no avail. Any ideas. Thanks

    What Interfaces in Network>Show:>Network Port Configurations are checked ON?
    What IP and such are shown in Network>TCP/IP tab?
    In System Profiler>Networks, what is shown as active?

  • Network Accounts Unavailable but not on all machines

    Hi
    I have a client with a Dual processor XServe G5 running 10.4.8 server, their Macs are also on 10.4.8 and they are setup with Network Home Directories.
    In the last few weeks, I have had intermittant problems with a couple of the machines that don't seem to be able to log onto their accounts in the morning when first switching the machines on. Clicking on the status line in the login window in this instance shows "Network Accounts Unavailable".
    To solve this I have been logging in remotely as admin to the machine(s) in question, deleting the LDAP configuration in Directory Access, re-configuring, rebinding and then logging out. When doing this, the Network Accounts are then shown as available and the user can log in normally.
    Interestingly, when I get to the point of deleting the configuration, it says that it can't contact the LDAP server, and asks if I want to force a disconnection and I guess this is why the user can't get to their network account in the first place, because it can't see the LDAP server?
    However, other machines on the network, don't have this problem and can log in after a restart or shutdown with no problems. Why would it do it on just a couple of machines? Could it be the network switch?
    None of these machines are connected via a wireless connection, they are all hard wired into a small 5 port switch, which in turn is wired back to the main switch in their rack and this is a 10/100 Allied Telesyn unit.
    Any ideas as to what I can do to resolve these intermittant issues. It's becoming a pain to have to resolve this every morning for the client when they come in.
    Thanks
    Paul
    PowerBook G4 17"   Mac OS X (10.4.8)  
    PowerBook G4 17"   Mac OS X (10.4.8)  

    Hmm, seems I solved it by tweeking with the broadband router.
    (I fed it with a backup DNS, and reactivated DoS firewall)
    Does neither explain why another PC worked well alongside this one,
    nor why another OS gave other results.
    Maybe just a broadband router inconsistency, anyway, l'll consider this fixed for now.

  • New Snow Leopard Server, Slow Network Accounts

    We've installed Snow Leopard Server on our XServe quite a while ago and since then all users who work with network accounts are complaining about serious perfomance issues. These issues are for instance logins which may very well take up to several minutes, or applications like Adobe InDesign which take their time to load files from the users network shares.
    Our System consist of:
    1 XServe running OS X 10.6.8 Snow Leopard Server
    48 iMacs running OS X 10.5
    1 Windows Server 2008
    The XServe serves as an OpenDirectory and Fileserver, while the Windows Server delivers DNS.
    We have created ~500 users and 25 groups in the OpenDirectory. All user files are located in their roaming profiles on the Xserve. Additionaly every user has access to one group folder, which is located on the Xserve as well.
    All group folders are Sharepoints and added to the dock of all users in the appropriate group.
    I have already checked DNS settings, user accounts, network connectivity in general, network load during peak hours, the ACLs on the group folders....
    By now im simply out of ideas what my cause the problem, let alone how to solve it.
    Any hints are greatly appreciated.

    Are you using any redirections?  Redirecting the cache folder from the network home to the /tmp should improve speed.  Use this white paper from apple.  http://images.apple.com/education/docs/Apple-ClientManagementWhitePaper.pdf The redirections are on page 53.

  • Using Final Cut Express and Network accounts

    I am having problems launching Final Cut Express when opening the program logged into a network account.
    It works fine when i am logged into administrator, but when i am in another account it will not launch
    Thanks
    Dave

    My general experience is that FCE either doesn't start or doesn't run properly unless you are logged in under an administrator account.
    Tom Wolsky advised one time that after installation FCE had to be run once from an administrator account and afterward it would run from regular accounts. That hasn't worked in my experience.
    As far as network accounts are concerned, are you using an xServe or a Mac with OSX Server installed, and workgroup manager? FCE will need to be installed on the local machine, not the server, and the network accounts won't necessarily work with FCE.

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

Maybe you are looking for