Really two basic things needed to be done to correct the issues.
A: Make all the servers that were replicas slaves i.e. "connected to
a directory system" I have had suggestions that this is a bandwidth
issue.
B: Ensure that all of your LDAP entries have the correct settings in
the inspector tab. The "HomeDirectory" setting should be the address
of the server and will look like "<home_dir><url>afp://10.0.1.10/".
The second setting that is important is the "NFSHomeDirectory" entry
which contains the value for the path to the home directory and will
look like "/Network/Server/servername/sharepoint/user".
As far as my testing is going. So far so good! Thanks so much for
everyone who helped out on this one!
- Barrett
On Sep 1, 2005, at 2:50 PM, Barrett Hartman wrote:
Will do. I am taking the replicas out of the loop and making them
slaves i.e. "connected to a directory system" It is one less thing
to complicate the process. Thanks again.
- Barrett
On Sep 1, 2005, at 10:15 AM, David B. Hunter wrote:
One more note...
...after re-creating your automounts. Pick a user for testing in
WGM and in the Homes tab, set their home directory to <NONE> and
then refresh the page. See what automounts are available and
select the one you want. I've had issues with home directories
after automount re-creation if I didn't first set the user's home
directory to <NONE>, save the setting and then select the home
directory I wanted, saving again.
At 9:48 AM -0400 9/1/05, Barrett Hartman wrote:
On Aug 31, 2005, at 3:55 PM, David B. Hunter wrote:
1. You may have exceeded the length of the user's home directory
URL, I have had this cause the error you are seeing in the past.
I've had less problems with the length of the pathname in 10.4
than in 10.4
I double checked this. The length of the directory path should
be fine for my servers they are running 10.3.9 so I gain the
extra 14 characters that you don't have prior to 10.3.5.
I am currently going through and recreating my automounts though.
"Just in case"
2. On the client machine, you may also want to check the /var/
log/secure.log file. I find that it has elaborate information
regarding the network login process. Including errors related
to the length of the path, authentication errors, etc.
The secure.log file didn't offer anything other than stating
successful or unsuccessful login attempts.
3. Using Workgroup Manager (WGM) check your share-points and
ensure that you can see them and they are valid. Try logging in
to a user's remote share by FIRST logging into the workstation
using a LOCAL account. Then try CMD-K and enter "afp://
<servername>/<username>" and see if the share mounts
successfully. If not, time to check sharing and automount records.
I have tried this previously if issue (A) occurs I can even
connect to the server from the users non functional account and
mount their home directory. It just won't automount. Still
unsure why.
4. Enable the option to edit directory records directly and then
click on the target icon in Workgroup manager and select
"Mounts". Make sure you see the automount records you think you
should.
Doing this right now!
I cannot thank you guys enough for helping me with this!
-
Barrett Hartman
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macos-x-server/hartmanb%
40mac.com
