Home / server / Questions / 390104
Accepted
Untalented
Asked: 2012-05-18 10:14:52 +0800 CST

SMTP, IMAP, and Web Issues on SBS 2003

  • 772

We just started having issues as of last night. Basically, all was good until I tried to add a users account to someones phone. It wasn't working and then noticed some activesync errors on the box. Per a KB article, it mentioned to add some reserved ports into the registry to resolve, and if the events continue to occur to remove the patch 951746 or 951748. Also, I can't get on the web whatsoever, but I can ping google and get a response.

In any case, I'm having issues now in that since last night around this time SMTP and IMAP will not start. Both give an error like "The service could not bind instance 1. The data is the error code.".

I checked netstat, but I don't see anything using or listening on SMTP or IMAP. I also tried to telnet to port 25, but don't get any connection.

There are no firewalls or AV enabled. Any help greatly appreciated while I wait on MS to give me a call back after opening this ticket.

windows-server-2003 exchange-2003 windows-sbs-2003 windows-sbs

2 Answers

  1. Without having any knowledge of the Patches you mentioned, I would check to make sure DNS is running on the server. It sounds to me like somehow the bindings got screwed up and caused the system services (DNS, SMTP, IMAP etc) to either go offline or refuse to start. All things being equal, check that you didn't update the Network Card Driver. And verify that it has the correct address.

    If SMTP isn't starting then trying to telnet to it will not work. But it is usually a good test to try it locally on the server back to itself using the loopback address (127.0.0.1). If that works, then it is probably just a setup issue. If it doesn't, then there is probably a service failure or it is set to NOT respond on 127.0.0.1.

    I did have one phone (one version of Motorola Android) that decided to slam the ActiveSync service. Something happened with the Mobile Device Partnership that caused it to repeatedly hit port 443. So might be worth taking a look at your web logs as well. (but that shouldn't have anything to do with SMTP and IMAP)

    • 0
  2. Best Answer

    It turns out there is an issue in SBS 2003 after applying certain patches. The DNS service eats up many available ports. Unfortunately, they were not showing as being used via netstat or TCPview. After shutting down the DNS Server service I was able to start the other services. I then restarted DNS and it was okay.

    I've still got a ticket open looking into a real fix, but this is a valid workaround.

    • 0