Christian Egger
Guest
|
 Posted:
Wed Nov 30, 2005 5:58 pm Post subject:
Error 4003 and 984 MSEXCHANGETRANSPORT |
|
|
Hi!
We have an Exchange Organisation that is in the upgrade process from 5.5 to
2003. We have about 50 Sites / AGs and Messagerouting works properly except
for Users on one Server.
We have 1 Native Exchange 2003 AG / RG with one MSX 2003 Server. When we
send a mail from a mailbox homed on this Server to an User in one special
other AG (Exchange 5.5 Site) our mail stucks up in the Queue "Messages with
an undeliverable Destination ...". Sending a Mail to any other Exchange 5.5
Site works fine.
Our Topology looks like this:
About 50 Exchange 5.5 Sites (After ADC and SRS Installation they are
represented as Administrative Groups in System Manager).
One Administrative Group containing only one Exchange 2003 Server
Central Mailhub Site with one Exchange 5.5 Server that has an X.400
Connector to every Exchange 5.5 Site and one Exchange 2003 Server that is the
Site Replication Service and Bridgehead Server for the Routing Group
Connector that connects the Central Mailhub Routing Group with the Exchange
2003 Routing Group.
We have about 6 AD Domains in one Forest. The Exchange 2003 and 5.5 Servers
are in different Domains. Name Resolution work, i can ping from server 5.5 to
server 2003 and vice versa using the netbios name as well as the fqdn.
When a User homed on the Exchange 2003 Server sends a Mail to a User in one
special Exchange 5.5 Site, the mail stucks up in the queue and never leaves
the Server. Turning on Diagnostic Logging (Maximum) i get the following
Events after sending a message to the problematic 5.5 Server:
MSExchangeTransport ID 4003
The domain 'msx55servername.domain.com' is currently unreachable ...
MSExchangeTransport ID 984
DestAddr=<5.5ServerName>, Type=<SMTP>
MsgType=0x0, NextHopType=CURRENTLY_UNREACHABLE
RouteAddr=<>
Connector=<DNS>
Especially the Last Error is interesting, compared to the same Event when it
works. Under NextHopType should be value like "next_routing_group" or
something like that. and under RouteAddr and Connector should be a value
representing the GUID of the Connector.
The Central Mailhub Server and the Exchange 2003 Server are located in the
same subnet with no firewall between them. the routing table gets updated
when i check it with winroute or looking at the turned on smtp log whicht
contains x-link2state entries between the two exchange 2003 servers.
the exchange 2003 server in the central mailhub site is dedicated as the
routing group master.
between the central mailhub server an the exchange 5.5 server in the
problem-site are 2 cisco pix firewalls that have all the necessary ports open.
mailflow from the problematic 5.5 server to the new exchange 2003 server
works fine, just the other direction is the problem.
ad and adc replication is also working without problems.
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in