Cannot login Network User - Please Help!

Question

Level 1

0 points

Cannot login Network User - Please Help!

I upgraded to Mountain Lion Server 10.8.2, and now I cannot login to my network account.

Here is the error I see in the Console application:

9/23/12 8:54:40.555 PM authorizationhost[8454]: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] | PremountHomeDirectoryWithAuthentication( url=afp://server.local/Users, homedir=/Network/Servers/server.local/Users/samir, name=samir ) returned 64

DNS is working fine, and the home directory is located at /Network/Servers/server.local/Users/samir.

There is no separate client machine...I have the one Mac mini that is running the server, and that's where I'm trying to log in as the network user.

Also tried using mount_afp, but that didn't solve the problem either.

I've spent the entire weekend trying to get this to work...this is very frustrating.

Please help!

Thank you.

-Samir

Mac mini, OS X Mountain Lion (10.8.2), Mac OS X Server 10.8.2

Posted on Sep 24, 2012 7:38 AM

Reply

Answer 1

Sep 24, 2012 5:31 PM in response to samirbajaj

Hey,

I also have this exact same problem, and spent a week fighting it and ran across serveral other posts about similar problems. I hope someone can help, there's a lot of people with this problem.

Here are the steps to REPRODUCE the problem mentioned by samirbajaj:

1) After a clean install of 10.8.2, install Server 2.1, Server has as manually assigned static IP, and acts as the

DNS server for my local network, using walla.foo.com (for example). All of this was setup in Server.app on the first run.

2) Enabled Websites service in Server.app.

3) Next I setup Profile Manager by clicking the "Configure" button in Profile Manager and following along until all the steps are complete. Then added "configuration profile signing" and enabled profile manager. Then, before enabling the Profile Manager service, the "Review Certificates" area in the "Next Steps" slidout is clean with no problems.

4) Then I enabled the Profile Manager service, and at this point the complains that "no SSL cert is set for Open Directory". Weird! So I went to Hardware -> Settings -> and clicked Edit for SSL Certificate. Didn't do anything, and then magically the SSL cert for Open Directory became fixed, really buggy. And it really is broken if you don't do this "step", because ldaps won't work until you do it. It's junk, anyway...

5) Went to File Sharing, clicked "Make available for home directories over AFP" for /Users, and enabled Filesharing

6) Next added a "local network user" slappy in Server.app, and set his home directory to /Users from the previous step.

6) At this point the server is setup. Trying to login on the server with slappy fails with the same error the OP gave.

However, I can login on the network account "slappy" from other client machines configured to use the server for network accounts. Wierd, so the problem is only with logging on to network accounts from the server. Does anyone know why?

Here's the same error I get:

9/24/12 7:07:52.468 PM authorizationhost[1418]: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] | PremountHomeDirectoryWithAuthentication( url=afp://walla.foo.com/Users, homedir=/Network/Servers/walla.foo.com/Users/slappy, name=slappy ) returned 45n

This is where I am stuck too. I would be AWESOME if someone could help us with this, there are many people with this same problem.

Thank you!!!

Reply

Answer 2

Sep 25, 2012 9:10 AM in response to ServerBurninator

I had the same issue and have tried all the reccommedations that have been posted without any luck.

As a last resort and using the KISS method (Keep it simple stupid) and shockingly enough, a simple repair of the permissions worked for me but I used the single user method and did not use the GUI utilities app.

ACTION TAKEN:

Restart and hold down command-S - screen will come to unix screen. At prompt type "fsck -fy" (no quotes and note the space between k and hyphen. Once it runs through it's process (give it 5 minutes) at the next prompt type in "reboot" machine will restart.

Give it a go and now try to connect to your server(s)

Reply