Exchange SMTP Connector Problem - Considering use of ADSIEDIT

Posted on 2006-05-31
Medium Priority
Last Modified: 2012-08-14
Can anyone offer guidance on the use of ADSIEDIT to resolve my problem;

Exchange Server 1 - First and main server in the organization and still in operation.

Exchange Server 2 - Second Exchange server added to the organization for testing, never really used and now removed (the server has been shutdown and re-built)

Since removal of Exchange Server 2 (or possibly since it's implementation) Exchange Server 1 has been unable to "forward all mail through this connector to the following smart hosts", it is however still able to send mail if set to "Use DNS to route each address space" or with no SMTP Connector in the system.

Exchange Server 2 had no mailboxes in it's Information Store and the instructions in the following TchNet artical were followed: http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/fd4864c9-1ea1-4e6d-a5cc-64f00ffa7a2c.mspx?mfr=true

So Exchange Server was successfully uninstalled from Exchange Server 2 before it was shutdown.

What happens when attempting to use a smart host is the queue to the smart host fills with the external email but it never leaves the queue.

Exchange Server 2 was only a MEMBER of the same routing group as Exchange Server 1.

Exchange Server 2 is no longer listed in Exchange System Manager and no configuration found in Exchange System Manager referres to it.

Using ADSIEDIT I have found the removed Exchange Server listed as a mailGateway in the following tree;

Configuration > CN=Domain Name > CN=Services > CN=Microsoft Exchange Server > CN=Domain Name > CN=Connections


Also, the computer account for Exchange Server 2 is still in Active Directory - could this be causing problems?

Any help or advice will be greatly appreciated.


Question by:ITHELP-BOCS
  • 2
  • 2
LVL 18

Expert Comment

ID: 16804652

Please remove old exchange server entry as mail gateway through ADSIEDIT.

Configuration > CN=Domain Name > CN=Services > CN=Microsoft Exchange Server > CN=Domain Name > CN=Connections

Remove exchange entry from here.


Author Comment

ID: 16806035
Thanks Ashish,

I have a System State backup of our domain controller (which includes Active Directory) but I am concerned about using ADSIEDIT incorrectly as it is such a powerful tool - please can you confirm that you foresee no problems with removing the server from the CN=Connections in this way.

Also, what about the computer account for Exchange Server 2 - should this be deleted (I can see this in Active Directory Users and Computers)?

Thanks again for your help,
LVL 18

Accepted Solution

amaheshwari earned 1600 total points
ID: 16806064
If the server is not present and you want to remove its entry through ADSIEDIT then no issues will come .

But Before using ADSIEDIT please make sure that you have valid backup of your exchange server.If Possible take online and offline both .

LVL 31

Assisted Solution

LeeDerbyshire earned 400 total points
ID: 16807334
You can delete the entry safely enough, but it's usual to find old servers in that location, and deleting it may not solve your problem.  Can you actually see this Connector in ESM, though, or a connector that has server2 configured as a local bridgehead?

Author Comment

ID: 16808227
I haven't deleted the server from CN=Connections using ADSIEDIT yet.

The Connector seen in ESM on Exchange Server 1 only specifies Exchange Server 1 as a Local Bridgehead.

I have also tried deleting this connector and setting up a new one - problem still occurrs.

Exchange Server 2 actually comes top in the list in the CN=Connections folder (don't know if that makes a difference) and Exchange Server 1 is listed twice for some reason?

To my delight it doesn't look I'm going to have to use ADSIEDIT after all - I have just tested Exchange Server 1 again and after 2 days with this problem it seems to have gone away - e-mail IS now being sent through the SMTP Connector to our ISP's smart host - it's leaving the queue and arriving at the destination.

Thank you both for all of your help.


Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses
Course of the Month16 days, 18 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question