Okay the situation is this.
Yesterday my company changed our dns server, because our former one, was too unstable to work with. anyway today i went to one of our mac server, because it needed to be configured because of the new dns server. So i tried logging in to the local admin, because it couldn't find the network account server, because of the domain shift, but it just froze when trying to log in.
Okay so I went down to our server room to get a look at it locally. I tried logging in to the local admin, but i froze again. So i tried pulled the network cable out, and suddenly i could login just fine.
I tried logging in via vnc once again and it just hanged. better than it freezing, but still a problem. so i logged in locally. went to system preferences to edit the path to the network account server, so the mac server could find it once more, but then it just froze the system preferences when i went to login options.
So i restarted back and forth some time and finally got to edit the path to the network account server, but when i typed it in, the mac server just say that the network account server is not responding although all other computers, both linux and mac, are using it just fine. I tried updating, rebooting without the network. tried FQDN for the network account server, it's ip, it's hostname nothing work.
Does anyone have any clue to what is going on? cause I really have no idea what to do, other than maybe reinstall the system, which i would like to avoid if possible.
Answer
The problem was YP bind. it still thought that it should get the OD accounts from the old ip, so that was why it couldn't find them.
I deleted the file accociated with the domain in /var/yp/binding/ and restarted the system. The machine is now acting normal to ssh and logging in from gui.
No comments:
Post a Comment