[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

OWA access internally

Posted on 2012-09-12
20
Medium Priority
?
1,365 Views
Last Modified: 2012-09-19
We recently had a root-kit attack on our sbs2008 server. We believe we've cleaned up everything and everything is functioning normally except for the owa. I can access OWA by going to localhost/owa, log in, send/receive email, and it works great. But that is the only way that it can be accessed. I can't browse to it by IP address/owa or servername/owa.
We have confirmed we have the external DNS resolving to our external static IP correctly and that port forwarding is set up correctly. Users can still access outlook just fine on their PCs, but their smart phone accounts have stopped working. This DID work before the virus attack.

I'm very novice when it comes to IIS and OWA, but I just need to know where I should start looking for problems in this scenario.

Please let me know what additional information you require and I'll be happy to supply it.
0
Comment
Question by:deanavey
  • 12
  • 6
  • 2
20 Comments
 
LVL 9

Expert Comment

by:bharrington83
ID: 38391513
Did you confirm that the bindings are correct for the OWA site in IIS?
0
 

Author Comment

by:deanavey
ID: 38391688
The bindings do appear to be yes
0
 
LVL 9

Expert Comment

by:bharrington83
ID: 38391708
When you try to load the page from off the server, do you get any error messages or does it just time out?
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 

Author Comment

by:deanavey
ID: 38391710
It just times out and the browser says 'cant display webpage'
0
 

Author Comment

by:deanavey
ID: 38391712
When I ping externally I do get the correct static IP on the firewall
0
 
LVL 9

Expert Comment

by:bharrington83
ID: 38391717
Please post the bindings.
0
 
LVL 9

Expert Comment

by:bharrington83
ID: 38391728
It's not an issue of your firewall.  I got money on the bindings.  Please post what they are.  for example:  <All Available> : 443 or 192.168.0.8:80
0
 

Author Comment

by:deanavey
ID: 38392418
<All Available> : 80
<All Available> : 443
0
 
LVL 9

Expert Comment

by:bharrington83
ID: 38392433
And you are trying to connect via https://mail.contoso.com/OWA, correct?
0
 

Author Comment

by:deanavey
ID: 38392438
Yes that's correct
0
 
LVL 9

Expert Comment

by:bharrington83
ID: 38392449
Is RWW working?
0
 

Author Comment

by:deanavey
ID: 38392583
No. And actually, now localhost/owa isn't working either. The IIS site isnt even showing up
0
 

Author Comment

by:deanavey
ID: 38392597
Not Found

HTTP Error 404. The requested resource is not found.
0
 

Author Comment

by:deanavey
ID: 38392643
It was odd but the website were stopped. Started them back up but now receive this error:

HTTP Error 403.4 - Forbidden
The page you are trying to access is secured with Secure Sockets Layer (SSL).
0
 

Author Comment

by:deanavey
ID: 38392655
and then when using the https I get this: (the certificate is valid that I have selected for the 443 binding until 2013 from GoDaddy

localhost:443 uses an invalid security certificate.

The certificate is not trusted because the issuer certificate is unknown.
The certificate is only valid for the following names:
(listed local names)  

(Error code: sec_error_unknown_issuer)
0
 

Author Comment

by:deanavey
ID: 38392691
Ok.. incredibly odd...now localhost/owa works again...back to square 1 =)
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38393913
The first thing you should do is to rerun the Configure Internet Address Wizard -- this will repair your DNS settings and ensure all IIS bindings are correct.  Follow that with running the Fix My Network Wizard which will ensure everything else is correct.

If that process doesn't work, then you can reinstall the "Exchange Client Access Role" which is essentially OWA.

http://technet.microsoft.com/en-us/library/dd767439(v=ws.10)

Jeff
TechSoEasy
0
 

Accepted Solution

by:
deanavey earned 0 total points
ID: 38399934
Thanks for all the valuable information but nothing has worked so far. I think we're just going to revert to a backup of last week.
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38400183
Really?  You reinstalled the Exchange Client Access role and it didn't work?  Never heard of that happening.

Jeff
TechSoEasy
0
 

Author Closing Comment

by:deanavey
ID: 38412922
No expert solution worked. Virus may have done more damage than initially thought or visible.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to effectively resolve the number one email related issue received by helpdesks.
Steps to fix error: “Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Suggested Courses

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question