Exchange 2007: Domain Problems! Urgent no mail flow!
Hi, We have an Exchange Server 2007 Standard Edition on a Windows 2003 Standard and another Windows 2003 Std which is our Domain Controller.
All of a sudden if you open up the Exchange Console it comes up with the following errors:
get-ExchangeServer
Error:
Could not find and Domain Controller in domain {domainname}
Domain Controller not found in the Domain {domainname}
get-UMServer
Error:
Could not find and Domain Controller in domain {domainname}
Domain Controller not found in the Domain {domainname}
The Domain Server is up and running everyone can access it I can ping and file access it from the Exchange Server and get access to the Exchange server from the domain. Peoples outlook connected to Exchange arn't working saying it can't find the Exchange server or keeps prompting for passwords etc and mail doesn't seem to be flowing anywhere
I am also getting these in the Event Logs:
Event Type:ErrorEvent Source:MSExchangeTransportEvent Category:TransportService Event ID:12014Date:11/03/2008Time:16:07:55User:N/AComputer:SYSMAILDescription:Microsoft Exchange couldn't find a certificate that contains the domain name mail.systemhygienics.co.uk in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector OUTGOING with a FQDN parameter of mail.systemhygienics.co.uk. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type:WarningEvent Source:MSExchange ADAccessEvent Category:Topology Event ID:2106Date:11/03/2008Time:16:11:15User:N/AComputer:SYSMAILDescription:Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1464). Exchange Active Directory Provider failed to obtain DNS records for forest DC=SystemHygienics,DC=co,DC=uk. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values 0 (priority) and 100 (weight).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
As far as i can see nothing odd looking in the DC server. We have struggled with this for the last week sometimes mail flow works but the Console just does not work, I have tried adding a domain through the console but no domains appear.
Has anyone had this problem or know how to fix it? Thanks, Max.
March 11th, 2008 7:28pm
Ok Mail is flowing again but we still got the error with the console not working and we cant manage the Exchange Server at all.
Has anyone else had anything like this?
Free Windows Admin Tool Kit Click here and download it now
March 12th, 2008 12:32pm
Also other symptons:
Backup Server (yet another server) backsup across the network around 600MB per second from all servers apart from the DC where it runs about 18MB per second (we have a GB network throughout the company)
Another problem we are having is the internet sometimes goes slow at the moment its going fast but our DC/DHCP server when it pushes out the Settings when a client requests and IP address the internet (Default Gateway) is set to go straight to the Router and not interact with any servers.
DNS seems to be working fine so it can't be that. We have checked the network cables and changed things around that seems all fine. The users can talk to the File Server (DC Server) and read and save files perfectly fine
All servers can ping each other by name and ip address. So I don't reckon its a communication problem but there is something under the hood somewhere thats causing alot of problems unless there is more than one problem.
I have a question, Can an Exchange Server 2007 STD be removed from a domain and then reconnected to the domain with no harm to Exchange or its data/mailboxes and their content?
We had the idea of removing it from the domain rebooting then reconnecting it to the Domain just to see if that made any difference?
Thanks in advance,
Max.
March 12th, 2008 3:48pm