cannot login from client finder to mavericks server

Question

cannot login from client finder to mavericks server

Hi there,

I have read through all sorts of threads, but I couldn't find an answer to my question.

I have ugraded Server and Clients to Mavericks. Before everything worked flawlessly.

Now, when I click on the server icon in the finder of a client, finder doesn't connect automatically but shows the option to login as Guest.

When I change that to Registered User and put in my credentials, the window shakes and doesn't let me login.

If, however, I click on a link to a folder on the server that I have created before the upgrade process, I am logged in and can access all files on the server.

If I hit "Connect to Server" and put it what it says in the link, i.e. afp://servername._afpovertcp._tcp.local/share, I am also logged in correctly.

As far as I can tell, all settings on the server are OK - in any case, I didn't change anything coming from Mountain Lion server where it worked.

A different issue:

When Screen Sharing from Mavericks client to Mavericks Server, i get constant "re-connects" after which I have to re-type my password.

This happens at least 2-3 times while screen sharing.

I am connected via WIFI via the most recent time capsule.

Any thoughts?

Posted on Jul 24, 2014 1:53 AM

Reply

Answer 1

Linc Davis

Level 10

209,739 points

Jul 24, 2014 11:02 AM in response to Christian Innerhofer

You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.

The primary DNS server used by the server must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.

Reply

Answer 2

Jul 25, 2014 9:31 AM in response to Linc Davis

Hi there,

thanks for the suggestions concerning DNS - but everything was fine there.

I have, however, found out what the problem was:

Apparently, what was missing was a certificate. I set that to "self signed" and immediately everything worked as expected.

Maybe, that was me being stupid. But I really checked everything, read through every protocol etc.

Couldn't the server just somewhere say: I need a certificate?

Well, anyways, that solved it for me.

By accident, I also solved my other problem with the "re-connects".

I logged in from a different account from a different computer and there weren't any re-connects.

I then created a new account on my mac and again - no re-connects.

Seems like something got corrupted in my account.

Just weird that everything else seemed quite normal apart from those strange re-connects when I was screen sharing to my server.

-c.

Reply