Dan,
I haven't checked the latest tips and tricks but from the beginning I
was told and did set the LDAP DNS manually. That was the first step
in setting up Directory Access, I don't recall seeing or hearing
anyone say it was ok to go back to supplied DNS. Did I miss something
or could this be your problem?
Cheers,
Ed Crelin
On Aug 30, 2005, at 6:58 PM, Ball, Dan wrote:
Josh,
DNS is working 100% here......we did have issues with OS X clients
not auto creating DNS entries. Everything gets IP, DNS from DHCP
on a Windows 2003 server and was working fine then we did updates
one day on the servers and the OS X Clients stopped creating DNS
entries for forward and reverse records.
We rebooted the servers again and everything started to work again
so DNS is back to running at full capacity and the OS X clients and
servers are running fine as well with both forward and reverse.
I'm not sure why Tiger is getting the blue screen with the spinning
gear.....the part I am stuck on is if I put my credentials in when
binding 10.4.x to the OS X server within the LDAP plugin I don't
get errors in the logs. But if I don't put my credentials in and
set everything up like we have 10.3 I get errors in the logs and
eventually the blue screen.
I don't want to have to create an account just for binding the
clients to the server unless its needed but it shouldn't be to my
knowledge. Maybe one of the 400+ fixes in 10.4.3 will fix this issue?
Thanks,
Dan
----------------------
On Tuesday, August 30, 2005, at 08:06AM, Ed Crelin
<email@hidden> wrote:
This may serve as a good control for anyone else having
log in problems with outside DNS or LDAP services.
I'll just go on record here and state that, IMHO, you should never
attempt to setup OD (or AD for that matter.) without working,
verified, internal DNS. Never, ever, ever rely on the ISP DNS.
If you have central DNS at a district office or what not, then you
should have at least one slave at each remote location.
