Problems connecting to Exchange Server via Outlook, Outlook Web Access and Remote Desktop Connection
Hi, When using the external domain name exchange.alluremedia.com.au to attempt to connect to the Exchange server using the local area network, the connection fails. Additionally, the issues described below do not occur when trying to connect from outside the local area network. For example: When attempting Auto Account Setup for Outlook, the following occurs. Your Name and E-mail Address are automatically populated. After clicking Next > Setup searches for server settings, the process fails and a message "Problem Connecting to Server" appears. When running Test-OutlookWebServices | fl on the Exchange Management Shell, the process fails with the following output. [PS] C:\Windows\system32>Test-OutlookWebServices | fl Id : 1003 Type : Information Message : About to test AutoDiscover with the e-mail address kaan.kivilcim@alluremedia.com.au. Id : 1007 Type : Information Message : Testing server Freya.corp.alluremedia.com.au with the published name https://exchange.alluremedia.com.au/EWS/Exchange.asmx & . Id : 1019 Type : Information Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://exchange.alluremedia.com.au/Autodiscover/Autod iscover.xml. Id : 1013 Type : Error Message : When contacting https://exchange.alluremedia.com.au/Autodiscover/Autodiscover.xml received the error Unable to connect to the remote server Id : 1013 Type : Error Message : When contacting https://exchange.alluremedia.com.au/Autodiscover/Autodiscover.xml received the error A connection attempt failed because the conne cted party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 203.206. 210.72:443 Id : 1006 Type : Error Message : The Autodiscover service could not be contacted. When attempting to connect to the server using the external domain name exchange.alluremedia.com.au , the following occurs. The connection dialog shows "Connecting". The connection fails with a message "Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. When attempting to connect to the server using the internal domain name freya.corp.alluremedia.com.au or the local IP address 192.168.10.1, the following occurs. A warning is shown that reads "The identity of the remote computer cannot be verified. Do you want to connect anyway? The remote computer could not be authenticated due to problems with its security certificate. It may be unsafe to proceed." When attempting to use Outlook Web Access at the external address https://exchange.alluremedia.com.au/owa, the page cannot be found. Some things that I have tried are not permanent solutions, but have allowed the connection to succeed to varying degrees: When configuring a mail account, if I uncheck "Only connect to proxy servers that have this principal name in their certificate: msstd:exchange.alluremedia.com.au", I am able to connect. If I change the Windows hosts file and add an entry for exchange.alluremedia.com.au to resolve to the server's local IP address, I am able to connect. If I use the server's local name, freya.corp.alluremedia.com.au, I am able to use Outlook Web Access, at https://freya.corp.alluremedia.com.au, however certificate errors are presented "The identity of this website has not been verified". The certificate that is returned by the web server is for the external domain name exchange.alluremedia.com.au. Until a week or two ago, I was able to access all services internally and externally using the external domain name exchange.alluremedia.com.au, however now that only works externally. Any assistance in resolving the issue would be much appreciated.
September 24th, 2010 10:22am

Hi, Thank you for your replies. There is no A record for exchange.alluremedia.com.au on our internal DNS server, however as far as I know there wasn't one before the issue appeared. There is an A record on the external DNS. Here are the results of get-clientaccessserver |fl [PS] C:\Windows\system32>get-clientaccessserver |fl Name : FREYA OutlookAnywhereEnabled : True AutoDiscoverServiceCN : Freya AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service AutoDiscoverServiceInternalUri : https://exchange.alluremedia.com.au/Autodiscover/Autodiscover.xml AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596 AutoDiscoverSiteScope : {Default-First-Site-Name} IsValid : True OriginatingServer : Freya.corp.alluremedia.com.au ExchangeVersion : 0.1 (8.0.535.0) DistinguishedName : CN=FREYA,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Allure Media,CN=Microsof t Exchange,CN=Services,CN=Configuration,DC=corp,DC=alluremedia,DC=com,DC=au Identity : FREYA Guid : 5fbe31c0-4007-410b-9b56-5ad242cd4346 ObjectCategory : corp.alluremedia.com.au/Configuration/Schema/ms-Exch-Exchange-Server ObjectClass : {top, server, msExchExchangeServer} WhenChanged : 30/07/2009 1:15:34 PM WhenCreated : 15/07/2008 5:10:24 PM [PS] C:\Windows\system32> Here are the results for the outlook autodiscover test on testexchangeconnectivity.com. Attempting to test Autodiscover for luke.eller@company.com.au Testing Autodiscover failed. Test Steps ExRCA is attempting each method of contacting the Autodiscover service. The Autodiscover service couldn't be contacted successfully by any method. Test Steps Attempting to test potential AutoDiscover URL https://alluremedia.com.au/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to test potential AutoDiscover URL https://autodiscover.alluremedia.com.au/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps ExRCA is attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to contact Autodiscover using the HTTP Redirect method failed. Test Steps ExRCA is attempting to contact the Autodiscover service using the DNS SRV redirect method. Failed to contact AutoDiscover using the DNS SRV redirect method. Test Steps
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2010 8:47pm

Hi, Thank you, I have performed ping which resolves to the office modem/router's WAN IP address 203.206.210.72. Here are the results of ping exchange.alluremedia.com.au and the related IP address, as well as an nslookup on the IP address. C:\Users\luke.eller.THOR>ping exchange.alluremedia.com.au Pinging exchange.alluremedia.com.au [203.206.210.72] with 32 bytes of data: Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Ping statistics for 203.206.210.72: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\luke.eller.THOR>ping 203.206.210.72 Pinging 203.206.210.72 with 32 bytes of data: Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Ping statistics for 203.206.210.72: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\luke.eller.THOR>nslookup 203.206.210.72 Server: UnKnown Address: 192.168.10.1 Name: exchange.alluremedia.com.au Address: 203.206.210.72 C:\Users\luke.eller.THOR> Here are the results of browsing to the addresses you specified. I have replaced company with our company name. https://exchange.alluremedia.com.au/Autodiscover/Autodiscover.xml https://alluremedia.com.au/AutoDiscover/AutoDiscover.xml https://autodiscover.alluremedia.com.au/AutoDiscover/AutoDiscover.xml from IE. Please note the result was the same in each instance. Internet Explorer cannot display the webpage What you can try: Diagnose Connection Problems More information This problem can be caused by a variety of issues, including: •Internet connectivity has been lost. •The website is temporarily unavailable. •The Domain Name Server (DNS) is not reachable. •The Domain Name Server (DNS) does not have a listing for the website's domain. •There might be a typing error in the address. •If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section. For offline users You can still view subscribed feeds and some recently viewed webpages. To view subscribed feeds 1.Click the Favorites Center button , click Feeds, and then click the feed you want to view. To view recently visited webpages (might not work on all pages) 1.Click Tools , and then click Work Offline. 2.Click the Favorites Center button , click History, and then click the page you want to view. I also tried Get-OutlookProviders. [PS] C:\Windows\system32>get-outlookprovider Name Server CertPrincipalName TTL ---- ------ ----------------- --- EXCH freya.corp.alluremedia.com.au 1 EXPR 1 WEB 1 Could the fact that CertPrincipalName is empty have anything to do with the problem? Kind regards, Luke
September 28th, 2010 12:34am

Hi, Thank you, I have performed ping which resolves to the office modem/router's WAN IP address 203.206.210.72. Here are the results of ping exchange.alluremedia.com.au and the related IP address, as well as an nslookup on the IP address. C:\Users\luke.eller.THOR>ping exchange.alluremedia.com.au Pinging exchange.alluremedia.com.au [203.206.210.72] with 32 bytes of data: Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Ping statistics for 203.206.210.72: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\luke.eller.THOR>ping 203.206.210.72 Pinging 203.206.210.72 with 32 bytes of data: Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Reply from 203.206.210.72: bytes=32 time<1ms TTL=64 Ping statistics for 203.206.210.72: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\luke.eller.THOR>nslookup 203.206.210.72 Server: UnKnown Address: 192.168.10.1 Name: exchange.alluremedia.com.au Address: 203.206.210.72 C:\Users\luke.eller.THOR> Here are the results of browsing to the addresses you specified. I have replaced company with our company name. https://exchange.alluremedia.com.au/Autodiscover/Autodiscover.xml https://alluremedia.com.au/AutoDiscover/AutoDiscover.xml https://autodiscover.alluremedia.com.au/AutoDiscover/AutoDiscover.xml from IE. Please note the result was the same in each instance. Internet Explorer cannot display the webpage What you can try: Diagnose Connection Problems More information This problem can be caused by a variety of issues, including: •Internet connectivity has been lost. •The website is temporarily unavailable. •The Domain Name Server (DNS) is not reachable. •The Domain Name Server (DNS) does not have a listing for the website's domain. •There might be a typing error in the address. •If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section. For offline users You can still view subscribed feeds and some recently viewed webpages. To view subscribed feeds 1.Click the Favorites Center button , click Feeds, and then click the feed you want to view. To view recently visited webpages (might not work on all pages) 1.Click Tools , and then click Work Offline. 2.Click the Favorites Center button , click History, and then click the page you want to view. Kind regards, Luke
Free Windows Admin Tool Kit Click here and download it now
September 28th, 2010 12:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics