Re: Microsoft Exchange 2007 and port 80?

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Wed, 12 Aug 2009 11:39:03 -0700 (PDT), John <techstorm@xxxxxxxxxxx>
wrote:

On Aug 11, 7:29 pm, "Rich Matheisen [MVP]"
<richn...@xxxxxxxxxxxxxxxxxxxxx> wrote:
Oh . . . I'd be remiss if I dodn't mention running the Exchange Best
Practices Analyzer. Fix the serious stuff. Try to fix the stuff it
points out as less serious. The fewer things there are that out of
line the easier it'll be to figure out what's wrong.

And when things stop, there's also the mail-flow troubleshooter in the
toolbox. Make sure you run it once before you have a problem so you
have the latest version on the machine.
---
Rich Matheisen
MCSE+I, Exchange MVP

So apparently it is every 5 days because mail flow on the Exchange
server stopped again today. I ran the mailflow troubleshooter and I
did get two red errors that simply said, "Error submitting mail. Mail
submission failed: Error message: Server does not support secure
connections." It actually says the same thing twice. I do know that
our 3rd party SSL certificate is current and working because I can log
into the OAW using https://mail.ourdomainname.com/owa

Not supporting secure connections doesn't mean that there's a problem
with a certificate. Not /having/ a certificate would cause that. Not
allowing TLS would cause that. But a simple "telnet
<your-servers-ip-address> 25" and then entering "EHLO domain.com"
would show you if there's a STARTTLS in the set of keywords.

I ran the Best Practices Analyzer and the only two errors it found
were that a storage driver for the RAID card was 2 years old and we
were allowing all Outlook clients (2000-2007). So nothing major there.
I needed to get email working again. So I opened up the router config
page, changed port 80 back to the Exchange. Immediately email began
coming in and going out.

You still haven't said whether or not you can connect to port 25 on
your server at that time. Or if your server can connect to other MTAs
on port 25. Since mail uses at port you really haven't done much more
than point a finger at the router as being the casue of the problem.

I went back to the router page, changed port
80 back to the web server. Mail is still coming in from outside
senders and they can send to anyone.

That'd be significant if SMTP used port 80. It doesn't.

I noticed that the errors I posted earlier are happening very
frequently.

The two errors (not the other 'warning' and 'information' events)
point to a problem communicating with the AD. That'll definitly casue
problems.

It fills up the Event logs and are showing up at least
every 15 minutes.

Five events every 15 minutes will take an awfully long time to fill up
a normal sized event log.

I can't help but believe that the errors are telling
me what's wrong but I can't find anything on the net about them on the
internet.

Try clicking on the link in the "Description" of the event.

When I google the error "Process MSEXCHANGEADTOPOLOGY
(PID=1680). The site monitor API was
unable to verify the site name for this Exchange computer" the first
site to come up is the one where I am posting this message from! I
can't be the first person to ever see this error. At least for now I
know how to fix it even if it is only temporary.

I don't think you're fixing anything. If monkeying around with your
router (or firewall) makes things work, but they go back to NOT
working later then I'd sure be looking at the way the network is set
up -- especially if the Exchange server and AD aren't separated by a
firewall.
---
Rich Matheisen
MCSE+I, Exchange MVP
.

Relevant Pages

  • RE: DNS and Exchange issues
    ... with the Exchange Server after you have installed the patch 888619. ... XFOR: Telnet to Port 25 of IMC to Test IMC Communication: ... Start Exchange System Manager. ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, ...
    (microsoft.public.exchange.setup)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.admin)
  • Re: Exchange 2003 - POP3 only delivers email to Administrator
    ... Server to allow internet users access Exchange through POP3 services, ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.setup)