Forum Replies Created
-
Posts
-
I tried another client machine, and it showed the same results. Confirming my theory of the local cached version of the server, it only had the user’s folder that I had logged into. It had the full structure of the server under /Network/Servers/myserver/FileHD/subdirs. But inside those subdirs was nothing; it was empty, despite there being at least two user home directory in each on the server.
I also tried a Tiger client, since I have since been testing with Jaguar clients. This produced a different error message, that it can’t load the home directory because it’s on an AFP server. (you know, that common one).
However, I finally did find the problem. It was the permissions of the various share points. They were set to have the teachers group as read only, but no one else other than admin could read or do anything. Under Panther Server, which is where this server is being upgraded from, doing that didn’t cause this problem. It seemed that if the subdirectories (meaning the home directories) had the right permissions, the parent directory’s permissions didn’t matter. In Tiger Server, however, this does not seem to be the case. It seems the user needs at least read only access in order to be able to use the automount share point.
I have since tried logging in with multiple users and everything seems to be golden. Thanks for all the help 🙂 Now I just need to setup some managed preferences and I should be good. If only the many, many clients are going to be this easy to upgrade >_>
There aren’t any other automounts; just these ones for the home directories. When I use Go in the Finder, it doesn’t seem to be able to find them either. It lets me browse normally, but what I see seems to be a cached local version of the network mounts. For example, I can see a folder for one of the test accounts that I have deleted a while ago. What it looks like to me is the client is somehow using a local version of the network share, and that is why it doesn’t give me an error about not being able to find the home directory.
Should I perhaps try logging in with another client?
