At 20:14 +1100 1/29/05, Paul Kneipp wrote:
>great response!! Thanks so much people - I pass this stuff on!
>
>>From your replies, it appears that getting the 'home folder missing' error:
>
>1. Is quite common.
>2. Is more common when trying to force OS X clients to bind across subnets to the server.
>3. Can be beaten via scripts which delay the boot sequence.
>
>This would explain why I got the whole pathetic mess to work today (yay caffeine!) by duplicating the LDAP server in Directory Services and entering the IP address as a search base. ( two entries in Directory Services/LDAPv3) This means it probably just slows down the load enough to work.
I, too, have encountered this problem and solved it using the IP address instead of the FQDN in the Directory Access utility and without using the slowdown/delay scripts during client workstation boot. Why this works, I'm not sure. After all, if I don't use the slowdown scripts, it shouldn't make a difference whether I use the FQDN or the IP address in the Directory Access utility on the client workstations. Unless, of course, the mere act of doing a DNS lookup slows the client workstation sufficiently that it doesn't pick up the network mounted home directories. Another data point, for what it's worth.
You do know the caveats of using IP instead of FQDN, right?
--
Network Wrangling and System Delousing
Apple Certified Help Desk Specialist - Panther
Apple Developer Connection member
Reality Artisans, Inc.
New York, NY
<http://www.realityartisans.com>
(212) 369-4876 (Voice)
PGP Fingerprint: 77B3 D1E9 D24B 4FA9 9606 6C8D 62E4 2E4A 6FDD 9FD5
_______________________________________________
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/email@hidden
This email sent to email@hidden
