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

OWA Stops responding after running ActiveSync

Hi Experts,

This's URGENT Please.

OWA all of a sudden stopped responding with a "HTTP Error 404 - File or directory not found". This happened as i remember after we configured Activesync to work.

Both HTTPS and HTTP OWA are not working.

Any Suggestions ??

Regards,
0
ashkaat
Asked:
ashkaat
  • 7
  • 3
1 Solution
 
ashkaatAuthor Commented:
Hi Guys,

Something strange happened now. I removed the SSL configuration from the IIS to see if this's what's causing the problem. But, HTTP didn't also open.

I then followed the second method mentioned in this article:
http://support.microsoft.com/kb/298513/en-us

I deleted DS2MB, restarted the services as mentioned and then OWA HTTP worked again.

I then tried to configure IIS again to work with SSL .. Guess what, OWA Stopped again !!

P.S: Both HTTPS and HTTP was working well a couple of days ago. !!


Any Suggestions Guys ??
0
 
ashkaatAuthor Commented:
Does this have anything to do with my CA ??
0
 
VahikCommented:
http://support.microsoft.com/kb/817379

if u have a single exchange u must use this article to configure ur exchange server for OMA and activesync to work with SSL...
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
ashkaatAuthor Commented:
Dear Vahik,

I'm having a Frontend-Backend Topology.
0
 
Stacy SpearCommented:
Did you check the IIS admin and www service on the front and back end servers?

More detail on what you mean by "Both HTTPS and HTTP OWA are not working". Any errors, whats it giving, etc.
0
 
ashkaatAuthor Commented:
Dear Darkstar,

IIS admin and WWW services are running on both Servers. No Errors in the Eventvwr.

The OWA just giving me "404 Error, File or Directory not found"
0
 
ashkaatAuthor Commented:
Hi Guys,

I resolved part of the problem. It's now working with HTTP, HTTPS internally. I reinstalled the CA and reissued the Certificates.

The Problem now is HTTPS is not working from Outside, so when i try to access "https://mymail.domain.com" it's not opening anything.

I monitored ISA 2004 for this and found that the traffic from the external client stops at the ISA Server, i get:

192.168.1.2      443      HTTPS      Initiated Connection      62.114.248.64      External      Local Host
192.168.1.2      443      HTTPS      Closed Connection      62.114.248.64      External      Local Host


"192.168.1.2" Is the External Interface for ISA.
0
 
Stacy SpearCommented:
Are you allowing 443 to the exchange server? Did the https://mymail.domain.com timeout, error 404, error 500, etc?
0
 
ashkaatAuthor Commented:
Dear Sarkstar,

I'm allowing all the traffic including 443 from ISA to the Exchange Servers, and i can open "https://mymail.domain.com" from the ISA Server itself.

When i try to open it from outside, i get "The Page can't be displayed"
0
 
Stacy SpearCommented:
Are you allowing external secure connections at the exchange server? And are you sure that it is accepting 443 connections internally? for instance https://servername/exchweb works and shows an OWA logon?

If not its not accepting local 443 either. Most likely if you are allowing all traffic to hit exchange, then your IIS on exchange isn't configured to allow remote 443 only local.

The following tool is great at showing which ports are available.

http://insecure.org/nmap/ 
0
 
ashkaatAuthor Commented:
Dear Darkstar,

Thanks for you help. I solved it.

I just restarted DC, Both Exchange Servers, and ISA. and Everything worked again.

Thanks for your help anyway,
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

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