• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1638
  • Last Modified:

Outlook 2003 will not connect to either exchange server!

I recently installed Exchange 2007 on a dell poweredge 2850 in hopes of transitioning out my former 2003 exchange server. My DNS and DCHP and Domain controller run on a seperate x64 windows 2003 server. The 2003 exchange server also runs on a separate x32 version of windows server 2003 standard and is also a domain controller. After installing all the necessary updates and configuring the Server to handle 2007 exchange(all sp2 and .net update...), i installed it. I actually had to reinstall Exchange 2007 because i accidentally installed it on the C:\ drive which did not have adequate space. In order to complete this i had to reinstall the server operating system. After that i had to remove several objects from the active directory in order to successfully install the new copy of exchange 2007. Finally after that i was able to install it cleanly and everything went smoothly.Now that the server is installed on the domain i am unable to connect to EITHER server from an outlook 2003 client on a computer inside or outside the domain. When i try to set up a new exchange mailbox it is unable to find any exchange server on the domain. Also a routing group connector is setup between the two, this was automatically done during installation. I did a typical installation for the second time, the mailboxes transferred over without issues and the mailbox groups are mounted.

When i look into event viewer under system i receive several consistent errors: See attached 1
I also receive errors in the event logs of the 2003 exchange server and the DNS Server: See attatched 2 and 3

Any help would be great! Thanks so much!
The Active Directory topology service could not discover any route to connector CN=Internet Connect,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TIZA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=TIZA,DC=LOCAL in the routing tables with the timestamp 6/23/2008 8:35:17 PM. This connector will not be used.
Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=Microsoft MTA\0ADEL:605b6d2b-b5a6-48f2-a74d-ecc105157787,CN=Deleted Objects,CN=Configuration,DC=TIZA,DC=LOCAL for connector CN=Internet Connect,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TIZA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=TIZA,DC=LOCAL in routing tables with timestamp 6/23/2008 8:35:17 PM. Microsoft Exchange is ignoring the source transport server.
Failed in reading Connector's DS Info Process Id: 2984 Process location: E:\WINDOWS\system32\wbem\wmiprvse.exe -Embedding ConnectorDN: CN=Internet Connect,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TIZA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=TIZA,DC=LOCAL Hr:80040920 Attribute:[]
3(from the DNS server)
DhcpServer error 1059
The DHCP service failed to see a directory server for authorization.

Open in new window

  • 4
  • 3
1 Solution
If this is only the case of one single computer that is not able to connect, then make sure that the machine has the proper DNS server assigned to it.
jmgagenAuthor Commented:
sorry - to be clear NO workstations can connect
OK, looks like your DHCP server is not supplying the correct DNS server IP address. On one of your stations. launch the command prompt and type ipconfig /all. check if there is a DNS server IP address and if that address corresponds the DNS server of your internal domain.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

jmgagenAuthor Commented:
Hey Isaman07, thanks for the response.

I did what you suggested and yes the DNS server IP address does correspond with the ip address of our internal domain dns server.

For some reason the "connection specific DNS Suffix:     "  is blank when i use ipconfig on the servers connected to the domain. When i do ipconfig to a workstation that is not part of the domain the connection specific DNS suffix come up with tiza.local which is the domain name. I'm not sure if this has any correlation but before with the first installation of exchange 2007 this was not blank and we could actually connect to the exchange server. THANKS SO MUCH.
Are you sure that your active directory zone is good? Do you have MX record in place for both exchange servers? Is your internal DNS zone active directory integrated and does it allow dynamic updates? Clearly, this is about your clients not being able to find the domain controlers and the exchange servers, meaning, no proper name resolution which leads us to your DNS.
Do not forget, that DNS is not only a name resolution, but a service locator. It's your DNS that will tell your clienys who is the domain controler, the global catalog and the exchange server. So make sure, that all those records exist in your DNS.
As for the DNS suffix, you can easily addit on your DHCP server. Launch your DHCP server and expand the server option, check if option 15 is enabled, if not add it and enter your internal domain name, do a ipconfig /release then ipconfig/refresh to see if you will get the DNS suffix in place.
With that said, i don't beleive that your problem relates to the DNS suffix. if it is, then i will be happy to learn something new.
Keep me posted.
jmgagenAuthor Commented:
Hey Isaman07, again thanks for your response's!

So i enabled the option 15 in the DHCP Server and followed your directions, but when i tried to use the ipconfig /release command i received an error: "The operation failed as no adapter is in the state permissible for this operation."

This happened on the DHCP/DNS server as well as the new 2007 exchange server. What might this be?

Also, how would you suggest i check in the active directory zone is "good"? Are there certain things i should be looking for?

The internal DNS zone active directory does look to be integrated, but i am not sure how to check to see if it allows dynamic updates.


It's normal that you receive error during ipconfig/release on your servers, as your servers have static IPs, you should do the command on your clients only and not the servers.
As for DNS, right click the zone name and choose properties, as this will tell you what kind of a zone it is, then make sure that dynamic updates are enabled, plus,check under the zone if there are subfolders like domaindnszone forestdnszone.
Additionaly, make sure that the dns server for your exchange server is the internal active directory dns server, which is your domain controler.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now