I did restart after modifying the registry. Here is the log file: 11/28/2010/9:32:36 AM SMTP threaded Message: 14323653120101128.SA622279-1, Failed to NetDial Connect, error description: Cannot find the phone book entry., error code: 0x800a5090 11/28/2010/9:32:36 AM SMTP threaded Message: 14323653120101128.SA622279-1, DUN connection needed, following localhost received to be used: 11/28/2010/9:32:36 AM SMTP threaded Message: 14323653120101128.SA622279-1, The following localhost value will be used for connecting: 192.168.5.32 11/28/2010/9:32:57 AM SMTP threaded Message: 14323653120101128.SA622279-1, Last Receive Message: Connecting to mail server. (I), Failed to POP Connect 11/28/2010/9:34:50 AM SMTP threaded Message: 14345082820101128.SA622279-1, Failed to NetDial Connect, error description: Cannot find the phone book entry., error code: 0x800a5090 11/28/2010/9:34:50 AM SMTP threaded Message: 14345082820101128.SA622279-1, DUN connection needed, following localhost received to be used: 11/28/2010/9:34:50 AM SMTP threaded Message: 14345082820101128.SA622279-1, The following localhost value will be used for connecting: 192.168.5.32 11/28/2010/9:35:11 AM SMTP threaded Message: 14345082820101128.SA622279-1, Last Receive Message: Connecting to mail server. (I), Failed to POP Connect
On Sun, Nov 28, 2010 at 7:30 AM, Dirk Bulinckx <[email protected] (mailto:[email protected])> wrote: Do know that Servers ALive v6.2 is NOT supported on Windows 2008(R2). Did you create the registry value and did you restart SA after it? If you do a test send , what does the logfile show? From: Servers Alive Discussion List [mailto:[email protected] (mailto:[email protected])] On Behalf Of Fry Guy Sent: Sunday, November 28, 2010 1:16 PM To: Servers Alive Discussion List Subject: [SA-list] Alternate SMTP port on Windows Server 2008? Is anyone running Servers Alive on a Windows 2008 Server R2 and sending SMTP mail alerts on a non-standard port? I've tried creating the registry values for a non-standard port per the documentation and an archived email from this list. Have had no success. Thank you! To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
