unable to get network users working in server 3

I am having the very same issue with muliple clients. The issue seems to be related to x.local, and your domain name being convulted during the upgrade and sidelining your certificate, with no apparent way to bring it back.

Same here, thanks Apple, the only element that you charged us for and it doesn't work.

Unable to get any of the computers, ipads or anything to get logged into the server.

Server app also crashes if you try a password reset or create a new acount.

Thanks a lot Apple. Back to Microsoft Small Business Server!

There is no way to create a new user, it borks out.I cannot add users, I cannot make reasonable changes tocertificates. It crashes. There is nothing good here. What good is a server if you cannot log into it.

Hey Leslie,

Just a short check up as I'm also having trouble getting my server app back: we REALLY have to pay for Server 3.0?

thanks,

Rob

Hi Rob

Yes in the UK £13.99 for the pleasure of upgrading to something that doesn't work!

Les

Just tried the same, can't do anything.

I'm having a similiar issue, but not quite the same. I have a Mini Server and a Macbook Pro and I use server solely for network accounts. I upgraded both machines and now I can only be logged into one machine at a time. If I am logged into the Mini I get the shaky password on the MBP. I normally leave the Mini logged in 24/7 in order to serve content to my AppleTV's. So now I have the choice between a worthless MBP or worthless AppleTV's (4 of them).

Not happy about this at all. The only reason I upgraded was because I thought it was free. It wasn't until after I upgraded to Mavericks that I found out I had to pay for Server and now none of it works anyway.

freefall - It is insanely easy to get a messed up DNS FQDN: Apple configures the domain name incorrectly by DEFAULT. This only took me six months to figure out on Server 2.0 and another four months to track down and fix the cascade of related problems from that original setup error.

In the Server DNS, click whatever magic button gets you "Show All Records." This is the only way to see the differentiation between the domain and the hostname. Apple's default makes the *hostname* into the *domain* name (helpfully called the Zone in the Server app). While this is an identical FQDN either way, you will have problems the second you add any other machines into your setup, since they will use the *hostname* of your server machine as their *domain* name.

Example: FQDN myhost.mynet.local; hostname myhost.mynet.local; Zone myhost.mynet.local. The next machine added to the Zone is now FQDN myotherhost.myhost.mynet.local instead of myotherhost.mynet.local.

You begin to see the problems?

Enterprise support kept saying, "Look at the DNS," and they were right. If only they'd bothered to mention the Show All Records in the first place, I would have avoided nearly a year of headaches. (No, I'm not upgrading any time soon, either.)

I agree with Kristin119,

Most People who are new to O X Server don't realize how important it i to have DNS FQDN setup correctly.I've been running OS X Server since the days OS X 10.2 Server and did not figure out DNS FQDN had to been correctly configured til 10.5 Server. As always, never expect Server update to go flawless since errors will happen during an upgrade process especially if configuration files are not properly configured. And always expect migration bugs and issues that can happen in a server update. When Apple transitioned from OS 10.6.8 Server to 10.7 yes there was huge bugs and messes since they were transtioning to server.app and away from admin tools. However, 10.8 Server seems more stable however SMBX was a mess. However at least its rumored that apple finally is licensing SMB2 from microsoft.

Note: OS X Server is not really "No IT" needed.

As noted: always do a full backup people ...

I haven't upgraded yet on my production machine but plan on upgrading my test server so I can evaluate when would be a good time to upgrade my other clients who are on 10.8.5 server.

Also note,

People forget OS X Server will do a reverse IP lookup for the name of the server. Which means that if you dont have your DNS configured and just use your ISP DNS like say comcast, then your server will become the name of xxx.dynamic.comcast.net or something like that. So if you configure your DNS server settings say yourserver.yourdomain.com and make sure you have a reverse lookup of your local ip and also set your DNS ip in network system prefs as 127.0.0.1 which refers back to the server itself so the server can find it's name when it does a reverse ip lookup. Also note, your should keep your DNS server settings to only lookup only local networks and also make sure it does not do any zone transfers.

We do not need to be lectured on who osx server is intended for, its a $20 application, clearly its marketed to everyone.

Prior to the update all these services were working for all the people in this thread, now it does not. Providing support and technical knowledge is what we are looking for. If its complicated and technical bring it on, we are all enthusiast here, but please don't tell us how a $20 program requires an IT team behind it.

This is broken and unusable. Reverting back after wasting many hours. What a shame. What happened to "it just works".

Kiantech,

I'm not sure if you are directed towards me, but if you are... I'm sorry if I gave you that impression on that people needed IT. My intent was to have to people stop blaming Apple when some knowledge is needed which is why I'm providing some knowledge saying that the best thing is to start fresh with Maverick Server and get DNS FQDN configured correctly. I'm not saying that that Server is intended only for IT personal, but it does require some knowledge to get it to run correctly.

I know I did give bits of information here and there why it is important to setup the server with a FQDN since those are the hoops that I had to jump through when I upgraded from previous OS X Servers. At this point people should start all over and get FQDN configured with DNS.

---Note this is just a way of doing this

Anyway Backup your data... first

Then wipe out your drive

Install 10.9

after installing it.. configure your server with a internal static LAN IP (example 192.168.100.150)

download the Server App.....

don't run it yet...

If you have another computer or server with DNS server .. configure say server.yourdomain.net

make sure you do a reserve DNS so when it checks the 192.168.100.150, it can pull up server.yourdomain.net

Im sure there might be a easier way to do this but hey I have other servers.

Next configure 10.9 to use your other DNS server.

After that.... run the Server App so it can start configuring and so it can pull up the FQDN from your other DNS server.

Once you configure 10.9 Server and it's running.. Run the DNS Server and do the same configuration as you did on the other DNS server.

After that... figure in System Prefs in Networks the DNS address that it uses which is itself 127.0.0.1

I know this might sound a little bit confusing for some, but this one one of the possible first steps on getting it configured to work right with a FQDN.