Ignimous Vondlechance
asked on
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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
ASKER
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
Check that the EWS virtual directory has authentication settings of anonymous, windows and basic auth set. If not set them and reset iis.
I changed my last post. I meant to say EWS virtual directory.
ASKER
ECP & EWS VD already had the following settings:
Anonymous Authentication | Enabled |
Basic Authentication | Enabled | HTTP 401 Challenge
Windows Authentication | Enabled | HTTP 401 Challenge
Anonymous Authentication | Enabled |
Basic Authentication | Enabled | HTTP 401 Challenge
Windows Authentication | Enabled | HTTP 401 Challenge
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-WebServicesVirtualDir
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.
ASKER
OOF has started working without any additional changes. Any idea why All unassigned setting stopped working?
Probably because the failed update. I am sure it was IIS related. Glad it is running now for you.
ASKER
Thanks for your help! Saved my bacon!
Glad I could help.
Ensure your server opens and listen on 443 (netstat -an | find "443" from command prompt)