Exchange 2010 RPC over HTTP not working
We are trying to enable RPC over HTTP. The feature is enabled on the server. We have installed this on the CAS/HUB role servers (2 servers - HLB).
Within IIS 7, the authentication shows disabled within 20 minutes of changing the setting to allow Basic Authentication. If I change the setting, it goes back to 'disabled' and continues not to work.
Do I need to restart IIS to get this going? I thought that you could change the authentication without an IIS restart.
Within IIS 7, the authentication shows disabled within 20 minutes of changing the setting to allow Basic Authentication. If I change the setting, it goes back to 'disabled' and continues not to work.
Do I need to restart IIS to get this going? I thought that you could change the authentication without an IIS restart.
ASKER
Trying it now... Maybe I didn't reset IIS fast enough on the first attempt. Within 5 minutes, I refreshed and it was 'disabled' again.
I'll give it another 30 minutes to see if the change holds.
I'll give it another 30 minutes to see if the change holds.
ASKER
Still nothing after IIS restart. Basic Authentication under RPC keeps defaulting to 'Disabled'.
I tested using Outlook 2010 and checking the connection status. I came back after it wasn't connecting via HTTPS... trying then connecting via TCP/IP. I checked the servers and RPC was back to 'disabled'.
Are there any settings within Exchange 2010 that may be changing the authentication setting in RPC back to 'disabled'?
I tested using Outlook 2010 and checking the connection status. I came back after it wasn't connecting via HTTPS... trying then connecting via TCP/IP. I checked the servers and RPC was back to 'disabled'.
Are there any settings within Exchange 2010 that may be changing the authentication setting in RPC back to 'disabled'?
Execute this from the power shell:
Set-OutlookAnywhere -Name Server01 -ClientAuthenticationMetho
where server01 has to be you exchange server name
Set-OutlookAnywhere -Name Server01 -ClientAuthenticationMetho
where server01 has to be you exchange server name
ASKER
Even after using the cmdlet above within EMS, the Basic Authentication is still disabled.... I even tried enabling it after the cmdlet. I did an IIS reset to lock in the change and nothing... still.
I don't know what could be causing this.
I don't know what could be causing this.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Should the change be reflect within IIS manager? If so, I'm not seeing it in the RPC application under Authentication.
Thanks
Thanks
ASKER
Disregard... the changes did show up in IIS. I'm now waiting to see if they hold.
THANKS!
THANKS!
ASKER
I'm having a hard time testing it since all of our machines are domain joined and onsite... they try HTTPS, but default over to TCP/IP after a few seconds.... I'm not sure if RPC over HTTP is working just yet, but the settings are staying within IIS. This is a good start.
iisreset /noforce