After changing:
-server IP address, subnet mask, router, and dns servers
-DNS server settings to reflect new subnet
-DHCP server settings to reflect new subnet
(OS X Server 10.3.4, btw)
Now, none of the users in (server)/LDAPv3/127.0.0.1 can log in at the client machines on the subnet.
Logging in as a local administrator at the client machines, I was able to confirm that the DHCP server is working, delivering an IP address, DNS servers, and LDAP settings. Also, using Network Utility I tested the DNS and all looked great, forward and reverse (looking up the server name/ip, as well as other named network devices).
AFP is working, and authenticates the same users that cannot login at the login window.
One odd thing I noticed, looking at Directory Access on the client machines, is that the ‘DHCP-supplied LDAP settings’ used the old server IP as the name of the settings, though the LDAP server shown as the DNS name of the server. I tried unchecking ‘use DHCP-supplied LDAP’ and entering correct values, but really they were correct, and all I did was create an identical set with a different name.
(OS X 10.3.4 on all clients, btw)
quickly getting lost……
thanks for any help.
Comments are closed