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

Exchange 2003 Inter-site mail delivery not working?

Hi -

I am looking for troubleshooting ideas / possible suggestions on this problem:

Started with an existing Win2000 Server running Exchange 2003.  This server will be decommissioned soon -

So on the same domain I have built an additional Win2k3 box with Exchange 2003 Sp2.  Installed into the Exchange Organization no sweat...

The idea is : Move mailboxes when we migrate.

Created a test user on one server, moved to other server no problem.

But I can't get mail delivery to flow from a test mailbox on the new Exchange box back to a test mailbox on the old.  It works the other way.  When looking in the queues, I can see the messages and they just hang there.  

I've turned on logging, but I'm not certain what information can be learned from this.  I've never troubleshooted inter-site mail flow before.  

Any ideas?

Jason
0
trivalent
Asked:
trivalent
  • 4
  • 3
1 Solution
 
rakeshmiglaniCommented:
is message tracking enabled? what does it tell you?

in which queues are the messages stuck?

any smart host entry on the new server?
0
 
brakk0Commented:
Are the servers in the same routing group? Have you set up routing groups?  Since it is temporary, you could try configuring two routing groups, put one server in each group and configure routing group connectors to move the mail.
0
 
trivalentAuthor Commented:
>Is message tracking enabled? what does it tell you?

I've turned on message tracking - but I'm not sure what I'm learning.  What extended properties should I enable?

>in which queues are the messages stuck?  

The messages are stuck in the queue for (new exchange server name).(domainname).local under the old Exchange server

>any smart host entry on the new server?

No there is not.

The old Exchange server has not been put up to SP2 yet.  Do you think that would make a difference in this scenario?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
rakeshmiglaniCommented:
try doing a telnet on port 25 on the exchange servers to check whether you are able to drop an email via telnet

XFOR: Telnet to Port 25 to Test SMTP Communication
http://support.microsoft.com/kb/153119/en-us
0
 
trivalentAuthor Commented:
> try doing a telnet on port 25 on the exchange servers to check whether you are able to drop an email via telnet

Done that.  Success both ways.
0
 
rakeshmiglaniCommented:
if you double click on any message stuck in the queue, do you see any information there.
0
 
trivalentAuthor Commented:
> if you double click on any message stuck in the queue, do you see any information there.

Yes, in the message properties it seems to be in a permanent 'Retry' state.   I've tried forcing the connection...
0
 
rakeshmiglaniCommented:
Cannot think of anything else.. try installing and running the following MS tool and see if it tells you anything

Microsoft Exchange Server Best Practices Analyzer Tool v2.6
http://www.microsoft.com/downloads/details.aspx?familyid=DBAB201F-4BEE-4943-AC22-E2DDBD258DF3&displaylang=en
0
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: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone 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