Hey Bill:
Understand about the brain hurting and needing beer.
Some fundamental questions; Are server one and server 2 in the
same Exchange organization? Are they in the same routing group? Are
they in the same administrative group?
What is USER2's SMTP address as stamped on the account by RUS?
Is it different from users on Server 1? If so, does Server 1 know how to
get there internally or is everything pointed at the firewall for
routing resolution?
I have more, but this should be a start.
John H. Matteson, Jr.
Systems Administrator/ITT Systems
FOB Orgun-E
Afghanistan
DSN - 318 431 8001
VoSIP - (308) 431 - 0000
Iridium - 717.633.3823
Roshain - 079 - 736 - 3832
"In the first place, we should insist that if the immigrant who comes
here in good faith becomes an American and assimilates himself to us, he
shall be treated on an exact equality with everyone else, for it is an
outrage to discriminate against any such man because of creed, or
birthplace, or origin. But this is predicated upon the person's becoming
in every facet an American, and nothing but an American... There can be
no divided allegiance here. Any man who says he is an American, but
something else also, isn't an American at all. We have room for but one
flag, the American flag.. We have room for but one language here, and
that is the English language... and we have room for but one sole
loyalty and that is a loyalty to the American people."
Teddy Roosevelt; 1907
-----Original Message-----
From: Bill Songstad (WCUL) [mailto:[EMAIL PROTECTED]
Sent: Friday, April 11, 2008 4:55 AM
To: MS-Exchange Admin Issues
Subject: RE: routing problem
To update things, after the spin around the firewall, the emails wind up
stuck in a current session on server1 for delivery from server2 but
there they time out. Emails the other direction, from server1 to
server2, are delivered in a timely fashion.
Brain hurts... must have beer...
________________________________
From: Bill Songstad (WCUL) [mailto:[EMAIL PROTECTED]
Sent: Thu 4/10/2008 2:38 PM
To: MS-Exchange Admin Issues
Subject: routing problem
I'm having a bit of a puzzler. I think it has to with DNS but I can't
seem to pin it down.
I added a second exchange 2000 server to a domain and moved one user
(user2) to the second server (server2).
User2 can send external mail fine. And can send mail to himself fine.
But, when user2 sends email to any user on server1 the email is routed
out through the firewall proxy and then back in.
The domain network setup is like this: public.com mx 30
=aaa.bbb.ccc.ddd (external interface of the firewall)
Private.net exchange servers: server1.private.net server2.private.net
Recipient policies have mail to [EMAIL PROTECTED] and [EMAIL PROTECTED] with
[EMAIL PROTECTED] being the default.
DNS server=server1.private.net and forwards externally to the firewall.
But it has a zone internally for private.net with hosts and mx records
mx 10 server1.private.net mx 20 server2.private.net
When user2 sends an email to a user on server1, an outbound queue
appears on server2 labeled "server1.private.net (outbound)" but the
email only arrives after spending several minutes swirling around on the
firewalls smtp proxy.
There are no connectors or smart hosts configured on either box.
Does anybody have any thoughts on why the servers are sending the mail
outbound rather than routing them directly to the other server?
I swear my head's about to pop.
Bill Songstad
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
