XFOR: SMTP Services Do Not Start Automatically After One Is Stopped (193686)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Commercial Internet System 2.0
This article was previously published under Q193686 SYMPTOMS
When you start multiple instances of the Simple Mail Transfer Protocol
(SMTP) service, use the Microsoft Management Console (MMC) to stop one
instance, and then stop Smtpsvc.dll from a command prompt, all other
instances of the SMTP service are stopped. If you then start Smtpsvc.dll
from a command prompt, the instance that you stopped using the MMC and any
other instances that were initially started after that instance, do not
start automatically. The instance that you stopped using the MMC does not
normally start automatically, but all other instances normally do.
CAUSE
When you stop an instance of the SMTP service, the service is
automatically configured so that it does not start automatically when you
start Smtpsvc.dll. The problem described in this article occurs because
Smtpsvc.dll does not automatically start any instances of the SMTP service
after it encounters one instance that is configured in this manner.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed this to be a problem in Microsoft Commercial
Internet System version 2.0.
This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
| Modification Type: | Major | Last Reviewed: | 6/28/2004 |
|---|
| Keywords: | kbbug kbfix kbQFE KB193686 |
|---|
|