none
Outlook 2007 Disconnecting fro Exchange Server 2003 RRS feed

  • Question

  • My hosted exchange server support rep was unable to help.  Outlook 2007 works perfect using Outlook Anywhere from any place having internet...I just can’t get outlook to work in my office!  2 of 4 users in office do not have issues, while me and one other constantly get disconnected from Microsoft Exchange, and then reconnected - but email NEVER comes down.  OWA works fine from office, and as I stated it works great outside the office (so I go to Panera Bread to actually get something done).  COMCAST is ISP and pretty fast.  Can anyone help?

    Saturday, July 30, 2011 4:25 AM

Answers

  • Generally if just one or few users are affected, the issue is likely caused by the client side. My suggestion is:

     

    1.    Verify from the client side:

     

    1)    Run Outlook in Online mode to see if the issue continues. If the issue continues, the issue might be caused by the local OST file. Delete it and then try again.

    2)    Run Outlook in safe mode, or reboot your computer into safe mode with network connection. It will help us isolate the fault from third party applications or add-ins.

    3)    Logon your user account into the computer that has not encounter this issue, test to see if it is working fine.

     

    2.    Verify the vent log on the server side (ask your hosted supporter who is administrative your server to do so):

     

    Increase the diagnostics Logging in Mailbox understand MSExchangeIS from Exchange 2003 mailbox server; and then reproduce this issue to see if there is any event log occur.

    Also, increase the diagnostics logging in MSExchangeSA item to see if there is any error.

     

     

    3.    Collect network trace log for further analysis (you and your hosted supported need to work together):

     

    Download the network trace monitor tool and enable it in both side, then collect the log when the issue occurs.

     

    How to use Network Monitor to capture network traffic

    http://support.microsoft.com/kb/812953

    How to capture network traffic with Network Monitor

    http://support.microsoft.com/kb/148942

    (working) TCP network monitor trace explained.

    http://blogs.msdn.com/b/spike/archive/2009/02/27/working-tcp-network-monitor-trace-explained.aspx

     

    hope it is helpful. Please keep me posted.


    Fiona
    Tuesday, August 2, 2011 7:09 AM
    Moderator

All replies

  • Have ssen issues when DNS servers cannot handle SRV records. Don't know if your hoster use this for clients but there is a chance they do.

    Verify DNS settings on your clients and your local Name Server to see if SRV records resolv correctly


    lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com
    Saturday, July 30, 2011 8:39 AM
  • Generally if just one or few users are affected, the issue is likely caused by the client side. My suggestion is:

     

    1.    Verify from the client side:

     

    1)    Run Outlook in Online mode to see if the issue continues. If the issue continues, the issue might be caused by the local OST file. Delete it and then try again.

    2)    Run Outlook in safe mode, or reboot your computer into safe mode with network connection. It will help us isolate the fault from third party applications or add-ins.

    3)    Logon your user account into the computer that has not encounter this issue, test to see if it is working fine.

     

    2.    Verify the vent log on the server side (ask your hosted supporter who is administrative your server to do so):

     

    Increase the diagnostics Logging in Mailbox understand MSExchangeIS from Exchange 2003 mailbox server; and then reproduce this issue to see if there is any event log occur.

    Also, increase the diagnostics logging in MSExchangeSA item to see if there is any error.

     

     

    3.    Collect network trace log for further analysis (you and your hosted supported need to work together):

     

    Download the network trace monitor tool and enable it in both side, then collect the log when the issue occurs.

     

    How to use Network Monitor to capture network traffic

    http://support.microsoft.com/kb/812953

    How to capture network traffic with Network Monitor

    http://support.microsoft.com/kb/148942

    (working) TCP network monitor trace explained.

    http://blogs.msdn.com/b/spike/archive/2009/02/27/working-tcp-network-monitor-trace-explained.aspx

     

    hope it is helpful. Please keep me posted.


    Fiona
    Tuesday, August 2, 2011 7:09 AM
    Moderator