Home › Forums › OS X Server and Client Discussion › Questions and Answers › Tiger server / networked home directories
- This topic has 11 replies, 5 voices, and was last updated 18 years, 2 months ago by
deemery.
-
AuthorPosts
-
July 26, 2005 at 12:49 pm #362482
fleecy
ParticipantBrand new XServe G5, XServe RAID, Tiger Server 10.4.2, Tiger Client 10.4.2, Windows 2000/2003 network
I am trying to setup networked home directories. I pointed Tiger Server to my XServe RAID as its Users folder, setup a test account with a networked home pointing to this shared path (afp://myserversname.domain/Users).
My Tiger Client uses DHCP from the Windows network to get an IP address and a DNS server. My server’s DNS address resolves without problems when I use “connect to server” to mount AFP volumes.
I used Directory Access on the client to add Tiger server as an LDAP source and can logon to plain accounts from OD without problems. However, if I try to logon to my test account (with networked home directory), I get an error message stating that the client couldn’t logon because the home directory is on an AFP or SMB server.
What am I doing wrong?
July 26, 2005 at 12:54 pm #362485fleecy
ParticipantI forgot to mention that Tiger server allows me to use “Connect to server” and mount the Users folder to my desktop when I use my test account info as loginID/password. When I do this, the Users folder gets updated by the server to include a home directory for the test account. Trying to login again using that test account still gives me the same AFP/SMB error message, though.
July 26, 2005 at 2:36 pm #362491fleecy
ParticipantThanks for your help!
I did enable network mounting to my LDAP server (127.0.0.1/LDAPv3) using AFP as the protocol and User Home directories setup as “Use for”. My test account is also in 127.0.0.1/LDAPv3.
I also enabled Guest access for it, in case it helps. I still get the same error message.
September 26, 2005 at 5:47 pm #363363fleecy
ParticipantHere I am again…
I’m still unable to use networked home directories. I reinstalled the whole thing, and I still get the same results.
My Users directory is setup properly, and I can select it as a user’s home location in Workgroup Manager, but trying to login results in the following error :
“the home folder for the user account is located on an afp or smb server”.
I tried this with multiple new accounts on the server. Setting the user account’s home to “none” in Workgroup Manager enables me to login with that account, but the home is on the local hard drive, then.
Help!
September 27, 2005 at 8:05 am #363370littlemonkey
ParticipantHi,
I was having the same issue and I solved it by setting up in Workgroup Manager to mount my NHD on a ‘custom mount path’
/Network/Users
Basically it will create a new folder on the client Network directory of the same type as ‘Servers’
I was experiencing this issue with 10.4.1, solved it since with the trick above, but I was thinking it was solved with the 10.4.2… Apparently not…
Remember to restart the client before to test otherwise they do not take the new setting from the Server.David
September 29, 2005 at 12:34 am #363394fleecy
ParticipantOK, I found the solution to my issue.
My shared folder setup as the home directory mounting point was named with two words (Company users). Deleting it and creating a new one simply named “Users” fixed the problem. I can now use networked homes and I also successfully used NetBoot in Diskless mode. Very nice.
Thanks for the moral support, guys!
October 3, 2005 at 12:37 am #363444ptone
ParticipantGlad you fixed it, I’ve also seen this if fast user switching is turned on in the client and you switch between two network log ins.
-P
January 24, 2007 at 7:58 pm #368093fleecy
ParticipantIs there anything new about this FUS problem?
We decided to live without logging in multiple network users through Fast User Switching on our computers, but it’s a definite pain in the derrière.
January 26, 2007 at 12:14 am #368104deemery
ParticipantIt seemed to me that it was no good to have two users Fast-User-Switched on the same machine with the same home directory mount point.
So for my home use, my ~ is on a mount point named “u” , and my wife’s ~ is on a mount point named “u2”. (OK, so not much originality there, but no spaces in the disk name…)
All I know for sure was that I was having problems getting the second account to work right until I created a new mount point for its home directory.
Generically, that’s been my experience with OS X Server as a non-professional administrator. When it works right, it’s solid as a rock. But it can fail in strange ways and provide -no- intuition or help in understanding what just happened.
dave
-
AuthorPosts
- You must be logged in to reply to this topic.

Comments are closed