Originally posted by Steve Bosell:
I have been messing around with OS x.3 server latley. I was able to set up ldap users fine with home folders on the server, however how can I create an ldap user who logs in with a home folder on the local drive?
thanks
Hi, is your problem related to mine, see the text below that I posted some time ago.
-Stefan
Here is my problem (and partially, others have seen similar problems):
- one OS X Server 10.3.4
- many clients with 10.3.4
- home directories are primarily on **clients**
- clients share their home directory disk with AFP (guest access, privileges
__seem to be ok).
- OS X Server has each client's home directory disk as automount point in LDAP
__as well as the proper network mount info for each user
- automout works fine across all clients (and also the server)
- console login works fine on each client for any home directory, no matter
__on which client (or server) it is located, EXCEPT ....
- THE PROBLEM: console login on the client that physically has the homedirectory
_______________of a user does not work for the user!
- the syslog error message is:
Jul 1 19:40:13 localhost loginwindow[513]: MountURLWithAuthentication returned 65
Jul 1 19:40:13 localhost loginwindow[513]: [Login.m:1090]: -[Login mountNetworkHomeWithURL:attributes:dirPath:usernam e:] returned -2
and then the system goes back to the login window.
On the screen, the error message is:
"You are unable to log in to the user at this time. Logging in to the
account failed because an error occurred. The home folder for the user
account is located on an AFP or SMB server. Contact system admin. for
help."
So what happens seem to be relatively clear:
- on the client with the physical home directory, the AFP mount of the
__home directory fails (as the local disk cannot be AFP mounted two times),
__and the login fails, too.
- on a client where the home directory is on a remote machine, things are fine
__as the AFP mount make sense.
BUT all this was also true under 10.2, and everything worked here. After all,
the user's home directory is present with the correct path.
Does anybody know how to fix this? (of course, add a local account for
each user that has the home directory on the local machine -- but this
is a pain for a large network).
Interestingly, home directories on the server DO NOT have this login problem,
thus, there is a proof that the problem is fixable.
Best wishes,
-Stefan