Messaging Server 3.6 fails to start even though the Administration Server says "Success"

Question

Messaging Server 3.6 fails to start even though the Administration Server says
"Success". There are no entries in the log to help explain what has happened.
<P>
Any failure to start Messaging Server via Administration should be analyzed by
starting the server with /etc/NscpMail.
<P>
# /etc/NscpMail start
19991219004527:Dispatch:Notification:Network Module (IMAP4-Server) Failed the verify environment test.
Module not Loaded.
Startup Problem:
Problem Gaining Unique Lock
Netscape Messaging Server Exiting!
<P>
This error is caused by an inability to create the .netscape.mailID file
inside the top level of the postoffice.
<P>
# cd /var/spool/postoffice
# ls -la
total 30
dr-x------ 8 nobody nobody 512 Dec 19 01:06 .
drwxrwxr-x 13 root bin 512 Feb 12 1999 ..
drwx------ 2 nobody nobody 1536 Dec 19 01:04 config
drwx------ 2 nobody nobody 512 Dec 19 01:04 control
drwx------ 3 nobody nobody 512 Dec 19 01:04 deferred
drwx------ 2 nobody nobody 512 Dec 19 01:04 hold
drwx------ 2 nobody nobody 5120 Dec 19 01:04 log
drwx------ 2 nobody nobody 512 Dec 19 01:04 messages
-rw-r--r-- 1 root other 183 Apr 12 1999 sie.conf
-rw-r--r-- 1 root other 6 Dec 19 01:04 socket.dat
<P>
NOTE: The "." entry is the same as ls -l /var/spool/postoffice
<P>
# chmod u+w .
# /etc/NscpMail start
# ls -la
total 32
drwx------ 8 nobody nobody 512 Dec 19 01:04 .
drwxrwxr-x 13 root bin 512 Feb 12 1999 ..
-rw------- 1 nobody nobody 5 Dec 19 01:04 .netscape.mailID
drwx------ 2 nobody nobody 1536 Dec 19 01:04 config
drwx------ 2 nobody nobody 512 Dec 19 01:04 control
drwx------ 3 nobody nobody 512 Dec 19 01:04 deferred
drwx------ 2 nobody nobody 512 Dec 19 01:04 hold
drwx------ 2 nobody nobody 5120 Dec 19 01:04 log
drwx------ 2 nobody nobody 512 Dec 19 01:04 messages
-rw-r--r-- 1 root other 183 Apr 12 1999 sie.conf
-rw-r--r-- 1 root other 6 Dec 19 01:04 socket.dat

Answer 1

Hi,
Please check if you have disabled the autodisconnect feature of the Server service. On Windows servers it can be configured through the Autodisconnect registry key.
\HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\
CIFS and SMB Timeouts in Windows
http://blogs.msdn.com/b/openspecification/archive/2013/03/19/cifs-and-smb-timeouts-in-windows.aspx
Based on the research, as the open shared folder is in a SMB session, the default timeout for SMB session is 15 minutes. If the SMB session is inactive for 15 minutes the server will send a TCP reset to close the SMB connection. Until the
Autodisconnect timer is reached, the server will send an NBT keep-alive packet every two minutes. If a client or server application is not written to properly handle network delays, it may terminate the session prior to the default timeout
period.
For more detailed information, please refer to the thread below:
Session doesn't close Shared Folder
https://social.technet.microsoft.com/Forums/en-US/54f658c8-3d41-4beb-9a2f-47b054a11b7a/session-doesnt-close-shared-folder?forum=smallbusinessserver
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.