JohnnyD74
asked on
Exchagne 2010 OWA "Page Cannot Be Displayed"
Hello Folks,
We have an install of Exchange 2010 and OWA has not been working for several days. When I try to access it with IE, it says "The Website Cannot Display the Page". I am not sure where to start. Can anyone assist?
We have an install of Exchange 2010 and OWA has not been working for several days. When I try to access it with IE, it says "The Website Cannot Display the Page". I am not sure where to start. Can anyone assist?
ASKER
Hello Clonyxlro,
IIS is running and I did not make any changes since it stopped working. I will try the article...thanks.
IIS is running and I did not make any changes since it stopped working. I will try the article...thanks.
With issues like this, I like to start at https://testconnectivity.microsoft.com/
Most likely a DNS change that is affecting your service, if IE cannot display the page.
Can you access owa internally via http://localservername/owa ?
Most likely a DNS change that is affecting your service, if IE cannot display the page.
Can you access owa internally via http://localservername/owa ?
ASKER
Hello and thank you! it is not DNS as I cannot access intenally or even on the server desktop from http://localservername/owa.
ASKER
Sorry, what about https://localservername/owa
If that doesnt work, try opening a telnet session to localservername 443
Perhaps a firewall issue?
Failing that, what is the internal url and external url set to?
From EMS, run this command:
get-owavirtualdirectory | fl and verify the internal and external url.
If that doesnt work, try opening a telnet session to localservername 443
Perhaps a firewall issue?
Failing that, what is the internal url and external url set to?
From EMS, run this command:
get-owavirtualdirectory | fl and verify the internal and external url.
If the server is listening on 443 internally, then verify that 443 is forwarding on your router/firewall to the internal server.
If it is not responding internally, then it appears as mentioned by @JohnnyD74 that IIS is having some issues. Restart the World Wide Web Publishing service by running services.msc > World Wide Web Publishing Service > right-click > restart.
Since Autodiscover failed as well, do you have an autodiscover CNAME setup in your registrar's DNS?
If it is not responding internally, then it appears as mentioned by @JohnnyD74 that IIS is having some issues. Restart the World Wide Web Publishing service by running services.msc > World Wide Web Publishing Service > right-click > restart.
Since Autodiscover failed as well, do you have an autodiscover CNAME setup in your registrar's DNS?
ASKER
Thanks again :-) Even when I am logged on to the desktop of the exchange server and go to https://localservername/owa , I still cannot access. There are no firewalls running on the server.
ASKER
I tried to restart the World Wide Web Publishing service but same problem.
What about the telnet session? Does it time out or connect?
Try https://internalipaddress/owa
And also, telnet to the internal IP on 443.
Do any of those respond?
Try https://internalipaddress/owa
And also, telnet to the internal IP on 443.
Do any of those respond?
Could you post a screenshot of your OWA tab in EMC?
Server Configuration > Client Access > Outlook Web App tab.
See attached screenshot.
Screen-Shot-2013-10-25-at-10.53..png
Server Configuration > Client Access > Outlook Web App tab.
See attached screenshot.
Screen-Shot-2013-10-25-at-10.53..png
If you can connect via the IP address internally, then it most definitely is a DNS configuration issue. What has changed in the environment recently?
Also, are you still getting mail? Are there more than one server in the environment?
Also, are you still getting mail? Are there more than one server in the environment?
ASKER
Hi,
I tried to telnet but got no reponse. Here is a screenshot but I blocked out the addresses for security purposes. http://screencast.com/t/arbSv2rZ
I tried to telnet but got no reponse. Here is a screenshot but I blocked out the addresses for security purposes. http://screencast.com/t/arbSv2rZ
ASKER
We have just one exchange server. I cannot connect with the IP internally and am not aware of any changes recently. I am still getting email via Outlook however.
On the exchange server, can you open a command prompt and do netstat -aon
See if the server is listening on 443.
If it is, then revisit firewall and see if something has been turned on that shouldnt be.
See if the server is listening on 443.
If it is, then revisit firewall and see if something has been turned on that shouldnt be.
If it is not, then IIS is not working properly, per @clonyxlro
Secondly, if you ping the server does it respond on IPv4 or IPv6?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes...it looks like it is listening as shown: http://screencast.com/t/6IzfZeGgo3q
I tested OWA directly on the server so this eliminates the firewall.
I tested OWA directly on the server so this eliminates the firewall.
did you restart Microsoft Exchange Forms-Based Authentication service ?
some how i can not browse http://screencast.com/t/6IzfZeGgo3q (due to IS Policy).
and the best effort i will ask you try that..restart the exchange server. because you are saying nothing is changed and IIS config is also not changed.
please share the output
some how i can not browse http://screencast.com/t/6IzfZeGgo3q (due to IS Policy).
and the best effort i will ask you try that..restart the exchange server. because you are saying nothing is changed and IIS config is also not changed.
please share the output
ASKER
Thank you so much! Resetting the exchange virtual directory per your recommended article below did the trick! It works fine now!
http://technet.microsoft.com/en-us/library/ff629372.aspx
http://technet.microsoft.com/en-us/library/ff629372.aspx
Is the IIS service is started?
You may also check this article too: http://blogs.technet.com/b/exchange/archive/2008/12/31/3406686.aspx