Home Forums OS X Server and Client Discussion Open Directory Open Directory users cannot login after changing server IP

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #358401
    Anonymous
    Participant

    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.

    #358402
    Anonymous
    Participant

    I found references to the old server IP address in
    /Library/Preferences/DirectoryService/DSLDAPv3PlugInConfig.plist
    on client and server.

    The IP shows up in the value for the “Replica Hostname List” and “Writeable Hostname List” keys.

    I presume this is what is causing the problem, or is at least another symptom of something I did wrong.

    Due to other, unrelated problems associated with the current project to reconfigure the network IP structure, we have reverted all settings. Things are now working as they were before.

    However, this is but a reprieve. If anyone could still comment on the problem I created for myself, and how I might avoid it next time, I would still greatly appreciate the advice.

    Thanks,
    Adam

    #358726
    Anonymous
    Guest

    Ok… it was a rookie mistake. The second time around, armed with the knowledge of the changeip utility, this was pretty much trivial.

    Just ran changeip with the proper args,
    then changed the network preferences,
    then rebooted and updated my DHCP and DNS settings,
    and everything was smooth.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed