Have a valid certificate and correct DNS entries, but getting this error id: 1019 When contacting https://..... /autdiscover/autodiscover.xml receive the error the underlying connection was closed. An unexpected errored on a send. And then on the next row: xml received the error authentication failed because the remote party has closed the transport stream". Any ideas? PS] C:\Documents and Settings\Administrator.GASTON>test-outlookwebservices | fl Id: 1003 Type: Information Message : About to test AutoDiscover with the e-mail address DNS entries, but getting this error id: 1019 When contacting https://..... /autdiscover/autodiscover.xml receive the error the underlying connection was closed. An unexpected errored on a send. And then on the next row: xml received the error authentication failed because the remote party has closed the transport stream". Any ideas? PS] C:\Documents and Settings\Administrator.GASTON>test-outlookwebservices | fl Id: 1003 Type: Information Message : About to test AutoDiscover with the e-mail address Administrator@ourdomain.com. Id: 1007 Type: Information Message : Testing server GAExchange3.gaston with the published name https://gae xchange3.gaston/ews/exchange.asmx & https://gaexchange3.gaston/ews/ex change.asmx. Id: 1019 Type: Information Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://gaexchange3.gaston/autodiscover/autodi scover.xml. Id: 1013 Type: Error Message : When contacting https://gaexchange3.gaston/autodiscover/autodiscover. xml received the error The underlying connection was closed: An unexp ected error occurred on a send. Id: 1013 Type: Error Message : When contacting https://gaexchange3.gaston/autodiscover/autodiscover. xml received the error Authentication failed because the remote party has closed the transport stream. Id: 1006 Type: Error Message : Failed to contact AutoDiscover

I am experiencing a very similar problem to this.Outlook clients fail to successfully access the autodiscover service and when I run test-outlookwebservices I get the following output.Id : 1003Type : InformationMessage : About to test AutoDiscover with the e-mail address XXXId : 1007Type : InformationMessage : Testing server oscar.hq.sarsensoft.co.uk with the published name https://XXX/EWS/Exchange.asmx & .Id : 1019Type : InformationMessage : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://XXX/Autodiscover/Autodiscover.xml.Id : 1013Type : ErrorMessage : When contacting https://XXX/Autodiscover/Autodiscover.xml received the error The underlying connection was closed: The connection was closed unexpectedly.Id : 1006Type : ErrorMessage : Failed to contact AutoDiscover----Output from get-autodiscovervirtualdirectory isName : Autodiscover (Default Web Site)InternalAuthenticationMethods : {Basic, Ntlm}ExternalAuthenticationMethods : {Basic, Ntlm}BasicAuthentication : TrueDigestAuthentication : FalseWindowsAuthentication : TrueMetabasePath : IIS://XXX/W3SVC/1/ROOT/AutodiscoverPath : C:\Program Files\Microsoft\Exchange Server\ClientAccess\AutodiscoverServer : XXXInternalUrl : ExternalUrl : AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0)DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=XXX,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=XXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XX,DC=XXX,DC=co,DC=ukIdentity : XXX\Autodiscover (Default Web Site)Guid : 734ed468-bdc0-4ecc-9c1c-a4d1439db6a4ObjectCategory : XXX/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-DirectoryObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}WhenChanged : 08/10/2007 21:00:59WhenCreated : 08/10/2007 21:00:59OriginatingServer : XXXIsValid : TrueIm pretty sure I have DNS and certificates running correctly, does anyone have some ideas about this?Cheers!

I am experiencing the exact same problem. Did anyone ever get an update on this?

Hi, I cant rememeber exactly how I fixed this - was some time ago. I think I had somehow messed up the configuration inIIS so in the end i reinstalled the client access bits and it started working again.