IIS6 Virtual SMTP server isn't coming back up automatically after a system restart

I've got a virtual server running Win2008 RC2. I've set up IIS6 with a virtual SMTP server on it to be the mail provider for the websites I'm hosting there. It all works great, but if for some reason the server reboots (auto updates are still enabled - I'm trying to make this as little work as possible as we've got a Lot of clients), the IIS6 doesn't restart the SMTP server. The failure causes 500 errors on the current setup, so I'm spending half the day apologising.

Any ideas?

In Services I've set everything to come back up automatically, but still no dice.

As soon as I restart the SMTP, no problems, all the mail gets sent. It's working perfectly, it just won't restart on it's own.

I'd really rather not turn auto updates off as we're such a small company I just can't spare the time to be manually updating 15 copies of windows every time MS decide there's a security patch.

All advice appreciated! BTW, I am a complete newb to these forums. I searched but couldn't find an answer, so please be nice. But firm. I've got to learn here.


Solution 1:

The SMPT server is probably set to start manualy to change it to automatic follow the steps below.

  1. Click Start
  2. In the Search box type Services then press enter
  3. Find IIS Admin Service in the list of services
  4. Double click IIS Admin Service, and set "Startup Type" to Automatic
  5. Find Simple Mail Transfer Protocol (SMTP) in the list of services
  6. Double click IIS Simple Mail Transfer Protocol (SMTP), and set "Startup Type" to Automatic
  7. Done! It should now start when automaticaly when your computer turns on

Solution 2:

I noticed in 2008, with IIS6 SMTP installed, the SMTPSvc is not set to automatically start, it's set to manual. You might try:

sc config smtpsvc start= auto

If that's not the right syntax (I don't have a machine with it handy at the moment), you can run services.msc, and find the SMTP service, and change it to automatic. Then give your server a quick reboot and see if that helps.