?
Solved

smtp / smart host routing between exchange 2000 and exchange 2003

Posted on 2004-11-23
14
Medium Priority
?
401 Views
Last Modified: 2008-02-26
My situation

There is a Exchange 2000 on site 1 in Holland that has been working for about a year.  It recieves email for about 7 domains.  In the SMTP delivery advanced it has a smart host entry which is an ISA 2000 server.  On ISA it secures OWA and runs the SMTP queues as well each domain is listed in there.  The domians have a smart host entry back to the exchange 2000 server.

I have a exchange 2003 server which receives for another domain name (the MX points to me) and works fine.  In the same organisation and routing group.  

The problem I have is that some of the people (mailboxes) on my server have alias (smtp) for some of the domain names on the other server.  They are not getting mail or having it delivered 30 after it is sent.

It would seem that due to the smart host entry Exchange has lost the ability to look at the recipient policy which has all domains in and make the necesaary routing decsions.  The senders are not getting a ndr so in effect I have been loosing interna, and external mail for the last week.

Any help to resolve this would be appreciated.

Benjamin
0
Comment
Question by:benjamin
  • 8
  • 6
14 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 12659556
You need to remove the smart host entry from the SMTP virtual server. This is overriding the routing that Exchange needs to use. Instead of sending the messages to the other server, it sends them to the smart host.
Instead, create SMTP Connectors to send the messages to the smart host. Exchange can then route the messages in the correct way.

Simon.
0
 
LVL 2

Author Comment

by:benjamin
ID: 12659730
Simon

You are saying that I should remove the smart host entry for both servers in the smtp vserver delery advanced options, ok.

I have two connectors are present both smtp * cost of 1.  1 labelled for each server containing that server as a bridgehead.  do i leave these two?

All so what are the exact details I need to enter to create the connector do I enter all domain names @.....com etc and select forward to smart host?  Then do i need to restart exchange or anything for it to pick up the new connector I suspected the answer lay i th econnector but I have not created one before.
0
 
LVL 2

Author Comment

by:benjamin
ID: 12659960
As a though if I have mx record pointing to the two server do all domain names need to be in the new connector.

Can I leave the old connectore but gice them a high routing value?

Does the SMTP queue on the ISA server (smart host) it has the domains names entered and the smart host of one or the other server what do i do with them.

Thanks
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
LVL 104

Expert Comment

by:Sembee
ID: 12660249
You need to remove all the Smart Host entries on the virtual servers. Once you get to more than one server they MUST be removed. I personally feel it is bad practise to use them for configuration and will start with SMTP connectors to start with.

What are the existing connectors doing? Exchange is quite capable of delivering email on its own, without the need for the connector. Therefore if the connector does NOT have smart hosts entered in it then they can be added. A SMTP connector is used to send email in a direction that the Exchange server cannot work out for itself (usually to go via another server). On this site most of the time we are recommending use of a connector is to send email via the ISPs mail server.

Exchange will know what is internal email and will not use it for internal messages. Therefore if all outbound email needs to be routed via another machine then you just leave the * in place. Adding domain names to the list on the connector will actually stop them from working - as you are telling Exchange what domains to use the connector for.  

The MX record and the connector are not related. MX is for inbound email and SMTP is for outbound.

As for ISA, I cannot help. I personally prefer to use a real firewall to protect my network.

Simon.
0
 
LVL 2

Author Comment

by:benjamin
ID: 12662758
The two existing connectors are one for each server. with just the one server as a bridgehead i.e the connector it releates to.  They are both internet mail connectors by lable and the address space contains * 1 for the domains and cost.

As a though where is the mail going that looks ike it is delivered but never seems to get there, the bad mail etc seemd clean?
0
 
LVL 2

Author Comment

by:benjamin
ID: 12669375
As a second thought I am having the MX reocrd transfered to my server as I know it is te ISA that is causing the problem I have removed the snart host entries.  Do i need any connectors or can i delete them ?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 12669426
If you are sending the email directly then you don't need any connectors. Connectors are usually used for sending email in a direction other than what Exchange can find itself.

Simon.
0
 
LVL 2

Author Comment

by:benjamin
ID: 12670070
mmm i used the mail conection wizard which created the conector! is that a bad idea?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 12674721
I have never used the wizards when setting up an Exchange server, mainly because I like to work things out for myself. While it wasn't a bad idea, I am at a loss as to why MS have added the connector - unless it is to give you something that you can easily adjust with alternative SMART HOSTs or DNS servers if required.

Simon.
0
 
LVL 2

Author Comment

by:benjamin
ID: 12677356
Ok

I have checked recipient policy and global address list the are correct and rebuilt.

I have deleted both connectors that I mentioned.

On the server that is 2003 it sends internal mail fine to the 2000 but the 2000 does not send internal mail to 2003.

Tha smart host entries are gone and both server have been rebooted.  Between them is a open PIX firewall and a 2mb link.

When I look at the 2000 smto queues I see the mail in there that simply sits in the que (labelled for my server, 2003) but the mail does not leave.

I dont see how the ISA is in the picture any more due to the removal of the smart host.

ANy more ideas? all so do I need WINS the analyser check tool for 2003 has suggested it is need for short name look up.  I run DNS only and al machines are 2000 or above?

Thanks Benjamin
0
 
LVL 104

Accepted Solution

by:
Sembee earned 2000 total points
ID: 12677587
You need to verify whether the two servers can connect to each other.

Ping the other server (from both) by IP address, name and FQDN.

Then try a telnet test. Again from each server to the other

telnet server 25

Replace server with the IP address, name and FQDN in turn.
This will confirm connectivity between the servers. If it fails, then there is an issue with the connectivity.

As for WINS, Microsoft seem to be very reluctant to let go of it. I run a number of Exchange installations without WINS and they have no problems - except failures within Microsoft tests.

Simon.
0
 
LVL 2

Author Comment

by:benjamin
ID: 12681375
Simon

It turned out to be port 25 through the PIX that caused the conectivity issues.  The network guy who tested it still can not believe he missed it.  I tested it myself and saw straight away that that I could not telnet.  

However you supplied some very good info and pointed me to self test in effect with your last comment. SO you get the points.  

As a side question can you offer any advice on the receipient policy.

2 server, 7 domain names coming in.  I assume I should create seperate policies for each gourp of people who want a given set of addresses?

Thanks
0
 
LVL 104

Expert Comment

by:Sembee
ID: 12682442
I tend to just add the domain names to the default policy. This makes life easy. The only thing with adding the domains to the same policy is that all users get email addresses on all the domains - you then have to adjust the addresses by hand to control which address is default and thus goes out on all email messages.

Simon.
0
 
LVL 2

Author Comment

by:benjamin
ID: 12682691
Ok thanks for all the above Simon.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

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

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month14 days, 4 hours left to enroll

807 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