Setup -2003-2007 exchange enviro -2k7CAS -ISA 2006 -2 Single-name Certs Scenario - 2 ips, 2 virtual dir. AutoDiscoverServiceInternalUri: https://autodiscover.DOMAINNAME.com:4443/autodiscover/autodiscover.xml I did this because we have a weblistener on 443 already in ISA. When I do a test-outlookservices -Idenity user@domain.com | fl Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address user@domain.com. Id : 1007 Type : Information Message : Testing server CAS.DOMAIN.com with the published name https://CAS.DOMAIN.com/EWS/Exchange.asmx & https://CAS.DOMAIN.com/EWS/Exchange.asmx. Id : 1019 Type : Information Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://autodiscover.DOMAIN.com:4443/autodiscover/autodiscover.xml. Id : 1006 Type : Information Message : The Autodiscover service was contacted at https://autodiscover.DOMAIN.com:4443/autodiscover/autodiscover.xml. Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at https://CAS.DOMAIN.com/EWS/Exchange.asmx. The elapsed time was 124 milliseconds. Id : 1015 Type : Information Message : [EXCH]-The OAB is not configured for this user. Id : 1014 Type : Success Message : [EXCH]-Successfully contacted the UM service at https://CAS.DOMAIN.com/UnifiedMessaging/Service.asmx. The elapsed time was 0 millis econds. Id : 1016 Type : Success Message : [EXPR]-Successfully contacted the AS service at https://CAS.DOMAIN.com/EWS/Exchange.asmx. The elapsed time was 31 milliseconds. Id : 1015 Type : Information Message : [EXPR]-The OAB is not configured for this user. Id : 1014 Type : Information Message : [EXPR]-The UM is not configured for this user. Id : 1017 Type : Success Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://CAS.DOMAIN.com/Rpc. The elapsed time was 0 milliseconds. Id : 1006 Type : Success Message : The Autodiscover service was tested successfully. but when I check with outlook "Test Email AutoConfiguration.." I get a TIMEOUT on the "https://autodiscover.DOMAINNAME.com:4443/autodiscover/autodiscover.xml" site Note: I also used the script below to bind the hostnames cscript adsutil.vbs set /w3svc/1/secure bindings ":443:CAS.domain.com" and cscript adsutil.vbs set /w3svc/5606/secure bindings ":4443:autodiscover.domain.com"

Why the extra 4 in 4443? Is the autodiscover virtual directory published through ISA? PS wouldn't traverse ISA, but Outlook would. Mike Crowley Check out My Blog!

I used the extra 4 because I have a Listener on https already in ISA. I tried turning the proxy off on my machine but still not working.

Can you connect to that directory from a browser? Did you update the autodiscover url to include the extra 4? This sounds like it could work, but its a step off the beaten path and makes me wonder if it's not interfering. Are the IIS bindings updated to accept this new port? Mike Crowley Check out My Blog!

>>Can you connect to that directory from a browser? https://autodiscover.DOMAIN.com:4443/autodiscover/autodiscover.xml <?xml version="1.0" encoding="utf-8" ?> - <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> - <Response> - <Error Time="10:43:37.7055075" Id="3051913805"> <ErrorCode>600</ErrorCode> <Message>Invalid Request</Message> <DebugData /> </Error> </Response> </Autodiscover> >>Did you update the autodiscover url to include the extra 4? AutoDiscoverServiceInternalUri: https://autodiscover.DOMAINNAME.com:4443/autodiscover/autodiscover.xml >>Are the IIS bindings updated to accept this new port? Redirect request to HTTP port 4443 Redirect request to SSL port 4443 The Traffic tab is still set to HTTPS, and the listener is on 4443.

since you adjusted the internal uri, this means local clients will be resolving to autodiscover.domainname.com and making a connection on 4443. does ISA allow this connection from inside the network? Mike Crowley Check out My Blog!

Do you mean do I have a SSL Tunnel for 4443? if so then Yes. I thought of this aswell but no dice.

-ttt

Hi, I have setup a lab and I can reproduce the issue. So I capture a netmon(when we run test emailautoconfiguration) and found that 4443 did not consider to be the port for https. Also outlook do not get any response from Exchange Server on port 4443. Besides, This issue has been reported as a known issue. We cannot change the port. It has been hardcoded. I found another thread which is the same error like yours, our engineers do recommend to use the default port for those Exchange Services. Regards, Xiu

Aha ok this makes sense! Perhaps put a note on http://technet.microsoft.com/en-us/library/bb125157.aspx to remind people of this. Mike Crowley Check out My Blog!