0 Replies Latest reply: May 14, 2013 6:02 AM by mjmatul
mjmatul Level 1 Level 1 (0 points)

I hope someone can point me in the right direction. About 2 weeks ago I replaced our network router with a brand new one. There were no directions for manual install, just a "wizard" to run for setup. BECAUSE I AM AN IDIOT I used the closest computer to run the wizard- my Snow Leopard Server. The router wizard did not ask what settings you want for your router, instead it CHANGED THE IP OF MY SERVER! No client was able to login. I finally got into the admin settings for the router, and changed it back to what had been before- server manual address 192.168.0.10 and router 192.168.0.1. It took me a half a day, but I got the server IP changed, and doing DNS correctly, the router does DHCP.

 

After that little glitch, most clients were ok. I had a handful, OS from 10.4 to 10.7, no rhyme or reason, that could not login. "you are unable to login at this time because an error occurred". Accounts would login fine on a different machine, but no account would login on the handful. I deleted and re-added server in directory utility, deleted prefs, with no luck. Quite a few clients, like more than half, had weird sloooooooow login problems, taking 2 or 3 minutes to fully load home, and occasional spinning beachballs after logging in.

 

Fast forward: We had a huge power outage- lasted about 2 hours last week. When power came back on, and I started up the server, at first Server Admin showed no services. I restarted, and my server returned to what I thought was normal- but now NO USER can login. I do not know if this is related to my earlier problem, or a new development. Logging in from any client is attempted, from the logs it looks like kerberos authentication succeeds, but home directories fail to load, and user is dumped to the "you are unable to login because of an error" helpful screen.

 

What I have tried: Checking DNS - sudo changeip -checkhostname returns correctly, ip addresses match and are correct. FQDN for server is correct. I can ping the server both by name and ip from the client. nslookup on client returns correctly. I have checked sharepoint for home directories- appears to be shared correctly. If I login to client computer with a local login, then Go:Connect to Server, and login with a user account- the user's home is loaded as a connected disk- everything is there. I have looked through console log on client, and various logs in server admin, but I don't really know what to look for. I have gone as far as exporting my open directory database, demoting the server to a standalone server, re-promoting to open directory master, and restoring from the database, all of which seemed to go well- I am able to connect to server accounts manually as above, and all my users are back. In Workgroup Manager, accounts show as normal, and home folders are located in the same place they have always been. I don't know what to try next. Users who do not have server accounts (windows machines, and macs with local logins) can connect to the internet and all is fine.

 

I have searched support postings on several different occasions, but did not find any helpful suggestions.