Cannot bind to domain
-
Just added a 2003 server to a network. It is not the DC, just an ordinary part of the network that happens to be running server. I checked the application event log and there were two errors in it following joining it to the domain. The first was error 1006, ".. cannot bind to my.local domain ...", and the second was error 1030, " ... unable to ... Group Policy ...". Not sure of exact wording on the second one but you get the idea. I have gone through several message boards looking for possible causes. All of the suggested fixes do not apply (i.e. the system is already configured as suggested). So, I took the next step of removing the computer from the domain and re-adding it. Following the reboot the computer joined the domain correctly (or at least there were no errors in the event log). This lasted until the next reboot when the messages reappeared. Several of the boards I read talked about one or the other message appearing in the log repeatedly, but in my case they just appear the one time. If I check the system event log after a few hours there will be error message about the new server not being able to receive NTP messages from the DC, so the problem is persistent. During the time the computer appeared to be joined to the domain these messages were not appearing in the log. Any ideas of what to try would be appreciated...
>>>-----> MikeO
-
Just added a 2003 server to a network. It is not the DC, just an ordinary part of the network that happens to be running server. I checked the application event log and there were two errors in it following joining it to the domain. The first was error 1006, ".. cannot bind to my.local domain ...", and the second was error 1030, " ... unable to ... Group Policy ...". Not sure of exact wording on the second one but you get the idea. I have gone through several message boards looking for possible causes. All of the suggested fixes do not apply (i.e. the system is already configured as suggested). So, I took the next step of removing the computer from the domain and re-adding it. Following the reboot the computer joined the domain correctly (or at least there were no errors in the event log). This lasted until the next reboot when the messages reappeared. Several of the boards I read talked about one or the other message appearing in the log repeatedly, but in my case they just appear the one time. If I check the system event log after a few hours there will be error message about the new server not being able to receive NTP messages from the DC, so the problem is persistent. During the time the computer appeared to be joined to the domain these messages were not appearing in the log. Any ideas of what to try would be appreciated...
>>>-----> MikeO
Today I tried something different. I removed the computer from the domain and rejoined it. Then I shutdown the computer and turned it back on with no errors. I did this twice more with no errors, then I restarted the computer without shutting down and the errors were back. The errors are there now whether I shutdown or not. Any suggestions on this would be really appreciated.
>>>-----> MikeO
-
Today I tried something different. I removed the computer from the domain and rejoined it. Then I shutdown the computer and turned it back on with no errors. I did this twice more with no errors, then I restarted the computer without shutting down and the errors were back. The errors are there now whether I shutdown or not. Any suggestions on this would be really appreciated.
>>>-----> MikeO
Mike Osbahr wrote:
Any suggestions on this would be really appreciated.
It almost sounds like its not really getting added into Active Directory when you add it. Log into the DC, is there an entry for that server listed in Active Directory Users & Computers? Try deleting the entry (if one exists) disjoin the server from Active Directory and rejoin it. After that make sure that there is an object listed in the DC. Also are there any entries in the DC’s event log?
I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:
-
Mike Osbahr wrote:
Any suggestions on this would be really appreciated.
It almost sounds like its not really getting added into Active Directory when you add it. Log into the DC, is there an entry for that server listed in Active Directory Users & Computers? Try deleting the entry (if one exists) disjoin the server from Active Directory and rejoin it. After that make sure that there is an object listed in the DC. Also are there any entries in the DC’s event log?
I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:
Thanx for the reply. That's what most of the boards I read suggested. It was getting added to Active Directory and DNS. There were no messages in the DC event log when I rebooted the other server (two of them actually). I finally put an SMC 10/100 adapter in a PCI slot and used it instead of the built-in Ethernet. It worked the first time.
>>>-----> MikeO
-
Thanx for the reply. That's what most of the boards I read suggested. It was getting added to Active Directory and DNS. There were no messages in the DC event log when I rebooted the other server (two of them actually). I finally put an SMC 10/100 adapter in a PCI slot and used it instead of the built-in Ethernet. It worked the first time.
>>>-----> MikeO
Mike Osbahr wrote:
I finally put an SMC 10/100 adapter in a PCI slot and used it instead of the built-in Ethernet. It worked the first time.
Interesting, thanks for replying back. Glad to hear you figured it out... I take it there was no faults registared on the NIC?
I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley: