• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 341
  • Last Modified:

Exchange Server 2003 - Outlook 2003/2007 stopped working

Hello,

Hoping someone can help me with this.

What I have: Exchange Server 2003 SP2 standard running on Windows Server 2003 Standard. I have about 75 users using either Outlook 2003 and Outlook 2007 on a LAN or using RPC over HTTPS. I have OWA users and I have Blackberry users with Blackberry Enterprise Server and Mac users using the "Mail" program with IMAP.

The issue: Suddenly today all Outlook 2003/2007 and Blackberry clients stopped working and upon lauching Outlook receive an error message "Cannot open your default e-mail folders. Microsoft Exhcnage is not avaialble..." There have been no changes to the server recently and before today eveything was working without issue.

Details: Outlook 2003/2007 on the LAN and RPC over HTTPS does not work. Blackberries do not work. Outlook Web Access does work. Mac clients using IMAP works. I can ping and otherwise access the Exchange Server without issue. There are no errors in the Application or System logs. I tried running Outlook on multiple machines and I tried recreating profiles. All in all the server itself seems to be working. Email is flowing in and out, but Outlook and Blackberries have no access.

Any ideas anyone?

Thanks!

Joe
0
funkyjoe1
Asked:
funkyjoe1
1 Solution
 
jawad1481Commented:
Hi!

could you do one thing just for testing purpose. re -create one of the users windows profile. go to c:\documents and settings ------ and rename the profile of the one user ---- log off and log in again.

now try to access mailbox using Outlook.
0
 
Narayan_singhCommented:
As you said OWA is working fine and the Blackbery and RPC-HTTPS are not working
did u make any changes in certificate
for RPC-HTTPS check the connectivity using https://www.testexchangeconnectivity.com/
and see where it is failing
0
 
funkyjoe1Author Commented:
To jawad,

Tried that and still have the same issue

To Narayan,

I don't know if the cert is relevant in this case because Outlook when not using RPC over HTTPS also does not work. If I run Outlook on the LAN I have the same issue. Also, if OWA is working using HTTPS doesn't that confirm that my cert is working?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Narayan_singhCommented:
perform following command on exchange server to turn off tcp chimney
Netsh int ip set chimney DISABLED
0
 
Sourabh-ExcahngeCommented:
please let me know when you create a new profile are you able to do a check name
and check if you are getting any error in the application,system logs
1 thing you can do to is try to configure the profile over the NTLM authentication
while creating a profile -- more settings -- security tab --- drom the dropdown box choose NTLM
if this works
got to start - run - \\exchange server name and check if you get share
2 go to start - run - control keymgr.dll and check if you have any cashed password if there are some please remove that
0
 
funkyjoe1Author Commented:
Narayan,

I tried the netsh command earlier today and it didn't work.

C:\>Netsh int ip set chimney DISABL
The following command was not found: int ip set chimney DISABLED.
0
 
funkyjoe1Author Commented:
Sourabh,

Check name works. All authentication seems to be fine.
0
 
Narayan_singhCommented:
try to remove exchange attribute of one user and again reconnect the mailbox and see if that helps or create new user all together and then create OL profile
0
 
funkyjoe1Author Commented:
Hi Narayan,

Tried it. Still no luck.
0
 
MesthaCommented:
If it is all users, have you rebooted the server?
What has changed? Access to Exchange doesn't stop for zero reason, something has changed somewhere.

Simon.
0
 
funkyjoe1Author Commented:
Hi Mestha,

Yes. All users are affected. I haven't re-booted the server yet because I'm forced to wait until after hours. Users can use OWA and IMAP so I had to let them get though the day. Since it's Outlook 2003/2007 on the LAN and for remote users using RPC over HTTPS as well as Blackberry users on BES, is there something common among those three methods of connecting that I can look at?
0
 
John HurstBusiness Consultant (Owner)Commented:
The last (and the only) time I had an Outlook Exchange problem at a client (worse than yours, I admit), I called Microsoft. They logged in, held my hand, worked me through it and fixed it same day. Given now the elapsed time here, if a re-start does not solve the problem, do call Microsoft.
... Thinkpads_User
0
 
funkyjoe1Author Commented:
All,

Problem solved. I finally got the okay to restart Exchange and that resolved the problem. The bummer of that is I still don't know exactly what the problem was. Is it possible it was some sort of RPC issue? When I did Start > run and entered Outlook /rpcdiag on my RPC over HTTPS client my "Directory" HTTPS connection showed as "Established," but my "Mail" connection hung up at "Connecting."  It would hang there indefinitely or until I force quit Outlook.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now