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
pramod1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pramod1Author Commented:
When I type test-webservices connectivity

I get scenario get folder failure..
0
Will SzymkowskiSenior Solution ArchitectCommented:
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.
0
pramod1Author Commented:
this is a CAS server only
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

pramod1Author Commented:
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)
0
pramod1Author Commented:
and there is no mailbox called sussone79a
0
pramod1Author Commented:
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.
0
pramod1Author Commented:
I am getting  TCP Connectivity with Autodiscover - RPC Client Access failure (Connect)

what should I check to make sure this server is working ok
0
pramod1Author Commented:
should I do test-outlook connectivity
0
pramod1Author Commented:
I see all success
0
Will SzymkowskiSenior Solution ArchitectCommented:
In order for Autodiscover to work externally, you need to either have one of two things..
- autodiscover.domain.com (DNS name in the UCC cert)
- autodiscover SRV record in your External DNS

I am not sure what you are trying to test exactly?

You can also run the autodiscover test from your Outlook client as well. Using the Test Email Auto Configuration. Hold CTRL+right click the Outlook icon in the system tray, then select Test Email AutoDiscover.

Are you having issues with Exchange specifically?

Will.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pramod1Author Commented:
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)
0
Will SzymkowskiSenior Solution ArchitectCommented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.