unable to get network users working in server 3

I was able to fix my file shares mount (includine time machine) issue with the following terminal commands.

source: https://discussions.apple.com/thread/3742995?answerId=19362746022#19362746022

The only solution I could find was following Apple's instructions for the removal of the server here. Once I removed, I redid the server settings. I did not reinstall anything, but the re-setting the server was long and painful. Now we are again, after many wasted hours.

To add a little more to the expanding discussion, I have wiped my Mac Mini server and done an out of the box install of Mavericks then installed server with no errors or crashing. DNS, Open Directory all set with no problems very similar to my former setup. But, once I bind the client to the server, I am getting Network Accounts Not Available at the login screen on the Client and can only login using local accounts. Setup on all counts was very simple, nothing complicated, FWDN, no joy.

Les

I am in the same boat. After the fresh set-up I mentioned one post above, I can login to all accounts on the Mavericks server machine, and I can login on ML client machines, but the only one machine with the mobile account (Mavericks) cannot login, despite having logged in once successfully. As others pointed out, I had modified the "join OD server" setting in the users pref panel on that machine a number of times, and it is now giving me the certificate warning when trying to change. I suspect it is related to some certificate issue + an issue relating to joining the OD server. I do not believe it is a mobile account issue, as I cannot login to non-mobile accounts from that machine either. Once again, that machine is running Mavericks.

There is another issue that I have not been able to resolve. A few months back, I had experimented with a x.dyndns.org address. In the log, I keep seeing users logging in as y@x.dyndns.org with a host of warnings, instead of y@mydomain.net, and despite my best efforts, I cannot eradicate x.dyndns.org. I suspect it is somehow related to reverse look-up as others have pointed out, but the address that I inserted into dyndns.org is not my server static address. So, it is coming from somewhere else, presumably my own server. Any insights would be greatly appreciated. (I am not running server DNS.)

I solved by adding the server name in the hosts file on evety client mac.

It seams to be a problem with DNS, that does not let the client mac resolve the name of the server.

So do this in terminal

# sudo nano /private/etc/hosts

add at the end of the file this line with the IP of your server and its domain name

168.192.0.4 mac-server.local

save the changes and you are done.

Further update, just rebuilt my MacBook and put Lion on it, bound it to the server and rebooted, no problems network login. Does that confirm that it is an issue with the Maverick client side as the server must be working?

Tried on my Mavericks client, and did not resolve my issue, unfortunately. Nice thought though. Thanks.

So far I have done two fresh installs and found a few things that were problems. I hope this helps someone! I'm not by means claiming to be an expert however, these are items that solved my problems.

• The client's primary DNS server must use a DNS server that is either serving the FQDN or is serving ".local" domains.
• If the server is using an FQDN, the clients must use a DNS server that lists the domain as a searchable domain.
• Last (and CERTAINLY not least!) make sure that the home folders are being set up to be shared over SMB. Though this is a setting, the Mavericks clients seem to only look for the user and user folder when they're shared over SMB. This seems to be why the Lion & ML clients are logging into the Mavericks servers but not the Mavericks clients.

Well, there's my $.02 for now! Hope it helps someone!

Any movement anyone, still no login with clean installs!

I see that in th UK you get 30 support from Apple as Server 3 was a purchase. Has anyone raised the login issues with Apple before I do myself.

Did you mean 30 days from Purchase, my install has messed up my remote clients.

Hi leslie,

I can agree with what nick.leblanc suggested. Regaarding about using the Mavericks Server DNS for your clients. It makes a lot of sense in configuration of the clients.

I upgraded my test server and everything seems fine along with two of my clients for testing and no issues for login into network users accounts.

Reason why I had no issues login in was probably since my clients use the server as it's DNS and the your ISP. However it makes all perfect sense.

As a reverse test on what nick suggested. I set one of my mavericks clients using the ISP DNS and network login stopped working... even after I rebinded. I tested a mountain lion client using the ISP DNS and network login worked fined.

Regardless, it makes perfect sense since it seems mavericks is picky about the server name since even if you provide the IP of the server it does reverse IP lookup of the server. So if you are using your ISP DNS it might return some other name that's provided by your ISP for your broadband,.

LIke I've been saying FQDN and DNS setup is very important. I guess Mavericks clients now depends more importantly on it now for proper configuration.

Like Again it makes perfect sense when thinking about it when setting up home directories in Workgroup manager. Especially, when you have to setup the full path, server.yourdomain.net part of the full path......

If your clients are not using your server DNS then it can not find the path. For whatever reason, in Mavericks clients DNS is more important than in Mountain Lion clients.

If people are still having trouble logging as network users, let me know since individually I might be able to help with setup of your Server DNS and then get your clients to login using the Server DNS settings... etc etc..

Hi Rodvela,

yeah editing the host file is one way to solve your issue, but that's a lot fo work if you need to edit alot of clients.

Are you clients using the DNS services of your Mavericks Server?

If not, Edit your DHCP server (your router or if you are using Mavericks Server) to use the local ip of your Mavericks Server.

Next make sure the name of the server is configured right for your servr in the DNS services. etc etc

Now if you do this, there is no need for changing host files of each client.

@haykong

I'm having trouble with what I think is DNS since an upgrade to 3.0.

Perhaps you could help me out. I have one Maverick Network Machine that is behaving oddly, I can log in, sort of, but can't talk to the server and I'm not 100% sure it's bound correctly.