Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Open Directory error
- Thread starter twoodcc
- Start date
- Sort by reaction score
rezenclowd3
macrumors 65816
As you know what time you tried to log in, check the logs on the server. Sorry, I have not ran across this problem.
Les Kern
macrumors 68040
I have seen this.
Start over. Delete the user and the share directory... save docs if needed. Drop their account off the mobile unit. Re-enter user (same short name) and drop their stuff back in. I never had it happen often enough to discover just WHY, and this fix takes a few minutes anyway.
Start over. Delete the user and the share directory... save docs if needed. Drop their account off the mobile unit. Re-enter user (same short name) and drop their stuff back in. I never had it happen often enough to discover just WHY, and this fix takes a few minutes anyway.
thanks. so just delete the user and unshare the sharepoint?
i tried just creating a new user, but i had the same problem.
also, the directoryService in activity monitor on the client machine bogs down the client sometimes.
i think i'm ready to give up on it again. i mean, i have the server setup and all, but when i bind client machines, either i'm not doing it right, or for some reason it's not working right.
i mean, i can't get the mobile home to sync correctly after logging in with a user account on the client machine.
if i'm on a regular account on the client machine (local to the client), then the directory service uses half the computer's resources.
and if i have it set in dns on my network stuff to look to my server, and then i leave my network, it slows down the internet.
sorry for the rant, but i've tried and tried with OS X server, and every time i seem to fail, even when it appears i have it setup right
i mean, i can't get the mobile home to sync correctly after logging in with a user account on the client machine.
if i'm on a regular account on the client machine (local to the client), then the directory service uses half the computer's resources.
and if i have it set in dns on my network stuff to look to my server, and then i leave my network, it slows down the internet.
sorry for the rant, but i've tried and tried with OS X server, and every time i seem to fail, even when it appears i have it setup right
Les Kern
macrumors 68040
Hmmm... in order to use open directory, you need a valid DNS server running... it's critical. Also, "shutting the internet down" could be related to a DNS storm, which I have suffered from... it COULD be related but who knows without actually being on site to witness this. I apologize but it's obviously something I am missing. My master has 2600 accounts on it, up to 300 using it at a time... so something is up with the basic configuration as it's a pretty robust system even on lesser servers. Looking like I can't help all that much here, this is a more complicated problem for a forum. Perhaps there are some local resources you can tap? If you are a business it might be good here to contact them esp. if this is mission critical?
Best of luck.
miniConvert
macrumors 68040
I don't use a DNS server and OD works fine for me. Took me a few tries of various errors and window shakes on client logins (I ended up reinstalling OS X Server I messed it up so badly the first time). Have you changed the IP address of your OS X Server ever? It hates that.
But yeah, no DNS for me. The .local hostname of the server resolves fine on all client machines on the network. As it aint broke, I don't intend to fix it 😉
No doubt OD on OS X Server can be fragile. I literally just put the IP of the server into the LDAP bit of Directory Access and let each client auto-configure itself, then it was fine.
(Tiger, btw, we don't use Leopard)
But yeah, no DNS for me. The .local hostname of the server resolves fine on all client machines on the network. As it aint broke, I don't intend to fix it 😉
No doubt OD on OS X Server can be fragile. I literally just put the IP of the server into the LDAP bit of Directory Access and let each client auto-configure itself, then it was fine.
(Tiger, btw, we don't use Leopard)
thanks for the replies.
i do have DNS running correctly (at least i think). and like i said, the clients bind to the server just like they should. but when i try to log-in, it doesn't.
or i do log-in, it won't home sync.
and when i'm away from the network, the internet is slow (the client continues to look for my server)
i do have DNS running correctly (at least i think). and like i said, the clients bind to the server just like they should. but when i try to log-in, it doesn't.
or i do log-in, it won't home sync.
and when i'm away from the network, the internet is slow (the client continues to look for my server)
I had the same issue when I was getting 10.5 up and running on my Xserve. I had the same error as you and had painfully long startup and login times for my client machines. I was able to trace it down to a DNS issue on my server. I also thought the DNS service was running properly, but I was wrong. After much searching(I only started working with osx server under 10.4 last year), I found a quick and easy way to check if your DNS is working. In the terminal application on your server type in...
changeip -checkhostname
If the DNS is working properly, it should read back the server ip address and your hostname(server.name.com) and say that the DNS is working. If it shows anything else, the DNS is not setup right. As I said I thought my DNS was working correctly, but recieved all sorts of errors when I ran the terminal command above. I discovered that when I had installed the os for the 6th time, maybe 7th I lost track after a while, the setup pulled some DNS hostname info from my isp and had saved that in the system somewhere. With my limited knowledge I was unable to remove that info from the system. So I ended up reinstalling the os again.
One other tip I learned from my research into this. When you install the os onto the server, don't have it hooked up to the internet. If it's going to be a primary OD server, network it like this...
server->switch/hub/router->client machine to test with
You can change how it's hookedup later but this keeps the server from pulling info from elsewhere during the initial setup. If this is going to be a secondary server then you would have it hooked up to the primary server to pull info from.
Hope this helps a bit and I wish you luck.
changeip -checkhostname
If the DNS is working properly, it should read back the server ip address and your hostname(server.name.com) and say that the DNS is working. If it shows anything else, the DNS is not setup right. As I said I thought my DNS was working correctly, but recieved all sorts of errors when I ran the terminal command above. I discovered that when I had installed the os for the 6th time, maybe 7th I lost track after a while, the setup pulled some DNS hostname info from my isp and had saved that in the system somewhere. With my limited knowledge I was unable to remove that info from the system. So I ended up reinstalling the os again.
One other tip I learned from my research into this. When you install the os onto the server, don't have it hooked up to the internet. If it's going to be a primary OD server, network it like this...
server->switch/hub/router->client machine to test with
You can change how it's hookedup later but this keeps the server from pulling info from elsewhere during the initial setup. If this is going to be a secondary server then you would have it hooked up to the primary server to pull info from.
Hope this helps a bit and I wish you luck.
thanks. i have also reinstalled several times. but i i have ran that command and i have my DNS working properly (or at least according to that command i do).
but i'm still having problems with logging in with the client machine.