Avatar of dcheyette
dcheyette
Flag for United States of America asked on

Cannot route internal messages - server to server - Exchange 2003 SP2

Exchange 2003 - SP2
Server1 - Original Server (swing method upgrade from Exchange 5.5 about 6 months ago)
Server2 - New Last week (lives over VPN connection from Server 1)

Last week I moved mailboxes from Server1 to Server2 so all users had local mailboxes.  

We also have 2 internet domains - domain1 smtp mail comes to server1 directly from internet.
                                                  domain2 smtp mail comes to server2 directly from internet.

Problem is... when a user from server1 tries to email a user whose mailbox store is on server2, the mail sits in the queue (Labeled Default SMTP Virtual Server).

Additionally, Server2 users can SUCCESSFULLY send mail to users on Server1, so this is a one-way problem.

Other information:

- Server2 users have a default internet email address of @domain2.com
- Recipient Policies are set to allow both domains.

I don't understand why this should be an SMTP issue as these mailboxes should be found by server1 internally.  Active Directory U&C shows proper mail store.  Replication between DC's is working properly.

Yes, I can ping servers in both directions.

Ideas?
Exchange

Avatar of undefined
Last Comment
dcheyette

8/22/2022 - Mon
Sembee

That usually means something is getting in the way. The classic cause is a smart host wrongly configured or an issue with SMTP. Pinging the servers isn't really enough. You need to test SMTP connectivity.

telnet server.domain.com 25
telnet servername 25
telnet ip.ad.re.ss 25

Try all three - entering the "other" server from the one you are testing. All three should succeed. If any or all fail then that can give an indication of the problem.

Simon.
dcheyette

ASKER
Simon,

I actually had done this before, and it works fine.  I get the appropriate response from all three.  I did it again just now to reconfirm.

Thanks,

David
ASKER CERTIFIED SOLUTION
Sembee

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
dcheyette

ASKER
There is no smarthost (I never use them) on the SMTP virtual server, but they are in the same routing group.  I'll try putting in a routing group connector.  I was thinking about this, but hadn't had any experience with them.

I'll let you know.

Thanks,

David
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
Sembee

Splitting them up shouldn't make much of a difference - but it will make message management more efficient.

Do you have antivirus on these machines? If so, check that there is no internal email scanning feature that could be getting in the way.

Simon.
dcheyette

ASKER
Simon,

I created separate routing groups and added routing group connectors both ways, restarted the routing engine and mta stacks on both servers and it did solve my problem.  Beats me why they couldn't route to each other using the default SMTP Virtual Server.

Thanks much,

David