Talk about loose confidence ! I have recently build a Windows 2008 R2 Domain with 2 Sites. I have the main Exchange Server in the same Rack as the DC with the FSMO roles. I re-booted the server yesterday and the the network card struggled to identfiy if it was in a home/public/domain. This has to be the worst development by MS!!!! If a server is in a domain all that Cr*p should be off. Thankfully it could see the Internet and was functional. Not happy...The server has 2 NIc's so I disable the spare and the Server then indentified the domain. It happened again after the next re-boot. Looking through articles it mentions opening the firewall TCP/UDP for 389. Ive done that but am not confident. Other things to note is that we have fully disabled IP 6 both through the controller and via the registry.
We have Baclup Exec 2010 with remote agents installed on the Server
Has anyone come across this? Can anyone point me at articles relating to this issue? Could it be the Backup agent?
I've spent many hours preparing this domain with Exchange and cannot believe that Domain Servers cannot remember they are in a domain.
Any help would be very appreciated!