Exchange issues

Had some odd problems after an update failed to apply correctly to my exhcange/ad server. After reboot we are no longer able to access OWA except via the loopback (ie https://localhost/owa or  https://127.0.0.1/owa). Cannot access OWA using FQDN, hostname or Static IP address.

Also, Outlook 2010 clients cannot change their Out of Office messages. They receive the error: "Your automatic reply settings cannot be displayed because the server is unavailable..."

In IIS manager > Default Website > SSL Settings. If I uncheck Require SSL I am able to access OWA using FQDN, etc. but only via http, not https, but this does not resolve the Out of Office issue
Ignimous VondlechanceAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Miguel Angel Perez MuñozCommented:
Could you check your firewall configuration? seems something is blocking TCP 443 traffic.
Ensure your server opens and listen on 443 (netstat -an | find "443" from command prompt)
0
tshearonCommented:
Open IIS on the server and check the default website has the right bindings. Right click 'default website' and select 'edit bindings.' In this case make sure 'https' is bound to either 'all unassigned' or the actual IP of the server you want users to connect to via OWA.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ignimous VondlechanceAuthor Commented:
TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
 TCP    192.168.1.11:443       192.168.1.100:50699    ESTABLISHED
 TCP    192.168.1.11:63958     74.125.204.84:443      ESTABLISHED
 TCP    192.168.1.11:63965     74.125.237.104:443     ESTABLISHED
 TCP    192.168.1.11:63972     50.31.164.165:443      ESTABLISHED
 TCP    192.168.1.11:63983     74.125.237.203:443     ESTABLISHED
 TCP    192.168.1.11:63985     220.244.223.84:443     ESTABLISHED
 TCP    [::]:443               [::]:0                 LISTENING
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Ignimous VondlechanceAuthor Commented:
I change the binding from All Unassigned to the server IP and this fixed the OWA issue. No good on the Outlook client front though
0
tshearonCommented:
Check that the EWS virtual directory has authentication settings of anonymous, windows and basic auth set. If not set them and reset iis.
0
tshearonCommented:
I changed my last post. I meant to say EWS virtual directory.
0
Ignimous VondlechanceAuthor Commented:
ECP & EWS VD already had the following settings:

Anonymous Authentication | Enabled |
Basic Authentication | Enabled | HTTP 401 Challenge
Windows Authentication | Enabled | HTTP 401 Challenge
0
tshearonCommented:
Can you check your EWS settings and make sure they are correct. Specifically the correct Internal and External URLS along with some auth settings. To do so you should open EMS and run 'Get-WebServicesVirtualDirectory |fl name,internalUrl,externalUrl,*auth*
0
tshearonCommented:
You can also perform an auto-configuration test with your Outlook client. It may help you find the OOF problem. I am sure it is Virtual Directory related however. Sounds like an IIS update got busted up.
0
Ignimous VondlechanceAuthor Commented:
OOF has started working without any additional changes. Any idea why  All unassigned setting stopped working?
0
tshearonCommented:
Probably because the failed update. I am sure it was IIS related. Glad it is running now for you.
0
Ignimous VondlechanceAuthor Commented:
Thanks for your help! Saved my bacon!
0
tshearonCommented:
Glad I could help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.