Q: unable to get network users working in server 3

I tried repairing permissions, reseting file sharining. Nothing working. Also the problem is causing my time machine to not work as well, probably because it can't mount the network share.

I'm utterly fscked off with Apple. This has been in beta for months, then when its released, they charge you for the privilge of it preventing any Network users to login to the server.

Thanks, just thanks. No really..

I am also having this issue after updating both client and server.  I see the following log message on the server when trying to log in as a network user:

no such entry found in hdb

Same here...

I've noted that the accounts still exist, and I can still access them using command line tools like finger, and even change the password (using passwd). Files owned by the accounts are still recognised with the old ownership, so the accounts are still live - they're just not logging in.

However I can't use the accounts for file sharing or logging in.

In the Server app, the "log in" tick box for each user is still ticked but its greyed out, and can't be changed. I'm not sure if thats because I'm logging into server app as local admin, rather than network admin - the directory administrator is of course a network account, so that's not working either!!!

Pretty stuck for ideas now...

Someone else posted somewhere I saw and implied that it seems to be a Mavericks client issue rather than a problem with the directory server itself.  That would support my case it seems, since I can access other clients using network credentials, but I do not have a ML client to test.  I had to force my clients to use cached credentials in order to log in.

There's something to this...

I can't log into ML machines with a network account, [presumably] as they can't access the home directory share (which is back on a Maveriks machine).

I CAN access files which are actually ON a ML machine using a network account which is authenticated from a Maveriks server.

Will Apple respond to this issue soon? I am having the same issue.  Our macs will not allow people to login from a network user account.  It works fine when I login as a local user.  This really should work considering it is a basic element of the software and it has been in BETA testing for months!

I'm having the same issue after an upgrade to Server v3 and Mavericks.  All clients running 10.9, same symptoms as everyone else except for one. Some of my users get the "shaking" password box indicating a wrong password while some are prompted to change their passwords. 

The one thing I have noticed is that my main system drive seems to have some funky permissions even after repairing. 

Also, in the Server app, under users, Home Folders show a "Custom" location. Even when choosing the correct home folder and clicking "OK" to save the config, it reverts back to "Custom".

Hi !

I have an iMac upgraded to Server 3 and Mavericks.

I have 2 macbooks which are "clients" of the iMac .

Macbook 1 (upgraded to Mavericks) : can't use network user access anymore ("shaking" password)

Macbook 2 (still ML) : everything is ok.

So, even 2 is not statistically ideal, it seems that the problem is on the Mavericks client!.

wajj82 wrote:

 

Will Apple respond to this issue soon? I am having the same issue.  Our macs will not allow people to login from a network user account.  It works fine when I login as a local user.  This really should work considering it is a basic element of the software and it has been in BETA testing for months!

I guess you never really done Apple Server Upgrades in the past. From Apple's Past history with Server upgrades, things always break during the first major ugprade. It normally takes time to fix it. Sometimes clean install works best.. and port over things. I always advise against upgrading a production machine and would be best to test it on a test server machine  before putting on production.

freefall722 wrote:

 

nick.leblanc wrote:

 

Also, in the Server app, under users, Home Folders show a "Custom" location. Even when choosing the correct home folder and clicking "OK" to save the config, it reverts back to "Custom".

I'm seeing this same behavior.

In Server App 2.2.2 and 10.8.5  thats normal to say "Custom" for home folders for network accounts. I'm not sure if some people correctly configured home folders for network accounts in Workgroup Manager.

For those that upgraded to 10.9 and Server App 3

have you tried downloading Workgoup Manager 10.9

http://support.apple.com/kb/DL1698

I think they forgot to update the webpage to reflect saying Mavericks.

Anyway... in workgroup manager under home per user

afp url should be set

along with user path

full path

Also you should have  FQDN for the server or things would not work right... just checking to make sure everyone has covered their bases with server setup.

freefall722,

       Sounds like in 10.8.X server you never had a full correct setup. I know things tend to break on upgrades or services when your server's name is not setup with a proper FQDN. And since you weren't running the DNS service might indicate that you did not have it setup correct.  OS X Server is very picky about having certain things configured right from the beginning like FQDN when setup up all the services from the beginning. When changing FQDN it can impact other services and some services will not function right if not correctly change at all points that need to be changed.

Have  you use workgroup manager 10.8 back when 10.8.5?

Anyway, if you haven't please download

Workgroup Manager 10.9 it'll give you more options in configuration of users.