On Jan 31, 2005, at 9:07 AM, Josh Wisenbaker wrote:
On Jan 31, 2005, at 9:45 AM, tim olson wrote:
by adding ip into directory services i ASSUME that you mean on the
client so that they go direct to the server with the home folder
Hmm... he said he put the IP in as the search base. I assumed this was
in an effort to cause a timeout error on a bad config and delay the
startup.
nope - its required if there are ANY other servers on the network -
automatic only works if there is ONE server as per the sample. as soon
as there is another reachable server - then it must be specific as to
WHICH server to get the home from.
apple assumes that if you have more than one server then you have paid
folks to take care of it - they gear the manual to a person with one
server - if you read it and follow the directions verbatum it will
work. i have three servers, osx, linux, win2003 - so i have to be
specific.
this is a specific listed step in apples manual that all clients that
are using network homes need to have the ip address of the server
with the home folder added - without that it is very very flakey.
however that bit of info is buried at the end of a paragraph near the
bottom of a page half way through the docs and is not indexed. but as
-dhan would remind us it IS there and it IS required.
Where is this info? I just poured over the Panther docs and can't find
it. Everything says DNS name _or_ IP address. I'm just curious if you
have a page number.
Getting Started.pdf page 120 to 126 for a SINGLE server page 126 is
for the client - the rest is for the server.
a document "Client Management with Mac OS X Server Mac OS X Server 10.3
Panther and connected clients (9.2, 10.2X and 10.3.X)" contains the
information on how to make a bullet proof client that will always
connect and how to make sure that your client picks the right server to
find its home folder each time.
the "automatic" on page 126 of the getting started is ONLY for a single
server - if the clients can see any other server they will start
casting around trying to find the right one with the home they are
seeking.
to
to
on client - go to:
applications/utilities/Directory Access
and UNCHECK box "use dhcp supplied LDAPv3"
then
applications/utilities/Directory Access LDAPv3-Authentication:
select custom path
add line /LADPv3/xxx.xxx.xxx.xxx
add line /LDAPv3/fqdn
home folders will be forever unreliable without this being done.
That's not been our experience at all. Only in cases with flakey DNS
have we ever needed to use the IP instead of the FQDN. What may be
going on here is that having two servers in the Auth path slows the
boot enough to where the homes work properly.
IF APPLE WOULD CHILL ON THE BOOT TIMES THIS WOULD PROBABLY GO AWAY!!!!
Arrgh! It makes me nuts that they will sacrifice enterprise stability
so that someone's new Mac mini will boot in 30 seconds instead of 45.
