| Author |
Reboot necessary after every little change in configuration!
|
|
|
| I made the observation (of course the hard way) that one
needs to reboot the server (2003 SE) after any little change
one makes in the configuration settings (just restarting the
services is not sufficient!). Otherwise SMTP and NNTP
stop functioning. It took me almost a whole week to get
SMTP and NNTP to work.
I think there is a BIG bug in this software.
| |
| Jeff Cochran 2005-02-05, 2:47 am |
| On Sat, 5 Feb 2005 04:41:33 +0100, "info" <info@nogashi.com> wrote:
>I made the observation (of course the hard way) that one
>needs to reboot the server (2003 SE) after any little change
>one makes in the configuration settings (just restarting the
>services is not sufficient!). Otherwise SMTP and NNTP
>stop functioning. It took me almost a whole week to get
>SMTP and NNTP to work.
>I think there is a BIG bug in this software.
You'd need to define "little change" but your experience doesn't match
mine. In many cases you don't even need to restart the service.
Jeff
| |
|
| "Jeff Cochran" <jeff.nospam@zina.com> wrote in message
news:42094aeb.314450606@msnews.microsoft.com...
> On Sat, 5 Feb 2005 04:41:33 +0100, "info" <info@nogashi.com> wrote:
>
>
> You'd need to define "little change" but your experience doesn't match
> mine. In many cases you don't even need to restart the service.
My observation/tests showed that it is ALWAYS necessary to reboot
for the change to take effect.
Can you list the cases when it is (not) necessary to restart the service(s)
(BTW which services at all; IIS too ?), and when a reboot is necesary
in configuring SMTP and NNTP?
|
|
|
|