Link to home
Start Free TrialLog in
Avatar of pramod1
pramod1Flag for United States of America

asked on

EXCHNAGE 2010

How to test connectivity to system mailbox in exchange 2010
as I am getting TCP connectivity with auto discover , want to check TCP is working or not
Avatar of pramod1
pramod1
Flag of United States of America image

ASKER

When I type test-webservices connectivity

I get scenario get folder failure..
Avatar of Will Szymkowski
Why do you need to test connectivity to the System Mailbox Specifically?

Can you just not use Remote Connectivity Analyzer?
https://testconnectivity.microsoft.com/

Will.
Avatar of pramod1

ASKER

this is a CAS server only
Avatar of pramod1

ASKER

I am getting below error
The test step MailboxConnect running over protocol 'ncacn_ip_tcp' issued from test user '/o=Clear Channel/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=DJ SUSSONE79a' failed with error: '1010(The configuration registry key is invalid)
Avatar of pramod1

ASKER

and there is no mailbox called sussone79a
Avatar of pramod1

ASKER

The Microsoft Connectivity Analyzer is attempting to test Autodiscover for pramodkumar@iheartmedia.com.
  Testing Autodiscover failed.
   Additional Details
  Elapsed Time: 6172 ms.  
 
   Test Steps
   Attempting each method of contacting the Autodiscover service.
  The Autodiscover service couldn't be contacted successfully by any method.
   Additional Details
  Elapsed Time: 6172 ms.  
 
   Test Steps
   Attempting to test potential Autodiscover URL https://iheartmedia.com:443/Autodiscover/Autodiscover.xml 
  Testing of this potential Autodiscover URL failed.
   Additional Details
  Elapsed Time: 1315 ms.  
 
   Test Steps
   Attempting to resolve the host name iheartmedia.com in DNS.
  The host name resolved successfully.
   Additional Details
  IP addresses returned: 207.230.142.10 Elapsed Time: 85 ms.  
 
 Testing TCP port 443 on host iheartmedia.com to ensure it's listening and open.
  The specified port is either blocked, not listening, or not producing the expected response.
   Tell me more about this issue and how to resolve it
   Additional Details
  A network error occurred while communicating with the remote host.
Elapsed Time: 1229 ms.  
 
 
 
 Attempting to test potential Autodiscover URL https://autodiscover.iheartmedia.com:443/Autodiscover/Autodiscover.xml 
  Testing of this potential Autodiscover URL failed.
   Additional Details
  Elapsed Time: 4591 ms.  
 
   Test Steps
   Attempting to resolve the host name autodiscover.iheartmedia.com in DNS.
  The host name resolved successfully.
   Additional Details
  IP addresses returned: 207.230.136.220 Elapsed Time: 152 ms.  
 
 Testing TCP port 443 on host autodiscover.iheartmedia.com to ensure it's listening and open.
  The port was opened successfully.
   Additional Details
  Elapsed Time: 154 ms.  
 
 Testing the SSL certificate to make sure it's valid.
  The certificate passed all validation requirements.
   Additional Details
  Elapsed Time: 1807 ms.  
 
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.iheartmedia.com on port 443.
  The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
   Additional Details
  Remote Certificate Subject: CN=*.iheartmedia.com, OU=Domain Control Validated, Issuer: CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US. Elapsed Time: 265 ms.  
 
 Validating the certificate name.
  The certificate name was validated successfully.
   Additional Details
  The host name that was found, autodiscover.iheartmedia.com, is a wildcard certificate match for common name *.iheartmedia.com. Elapsed Time: 0 ms.  
 
 Certificate trust is being validated.
  The certificate is trusted and all certificates are present in the chain.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=*.iheartmedia.com, OU=Domain Control Validated.
  One or more certificate chains were constructed successfully.
   Additional Details
  A total of 2 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US. Elapsed Time: 16 ms.  
 
 Analyzing the certificate chains for compatibility problems with versions of Windows.
  Potential compatibility problems were identified with some versions of Windows.
   Additional Details
  The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled. Elapsed Time: 3 ms.  
 
 
 
 Testing the certificate date to confirm the certificate is valid.
  Date validation passed. The certificate hasn't expired.
   Additional Details
  The certificate is valid. NotBefore = 9/12/2014 11:16:13 PM, NotAfter = 9/12/2015 11:16:13 PM Elapsed Time: 0 ms.  
 
 
 
 Checking the IIS configuration for client certificate authentication.
  Client certificate authentication wasn't detected.
   Additional Details
  Accept/Require Client Certificates isn't configured. Elapsed Time: 700 ms.  
 
 Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
  Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
   Additional Details
  Elapsed Time: 1776 ms.  
 
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.iheartmedia.com:443/Autodiscover/Autodiscover.xml for user pramodkumar@iheartmedia.com.
  The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
   Additional Details
  An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
HTTP Response Headers:
Content-Type: text/html
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="autodiscover.iheartmedia.com"
X-Powered-By: ASP.NET
Date: Tue, 14 Jul 2015 17:09:50 GMT
Content-Length: 58
Set-Cookie: NTLMconnpool=WxNeiSQBNc6urL6B+zF8gbOHLPdeMFUkIRMIwzZoGSoDPVcFz89sbVV7PmcajSylCTF37yj+tzcqIxNGxHHoa7BnUesExNRm01pb20tf383nadKQuTecYA4b3Cvg5O84bX9NoQ7GPJs=;secure;path=/;
Elapsed Time: 1775 ms.  
 
 
 
 
 
 Checking if there is an autodiscover CNAME record in DNS for your domain 'iheartmedia.com' for Office 365.
  Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
   Tell me more about this issue and how to resolve it
   Additional Details
  There is no Autodiscover CNAME record for your domain 'iheartmedia.com'. Elapsed Time: 264 ms.
Avatar of pramod1

ASKER

I am getting  TCP Connectivity with Autodiscover - RPC Client Access failure (Connect)

what should I check to make sure this server is working ok
Avatar of pramod1

ASKER

should I do test-outlook connectivity
Avatar of pramod1

ASKER

I see all success
ASKER CERTIFIED SOLUTION
Avatar of Will Szymkowski
Will Szymkowski
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of pramod1

ASKER

it is just  CAS SERVER  I don't think outlook is installed

one user pointed out that he is getting  TCP Connectivity with Autodiscover - RPC Client Access failure (Connect)
Where is this comming up. Is the user trying to connect via Outlook using Outlook anywhere? What authentication type is the user using in Outlook?

Will.