Re: MSExchange Transport Error Event ID: 4000

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Where exactly is server1 in relation to these servers (Remote1, Remote2 and
Remote3)?

Does server1 have any DNS servers listed on the properties of the SMTP
Virtual Server?

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Jim Harris" <JimHarris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:49A3BEEC-E569-4870-A4C5-82A12DAFF3C0@xxxxxxxxxxxxxxxx
I have an Exchange 2003 Server running on Windows Server 2003. Both are
Enterprise Edition. Exchange is SP2 and 2003 is SP1. I have 3 servers at
remote locations that are part of the administrative group. I have mail
sitting in the queues for 2 of the 3 remote servers. We will call the
three
servers Remote1, Remote2 and Remote3. I verified I can send mail to
Remote3.
Mail is stuck in the queues of Remote1 and Remote2 on the bridgehead
server
which I will call Server1. I tried forcing the connection of the queues
and
it does not work. I am getting Event ID: 4000 Source: MSExchange
Transport
Category: Connection Manager. Message Delivery to the remote domain
"mydomain.com" failed for the following reason: Destination server does
not
exist. I can ping both servers Remote1 and Remote2. NSLOOKUP is correct
for
forward and reverse lookup resolution. I tried RPCPing and it was
successful. I enabled diagnostic logging and Event ID: 4000 is the only
error I receive. I have seen this before and I am pretty sure if I reboot
it
would fix it but I would like to know if there is another fix and I can't
reboot until 8 hours from now. DCDIag and Netdiag both passed without any
failures.

Thanks in advance for the help


.

Relevant Pages

  • Re: configuration of 2 remote sites
    ... The users at the remote siites will need to access ... You should configure the sites and assign the proper subnets ... to these sites and then use IFM to promote the new additional servers, ... you're using different subnets you may want to setup WINS at these remote ...
    (microsoft.public.windows.server.active_directory)
  • Re: What happens to my W2K domain controllers
    ... Make sure you make the remote dc's gc's as well ... >> offices (running AD-integrated DNS) ... > 2003 member servers. ... >> 8) Run dcpromo on all four old W2k DCs to demote them to member servers. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Restricting access to a web server by IP
    ... > remote control clients, etc - we remotely ... > The agrument against is that mpst vulnerabilities seem to come through ... > servers, and blocking access to all IPs accept those on the allowed list - ...
    (comp.security.firewalls)
  • Re: Restricting access to a web server by IP
    ... > remote control clients, etc - we remotely ... > The agrument against is that mpst vulnerabilities seem to come through ... > servers, and blocking access to all IPs accept those on the allowed list - ...
    (alt.computer.security)
  • Re: MSAccess to Web App
    ... and almost by defintion remote. ... there are any applications running on a web. ... send information back and forth between clients and servers. ... what the client wanted but it's still a joke!). ...
    (comp.databases.ms-access)