Network Accounts Unavailable?

Hi

Go back to basics and start inspecting the physical structure of the network. Can you ping the server from the affected macs? Have you checked the network cables and wall ports? Have you checked the network settings are the same on the affected macs as they are on the unaffected macs? Are DNS server settings as well as Search Domains different on the affected macs? Are the affected macs assigning self-assigned IP addresses? Are they receiving correct information from the DHCP Server?

Hope this Helps, Tony

Hi Brian

You can use netstat and ipconfig to troubleshoot this further. On the Server issue:

netstat -a | grep LISTEN

If you see * . ldap then slapd is listening for LDAP requests. If it comes back with 127.0.0.1. ldap then its only listening on the loopback address. Although netstat probably won’t tell you much as for other clients its working. On the affected clients issue:

ipconfig getpacket en0/en1/en2

Where en0/en1/en2 is the network interface being used. Another possibility is time sync issues. Perhaps the date and time is so far out on the affected clients they are not being authorized to access the server?

Hope this helps, Tony

Hi Brian

I’ve deployed numerous OD Masters in different environments and I have never supplied any network user name or password when joining network clients to the Kerberos Realm. As long as the local client’s .local name populates the first field there is really no need to add anything else. Continue past this point and OK the next window. If you have enabled the 'require directory binding' option in Server Admin then you would have to add an authenticated LDAP user (diradmin generally).

http://discussions.apple.com/thread.jspa?messageID=4497792&#4497792

Is a link for 10.4 Server specifically. It may still help as a reference for 10.5 Server.

Hope this helps, Tony

Hi Brian

I may be able to explain this.

Before even taking client computers out of their boxes configure you server first as an OD Master with all the desired accounts existing in the LDAP node as well creating networked auto-mounting home directories.

As you switch on the clients the setup assistant will go through the process of assisting you in setting up the client's default admin account. If the client's are connected to the same network as your OD Master and are receiving IP addresses from the DHCP Server (it can be the OD Master but it also works if the DHCP Service is elsewhere) then you will be presented with an option to create the default admin account with an Account that exists on the Open Directory. It would be at this stage that you would present account details (name and password) that exists on the LDAP server. The account that gets created locally will still take the short name admin but will have the password of the network user account used. After the restart you'll be presented with the usual login window with admin and 'other'. This is a useful way of creating one admin account on the OD Server that can be used to create the local admin account on all the client computers. This account does not require a networked user home folder as the home folder would be created locally.

Defining a new Computer List and adding all client computers to that list should allow you to present a list of all OD users and groups.

Apologies if you already know this but its useful to present it here as others may read this post who are probably not aware that this is possible.

Hope this helps, Tony