This thought just crossed my mine.I work remotely on a Solo Win 2K3 server with Exchange 2007.I recently restarted the Server remotely, and cause all admin accounts to log off.So heres my question? Its late and I can never remember the answer.Does the server need someone to always be logged in to actually have everything running properly?No bashing please.

Per my knowledge, the answer is no, because most of the services are running as system account, not user account. Notes: This forum is for exchange related issue, if you have any further question about this case, please use “Windows Server” forum which would be the best place for the problemJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Oh I just thought I'd ask in this forum as per why my Exchange Server would stop receiving emails after a remote restart.

Could you provide more info? Is it a pure exchange 2007 environment, all server roles in a single box (MBX, HUB and CAS)? By stopping receiving mails, do you mean the incoming mail flow from internet? Does the internal mail flow still work? Does the outbound mail flow still work while the inbound mail flow is failed? Is there any error event in the application log on the exchange server during the issue? Does the external sender receive the NDR for undeliverable mails? Could you telnet exchange server and send the test mail? Please use Mail Flow Troubleshooter to check the mail flow on the exchange 2007 server Please run ExBPA against the exchange server for health checkJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

ok heres the setup.HUB, CAS and MBX are all in a single box.Internal to Internal works perfectly fine.Internal to Internet works perfect.Internet to Internal is intermittent. Sometimes works, and sometimes doesn't.No errors in the Evert Viewer for Exchange.The external user receives on the NDR:Reporting-MTA: dns; idcmail-mo1so.shaw.ca Final-Recipient: rfc822;Cory.Alexander@homeplanningcentre.comAction: failedStatus: 5.0.0 (permanent failure)Remote-MTA: dns; [64.18.4.10]Diagnostic-Code: smtp; 5.1.0 - Unknown address error 554-'No relaying allowed - psmtp' (delivery attempts: 0)Yes I can telnet and send mail no problem.MFT and ExBPA says everything is fine and healthy.

Can you tell the difference between the deliverable messages and the undeliverable? Usually, the server that generates the NDR messages is the possible cause of the issue. Please check the header info of the NDR message, can you see the generate server info in it? Please enable the protocol logging on the default receive connector (Receive the incoming mail flow) on the exchange server (Reference), and then reproduce the issue. It will let you to check SMTP communication between the sender and the exchange server Please increase diagnostic logging level for Transport Service on the exchange server, and reproduce the issue, see if there’s any related event on the transport server Get-EventLogLevel MSExchangeTransport |set-eventLogLevel -Level High Notes: Please don’t forget to reverse the setting back after the troubleshooting James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

FAILED NDRReturn-path: <>Received: from pd3mr2so-ssvc.prod.shaw.ca (pd3mr2so-ssvc.prod.shaw.ca [10.0.141.178]) by l-daemon (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0KW4006UMMOQOFZ0@l-daemon> for shift_d@shaw.ca; Tue, 12 Jan 2010 02:07:56 -0700 (MST)Received: from unknown (HELO idcmail-mo1so.shaw.ca) ([10.0.141.22]) by pd3mr2so-svcs.prod.shaw.ca with ESMTP; Tue, 12 Jan 2010 02:07:56 -0700Received: from localhost by idcmail-mo1so.shaw.ca; Tue, 12 Jan 2010 02:07:56 -0700Date: Tue, 12 Jan 2010 02:07:56 -0700From: Mail Delivery System <MAILER-DAEMON@shaw.ca>Subject: Delivery Status Notification (Failure)To: shift_d@shaw.caMessage-id: <8ca7sa$2umned@pd2mo1so.prod.shaw.ca>MIME-version: 1.0Content-type: multipart/report; report-type=delivery-status; boundary=5wrsS.4VFFzMsTz.1pXwjK.B1jAKIsX-Cloudmark-SP-Filtered: trueX-Cloudmark-SP-Result: v=1.0 c=1 a=MOoU6_y5KB8A:10 a=ctaZ9a5OAAAA:8 a=aj_2VA38k3xxiWW6bgwA:9 a=hfydqID2HxdakTNypHKWCSeSWMAA:4 a=P97b1yRG93kA:10 a=sBQHiDLlZEn-mfPaIEQA:9 a=jYqEAn1T-8ONLmak3rlya6FhqAIA:4 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=uMBTyOgPQqU9EWefQI0A:9 a=4QTZarzmnE0WIx_oMi0A:7 a=MhwJKm8mjXoSs7diUj3ZAOD1UoMA:4Original-recipient: rfc822;shift_d@shaw.ca From Event Viewer:Source: MSExchangeTransport Category:(12)The description for Event ID ( 12014 ) in Source ( MSExchangeTransport ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: homeplanningcentre.com.Source: MSExchangeTransport Category:(Devices)The description for Event ID ( 1022 ) in Source ( MSExchangeTransport ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Client RHINO, 5000.

What’s the idcmail-mo1so.shaw.ca server doing? There’s no difference between the deliverable message and the undeliverable? Please also check the protocol logging files, and have you increased the diagnostic logging level? Resources: TransportService EventID 12014 The description for Event ID ( nnnnn ) in Source ( XXXXX ) cannot be foundJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com