Network users can't login

Discussion in 'Mac OS X Server, Xserve, and Networking' started by justin071894, Aug 30, 2012.

  1. justin071894 macrumors newbie

    Aug 30, 2012
    I'm trying to setup about 9-10 iMacs all running OS X Mountain Lion to an iMac running OS X ML Server. The server is named "pubserver.local" with an IP address of I have some of the client machines connecting "pubserver.local" and others to the IP address for network authentication.

    I seem to be running into problems somewhere, because when I can login from the server, however when trying to login from a client machine, I receive an error saying " You are unable to login to the user account "jadkins" at this time. Logging in to the account failed because an error occurred."

    I have the network folders stored on the server's hard drive and it should mount them on login. There shared via APN.

    Any ideas? Should i just reinstall ML and then install OS X Server again?
  2. JonyHolt macrumors newbie

    Jul 13, 2011
    Fresno, CA
    Typically this is a permissions issue. However if you open the console log on the machine (after attempting to login multiple times login to the administrator local account and open the console app.) There it should read exactly what the reason for is.
  3. modernlifeiswar macrumors newbie

    Jul 17, 2012
    This is a problem related to DNS, which is crucial to Open Directory and network accounts.

    As root:

    bash-3.2# changeip -checkhostname
    Does it say:

    Primary address     = XXX.XXX.XXX.XXX
    Current HostName    = XXX.XXX.XXX
    DNS HostName        = XXX.XXX.XXX
    The names match. There is nothing to change.
    dirserv:success = "success"
  4. justin071894 thread starter macrumors newbie

    Aug 30, 2012
    Primary address     =
    Current HostName    = pubserver.local
    The DNS hostname is not available, please repair DNS and re-run this tool.
    dirserv:success = "success"
    How do i repair the DNS?
  5. guzhogi macrumors 68030


    Aug 31, 2003
    Wherever my feet take me…
    I get those errors at work as well. The IT guy in charge of servers & accounts says it's a Kerberos issue. Wish I could be more help, but I don't have access to that kind of stuff (above my pay grade).
  6. switon macrumors 6502a

    Sep 10, 2012
    Change hostname...


    It appears that your DNS server is messed will need to straighten it out first before proceeding. If you think that your DNS server is setup correctly, then try stopping/restarting it.

    I had this same problem many blue moons ago (under Leopard Server, actually - I now use ML OS X Server), and I found that if I changed the hostname and IP that this somehow forced a reset of the caches thereby resetting the DNS. To do this, you might try:

    ...stop your DNS server...
    sudo changeip -checkhostname
    --> returns the error you listed saying that the DNS hostname is unknown
    sudo changeip pubserver.local pubserver.private
    host pubserver.private
    sudo scutil --set HostName pubserver.private
    ...and now make sure that the DNS server is setup properly for the new hostname/IP address, then restart the DNS server...

    You can then reset the hostname/IP address back to the original ones, if you wish.

    DNS must be setup and operating properly before you can get Open Directory to work. Personally, I would try OD first without Kerberizing it initially. Once you get OD working so that it allows your network logins, then you can go back and Kerberize it.

    Good luck,
  7. RyanelRichie macrumors newbie

    Jan 2, 2014
    I'm having this issue but only with 4 users out of about 50. They can log in on their computer but no one else's. While the rest can log into any computer. Could the DNS server only affect a small group while the rest are fine to log in?
  8. alexprice macrumors 6502a

    Jan 8, 2005
    Certainly that DNS will be an issue.

    But also, make sure you have given users service access for 'File Sharing' in the Server App. Its under Users/Groups as the option to 'Edit Access to Services' within the cog wheel.
  9. mus0r macrumors regular


    Mar 27, 2005
    OS X Server has always been a PITA about DNS. Honestly, if the server doesn't need to connect to the internet for services, I'd just give it a fake FQDN and edit the host file so it resolves itself. I've had nothing but issues with services in the past when the server's name was anything.local.
  10. Rog210 macrumors regular

    Mar 23, 2004

    I'm having this issue too. It seems Apple has really dropped the ball here. I'm a little embarrassed I recommended a client go with a Mac solution for his small business now. Really amateurish and pathetic that this hasn't been addressed as a matter of urgency.

Share This Page

9 August 30, 2012