- This topic has 1 reply, 1 voice, and was last updated 22 years, 3 months ago by
.
-
Posts
-
Something has changed literally overnight in WGM.
My AD bind on the Xserve was OK. I come back in the morning and the AD domain in the dropdown in WGM (blue globe) says “Viewing directory: /Active Directory/burton-college.ac.uk not authenticated” (I can’t authenticate by clicking the lock – it says my name and password are not valid, but they are).
I think the last thing I was doing before I left last night was modifying my smb.conf file (realm = DOMAIN, use spnego = yes, security = ADS). I then had to setup and restart Windows Services as Domain Member. Did this trample my AD bind conf. ?
I’ve also switched off Appletalk on the Xserve, and I’m going to do this for all clients, so I’m just using TCP/IP.
In the past I’ve dumped files from Library/Preferences/DirectoryService and restarted/rebound.
My AD account has full rights and it’s the one I use to bind with.
(I think) I fixed it by unbinding (which actually accepted the AD account that WGM refused) and re-binding. I removed the authorisation/contact AD node prior to this and replaced it after the re-bind. I would still like to know why the authorisation failed in WGM – maybe after tinkering with smb.conf and re-starting Windows Services ?
Another point – Windows Service seems to have gone back to Standalone. I’ve just put it back to Domain Member. Our network has a Windows PDC.
You can probably tell I don’t fully understand implementing Windows service.
- You must be logged in to reply to this topic.