I can not get through the final setup of exchange can't connect from phone or exchange on a non domain computer. this is my report from testexchangeconnectivity.com Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Test Steps ExRCA is attempting to test Autodiscover for administrator@gsmith.biz. Testing Autodiscover failed. Test Steps 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://gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=VMMAIL, Issuer: CN=VMMAIL. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name gsmith.biz doesn't match any name found on the server certificate CN=VMMAIL. Attempting to test potential Autodiscover URL https://autodiscover.gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=VMMAIL, Issuer: CN=VMMAIL. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name autodiscover.gsmith.biz doesn't match any name found on the server certificate CN=VMMAIL. Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to contact Autodiscover using the HTTP Redirect method failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 80 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. ExRCA is checking the host autodiscover.gsmith.biz for an HTTP redirect to the Autodiscover service. ExRCA failed to get an HTTP redirect response for Autodiscover. Additional Details An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: Attempting to contact the Autodiscover service using the DNS SRV redirect method. ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method. Test Steps Attempting to locate SRV record _autodiscover._tcp.gsmith.biz in DNS. The Autodiscover SRV record wasn't found in DNS. Tell me more about this issue and how to resolve it I tried to setup autoconfigure in DNS but not sure how exactly to do it. any help would be great. 

Is that your SMTP Address? @gsmith.biz ? If so, simply create a record in external DNS for autodiscover.gsmith.biz that points to the external IP address for the external client access to your servers.

I tried that but something must be wrong as it still does not work. This is whats in my GoDaddy DNS: And I have this in my internal DNS. This is where I think I have gone wrong. I also manage to get incoming mail working so will try to get a instantssl certificate today (if they are still free) or could I just use a self signed one?

Right, so you need 2 things here: A valid DNS entry and a trusted cert with the FQDN of that entry as one of the subject names on it. self-signed certs should not be used. Go with the 3rd party trusted.

Right so there is an issue with my local autoconfugure. Is it the domain that is the issue when I fill out the fields i thought that the domain had to be _autoconfigure._tcp.gsmith.biz but I can not change it from the below. For the SSL must I have one? This is only a test\lab server so that I can try out exchange and server 2013, I don't really want to pay for one if I can help it (I don't care about the prompt if that is the difference.) Thanks for you quick help.

You can use a self-signed cert however, you will need to either add it to the mobile device or tell to ignore the fact its not trusted. Note its autodiscover.gsmith.biz not _autoconfigure._tcp.gsmith.biz and its really used for external autodiscover, not internal. Domain-joined clients use the SCP record in AD to find autodiscovery URLs.

OH crap! that is a dumb mistake, let me change it and try again.

I have changed it but still have same issue. When I try to connect from my phone does it first use public DNS autodiscover to look at my internal dns autodiscover then pass the info back to my phone?

External non-domain joined clients will only refer to external DNS Try running the test-exchangeconnectivity tests again

OK well that's the important one for me then. I can ping autodiscover.gsmith.biz so looks like DNS is OK. I'm not %100 sure that I filled in godaddys autodiscover correctly but it looks right to me. I ran the testexchangeconnectivity.com test again and this is the response (sorry it loses color when I put it in as HTML but at least its not all one parragraph) ExRCA is attempting to test Autodiscover for administrator@gsmith.biz. Testing Autodiscover failed. Test Steps 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://gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=VMMAIL, Issuer: CN=VMMAIL. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name gsmith.biz doesn't match any name found on the server certificate CN=VMMAIL. Attempting to test potential Autodiscover URL https://autodiscover.gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=VMMAIL, Issuer: CN=VMMAIL. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name autodiscover.gsmith.biz doesn't match any name found on the server certificate CN=VMMAIL. Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to contact Autodiscover using the HTTP Redirect method failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 80 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. ExRCA is checking the host autodiscover.gsmith.biz for an HTTP redirect to the Autodiscover service. ExRCA failed to get an HTTP redirect response for Autodiscover. Additional Details An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: Attempting to contact the Autodiscover service using the DNS SRV redirect method. ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method. Test Steps Attempting to locate SRV record _autodiscover._tcp.gsmith.biz in DNS. The Autodiscover SRV record wasn't found in DNS. Tell me more about this issue and how to resolve it

Host name autodiscover.gsmith.biz doesn't match any name found on the server You need that on the cert. Note that since this is a self-signed cert, you will fail any trust test and the phones wont work unless you use a trusted cert or bypass that on the phone. Or use HTTP ( not recommened)

So for exchange I just need a SSL cert with the name autodiscover.gsmith.biz I don't need any other one like mail.gsmith.biz or pop.gsmith.biz?

OK so I added a startssl cert for autodiscover.gsmith.biz and this is the output. ExRCA is attempting to test Autodiscover for administrator@gsmith.biz. Testing Autodiscover failed. Test Steps 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://gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=VMMAIL, Issuer: CN=VMMAIL. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name gsmith.biz doesn't match any name found on the server certificate CN=VMMAIL. Attempting to test potential Autodiscover URL https://autodiscover.gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=VMMAIL, Issuer: CN=VMMAIL. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name autodiscover.gsmith.biz doesn't match any name found on the server certificate CN=VMMAIL. Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to contact Autodiscover using the HTTP Redirect method failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 80 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. ExRCA is checking the host autodiscover.gsmith.biz for an HTTP redirect to the Autodiscover service. ExRCA failed to get an HTTP redirect response for Autodiscover. Additional Details An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: Attempting to contact the Autodiscover service using the DNS SRV redirect method. ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method. Test Steps Attempting to locate SRV record _autodiscover._tcp.gsmith.biz in DNS. The Autodiscover SRV record wasn't found in DNS. Tell me more about this issue and how to resolve it

On Wed, 31 Oct 2012 03:09:17 +0000, theawkward wrote: >OK so I added a startssl cert for autodiscover.gsmith.biz and this is the output. Try this to get the information about the certificate (it all goes on one line): Get-ExchangeCertificate <thumbprint> | fl Issuer,CertificateDomains,Subject If you have multiple certificates make sure you enabled the correct one! Your problem is stated pretty clearly: Host name autodiscover.gsmith.biz doesn't match any name found on the server certificate CN=VMMAIL. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I tried that command in Exchange Management shell (also tried PS) but I get this error. But I think that you may have solved it anyway. I didn't know that I had to have one as the default so went back to admin center and saw that I can change the services. I was going to tick the boxes for SMNP, IMAP, POP, IIS but I get this error and I am unsure if I want to do it. I had a look on the internet but couldn't find anything that was helpful. Is this where I went wrong? Shoudl I say yes?

when i clicked cancel it showed as having added those services so tested again and it all looks good. Thanks everyone! Now to see if it really works :)

On Wed, 31 Oct 2012 04:21:40 +0000, theawkward wrote: >I tried that command in Exchange Management shell (also tried PS) but I get this error. Well, sure . . . "<thumbprint>" is what you'd replace with the thumprint of your certificate. >But I think that you may have solved it anyway. I didn't know that I had to have one as the default so went back to admin center and saw that I can change the services. > >I was going to tick the boxes for SMNP, IMAP, POP, IIS but I get this error and I am unsure if I want to do it. I had a look on the internet but couldn't find anything that was helpful. > >Is this where I went wrong? Shoudl I say yes? If the certificate with the thumbprint "805A3...." is the one you want to use, sure. It isn't going to remove the other certificate from the certificate store so you always enable the one that you replace (at least until it's removed from the certificate store). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

:D Oh, that makes more sense. I've never used exchange or power shell before so was not sure what I was doing. I really just wanted to use a self signed certificate as its just a test server so that I can get used to exchange and server 2012 (technet). I ended up setting my self signed cert for SMNP, IMAP, POP, IIS (I left UM as I didn't know what it was) but I am still getting errors. When I run the PS command I get this [PS] C:\Windows\system32>Get-ExchangeCertificate EAD28B78253E49C9A480C7BBDADE8378DA50F17F | fl Issuer,CertificateDomains ,Subject Issuer : CN=vmmail.gsmith.biz CertificateDomains : {vmmail.gsmith.biz, AutoDiscover.gsmith.biz, mail.gsmith.biz, gsmith.biz} Subject : CN=vmmail.gsmith.biz That looks OK to me but I have other certificates that are assigned to the same services (exchange made these I think) Microsoft Exchange: IIS, SMTP Microsoft Exchange Server Auth Certificate: SMTP WMSVC: None So I tried to turn off these services but they are greyed out and I don't think I should just delete the certificates. If I try to setup mail in outlook 2013 (host, on non domain computer) then it looks like autodiscover is working as I get a prompt for Security certificate. and If i say yes then I all green ticks saying that it connected to the server But when I restart outlook I get this I have been trying to Google it but nothing seems related as its such a general error. Oh and I should say I am doing all this in the Exchange admin center not in IIS (i think this is where it used to go)

On Wed, 31 Oct 2012 23:12:12 +0000, theawkward wrote: [ snip ] >But when I restart outlook I get this Try running the Exchange Best Practices Analyzer. That GUID for the server name and the "=SMTP:" in the account name have, in the past, been caused by DNS and/or Outlook client issues. If the server's accessible from the Internet you can visit https://testexchangeconnectivity.com and verify that things are working correctly. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I have been doing this and so far I have this. Outbound: OK, but get this warning that I am ignoring Performing Sender ID validation. Sender ID validation was performed successfully. Test Steps Attempting to find the SPF record using a DNS TEXT record query. ExRCA wasn't able to find the SPF record. Additional Details No records were found. Inbound: Completely OK Outlook Autodiscover: Completely OK Outlook Anywhere (RPC over HTTP): This one not so good. I am trying to work out how to do the Autodiscover.xml right now cause that looks like most of the damage. Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Test Steps ExRCA is attempting to test Autodiscover for Administrator@gsmith.biz. Testing Autodiscover failed. Test Steps 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://gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=vmmail.gsmith.biz, Issuer: CN=vmmail.gsmith.biz. Validating the certificate name. The certificate name was validated successfully. Additional Details Host name gsmith.biz was found in the Certificate Subject Alternative Name entry. Certificate trust is being validated. Certificate trust validation failed. Test Steps ExRCA is attempting to build certificate chains for certificate CN=vmmail.gsmith.biz. A certificate chain couldn't be constructed for the certificate. Tell me more about this issue and how to resolve it Additional Details The certificate chain didn't end in a trusted root. Root = CN=vmmail.gsmith.biz Attempting to test potential Autodiscover URL https://autodiscover.gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=vmmail.gsmith.biz, Issuer: CN=vmmail.gsmith.biz. Validating the certificate name. The certificate name was validated successfully. Additional Details Host name autodiscover.gsmith.biz was found in the Certificate Subject Alternative Name entry. Certificate trust is being validated. Certificate trust validation failed. Test Steps ExRCA is attempting to build certificate chains for certificate CN=vmmail.gsmith.biz. A certificate chain couldn't be constructed for the certificate. Tell me more about this issue and how to resolve it Additional Details The certificate chain didn't end in a trusted root. Root = CN=vmmail.gsmith.biz Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to contact Autodiscover using the HTTP Redirect method failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 80 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. ExRCA is checking the host autodiscover.gsmith.biz for an HTTP redirect to the Autodiscover service. ExRCA failed to get an HTTP redirect response for Autodiscover. Additional Details An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: Attempting to contact the Autodiscover service using the DNS SRV redirect method. ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method. Test Steps Attempting to locate SRV record _autodiscover._tcp.gsmith.biz in DNS. The Autodiscover SRV record wasn't found in DNS. Tell me more about this issue and how to resolve it

On Thu, 1 Nov 2012 00:23:42 +0000, theawkward wrote: >I have been doing this and so far I have this. [ snip ] >Outlook Anywhere (RPC over HTTP): This one not so good. I am trying to work out how to do the Autodiscover.xml right now cause that looks like most of the damage. > >Testing RPC/HTTP connectivity. The RPC/HTTP test failed. [ snip ] Additional Details Remote Certificate Subject: CN=vmmail.gsmith.biz, Issuer: CN=vmmail.gsmith.biz. Validating the certificate name. [ snip ] Certificate trust validation failed. Test Steps ExRCA is attempting to build certificate chains for certificate CN=vmmail.gsmith.biz. A certificate chain couldn't be constructed for the certificate. Additional Details The certificate chain didn't end in a trusted root. Root = CN=vmmail.gsmith.biz The certificate isn't trusted by any public CA so you're not going to get this to work (well, maybe if you put the necessary information on an internet-facing machine you could). What infrmation did the ExBPA turn up? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Oh forgot it has been retired, still looking to see if it was replaced with something else. In Exchange 2010, the Exchange Best Practice Analyzer examined your Exchange deployment and determined whether the configuration was in line with Microsoft best practices. In Exchange 2013, the Exchange Best Practice Analyzer has been retired.

Do I have to create AutoDiscover.xml because I can't really find any information on how to set it up or create it.

On Thu, 1 Nov 2012 04:24:29 +0000, theawkward wrote: >Do I have to create AutoDiscover.xml because I can't really find any information on how to set it up or create it. The file isn't one that you create. But now that you have a certificate on your server, do you still have a problem with autodiscover? Does your client trust the issuer of the certificate? Does autodiscover work within your own LAN? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 1 Nov 2012 04:24:29 +0000, theawkward wrote: >Do I have to create AutoDiscover.xml because I can't really find any information on how to set it up or create it. The file isn't one that you create. But now that you have a certificate on your server, do you still have a problem with autodiscover? Does your client trust the issuer of the certificate? Does autodiscover work within your own LAN? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 1 Nov 2012 04:24:29 +0000, theawkward wrote: >Do I have to create AutoDiscover.xml because I can't really find any information on how to set it up or create it. The file isn't one that you create. But now that you have a certificate on your server, do you still have a problem with autodiscover? Does your client trust the issuer of the certificate? Does autodiscover work within your own LAN? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I still have the same issue in outlook as above where autodiscover works but when I restart it gives me those errors that show in the screen shots above. I am running exchange on a win8 hyper-v host and the host is not part of the domain and this is where I am trying to connect outlook. I will set up another hyper-v vm with windows7 today and join it to the domain and see if it works from there. but I am still getting the failure when autodiscover looks for autodiscover.xml as per my last post that shows testexch output. I t can resolve gsmith.biz fine but not https://autodiscover.gsmith.biz/AutoDiscover/AutoDiscover.xml

I still have the same issue in outlook as above where autodiscover works but when I restart it gives me those errors that show in the screen shots above. I am running exchange on a win8 hyper-v host and the host is not part of the domain and this is where I am trying to connect outlook. I will set up another hyper-v vm with windows7 today and join it to the domain and see if it works from there. but I am still getting the failure when autodiscover looks for autodiscover.xml as per my last post that shows testexch output. I t can resolve gsmith.biz fine but not https://autodiscover.gsmith.biz/AutoDiscover/AutoDiscover.xml

I still have the same issue in outlook as above where autodiscover works but when I restart it gives me those errors that show in the screen shots above. I am running exchange on a win8 hyper-v host and the host is not part of the domain and this is where I am trying to connect outlook. I will set up another hyper-v vm with windows7 today and join it to the domain and see if it works from there. but I am still getting the failure when autodiscover looks for autodiscover.xml as per my last post that shows testexch output. I t can resolve gsmith.biz fine but not https://autodiscover.gsmith.biz/AutoDiscover/AutoDiscover.xml

I just recreated the self signed cert to see if maybe it was the issue but I get the same thing. But it made me wonder, shouldn't the "Microsoft Exchange Server:" be "mail.gsmith.biz" instead of "4ddc3a6d-b129-4e8a-a15c-9aa189e81562@gsmith.biz"? What is this long number it does not correspond to a certificate that I can see.

I just recreated the self signed cert to see if maybe it was the issue but I get the same thing. But it made me wonder, shouldn't the "Microsoft Exchange Server:" be "mail.gsmith.biz" instead of "4ddc3a6d-b129-4e8a-a15c-9aa189e81562@gsmith.biz"? What is this long number it does not correspond to a certificate that I can see.

I just recreated the self signed cert to see if maybe it was the issue but I get the same thing. But it made me wonder, shouldn't the "Microsoft Exchange Server:" be "mail.gsmith.biz" instead of "4ddc3a6d-b129-4e8a-a15c-9aa189e81562@gsmith.biz"? What is this long number it does not correspond to a certificate that I can see.

On Thu, 1 Nov 2012 22:03:43 +0000, theawkward wrote: > > >I just recreated the self signed cert to see if maybe it was the issue but I get the same thing. > >But it made me wonder, shouldn't the "Microsoft Exchange Server:" be "mail.gsmith.biz" instead of "4ddc3a6d-b129-4e8a-a15c-9aa189e81562@gsmith.biz"? What is this long number it does not correspond to a certificate that I can see. I can't find a lot on the problem. These other threads have similar problems but none of them point to any one particular thing that might be wrong except, in a general way, access to the CAS: http://www.networksteve.com/exchange/topic.php/Exchange_2010_Autodiscover_incorrectly_configuring_Outlook_clien/?TopicId=23728&Posts=1 http://social.technet.microsoft.com/Forums/en-US/exchangesvr3rdpartyappslegacy/thread/45b4867a-17a4-46ea-8c49-1fa01f78f97e http://forums.asp.net/t/1199863.aspx/1 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 1 Nov 2012 22:03:43 +0000, theawkward wrote: > > >I just recreated the self signed cert to see if maybe it was the issue but I get the same thing. > >But it made me wonder, shouldn't the "Microsoft Exchange Server:" be "mail.gsmith.biz" instead of "4ddc3a6d-b129-4e8a-a15c-9aa189e81562@gsmith.biz"? What is this long number it does not correspond to a certificate that I can see. I can't find a lot on the problem. These other threads have similar problems but none of them point to any one particular thing that might be wrong except, in a general way, access to the CAS: http://www.networksteve.com/exchange/topic.php/Exchange_2010_Autodiscover_incorrectly_configuring_Outlook_clien/?TopicId=23728&Posts=1 http://social.technet.microsoft.com/Forums/en-US/exchangesvr3rdpartyappslegacy/thread/45b4867a-17a4-46ea-8c49-1fa01f78f97e http://forums.asp.net/t/1199863.aspx/1 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 1 Nov 2012 22:03:43 +0000, theawkward wrote: > > >I just recreated the self signed cert to see if maybe it was the issue but I get the same thing. > >But it made me wonder, shouldn't the "Microsoft Exchange Server:" be "mail.gsmith.biz" instead of "4ddc3a6d-b129-4e8a-a15c-9aa189e81562@gsmith.biz"? What is this long number it does not correspond to a certificate that I can see. I can't find a lot on the problem. These other threads have similar problems but none of them point to any one particular thing that might be wrong except, in a general way, access to the CAS: http://www.networksteve.com/exchange/topic.php/Exchange_2010_Autodiscover_incorrectly_configuring_Outlook_clien/?TopicId=23728&Posts=1 http://social.technet.microsoft.com/Forums/en-US/exchangesvr3rdpartyappslegacy/thread/45b4867a-17a4-46ea-8c49-1fa01f78f97e http://forums.asp.net/t/1199863.aspx/1 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

That thread is unrelated or I am missing something. I have had a play and found that BPA is not removed in Server 2012 (even if Microsoft says it has been) it is built in. So I have enabled it and cleared as many of them as I could but I still get 2 that wont clear. 1. VMMAIL Error DNS: DNS servers on Ethernet should include the loopback address, but not as the first entry. In the configuration I have changed it so that I have the IP of the server in the first entry 10.10.0.10 and 127.0.0.1 in the second but still get prompted every time. I assume that's because they are both pointing to itself. 2. VMMAIL Error The PDC emulator master VMMAIL.gsmith.biz in this forest should be configured to correctly synchronize time from a valid time source Configuration. I have done this a hundred times but it just does not seem to work or this message is coming up when it shouldn't. the command that I ran was: w32tm /config /computer:VMMAIL.gsmith.biz /manualpeerlist:time.windows.com /syncfromflags:manual /update And it tells me that it was successful. I guess it could also be that I have the DC on a hyper-v machine but I thought that was OK to do with Server 2012

That thread is unrelated or I am missing something. I have had a play and found that BPA is not removed in Server 2012 (even if Microsoft says it has been) it is built in. So I have enabled it and cleared as many of them as I could but I still get 2 that wont clear. 1. VMMAIL Error DNS: DNS servers on Ethernet should include the loopback address, but not as the first entry. In the configuration I have changed it so that I have the IP of the server in the first entry 10.10.0.10 and 127.0.0.1 in the second but still get prompted every time. I assume that's because they are both pointing to itself. 2. VMMAIL Error The PDC emulator master VMMAIL.gsmith.biz in this forest should be configured to correctly synchronize time from a valid time source Configuration. I have done this a hundred times but it just does not seem to work or this message is coming up when it shouldn't. the command that I ran was: w32tm /config /computer:VMMAIL.gsmith.biz /manualpeerlist:time.windows.com /syncfromflags:manual /update And it tells me that it was successful. I guess it could also be that I have the DC on a hyper-v machine but I thought that was OK to do with Server 2012

I am still getting the same issue in outlook when trying to setup. This error is stupid as it has already contacted the server to find administrators details. I think that this information above is the expected result with Exchange 2013 as per this site Another change in the Exchange 2013 server architecture is the absence of the RPC Endpoint. In Exchange 2010 there was the CAS Array that was the RPC Endpoint. An Outlook client had to go to this FQDN to get to the mailbox. This has changed from a FQDN to a GUID, followed by the domain name. When an Outlook client needs to access a mailbox it will query Active Directory and the GUID is returned, regardless of the Mailbox Server or the Mailbox Database. This will make life much easier when moving mailboxes, or when doing a *over in your Exchange environment. You can see this in the Outlook profile:

I am still getting the same issue in outlook when trying to setup. This error is stupid as it has already contacted the server to find administrators details. I think that this information above is the expected result with Exchange 2013 as per this site Another change in the Exchange 2013 server architecture is the absence of the RPC Endpoint. In Exchange 2010 there was the CAS Array that was the RPC Endpoint. An Outlook client had to go to this FQDN to get to the mailbox. This has changed from a FQDN to a GUID, followed by the domain name. When an Outlook client needs to access a mailbox it will query Active Directory and the GUID is returned, regardless of the Mailbox Server or the Mailbox Database. This will make life much easier when moving mailboxes, or when doing a *over in your Exchange environment. You can see this in the Outlook profile:

On Wed, 7 Nov 2012 04:20:58 +0000, theawkward wrote: > > >I am still getting the same issue in outlook when trying to setup. > > > >This error is stupid as it has already contacted the server to find administrators details. > > > >I think that this information above is the expected result with Exchange 2013 as per this site Notice that the example does NOT have "=SMTP:" in the user name after the name has been checked.> --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Wed, 7 Nov 2012 04:20:58 +0000, theawkward wrote: > > >I am still getting the same issue in outlook when trying to setup. > > > >This error is stupid as it has already contacted the server to find administrators details. > > > >I think that this information above is the expected result with Exchange 2013 as per this site Notice that the example does NOT have "=SMTP:" in the user name after the name has been checked.> --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I wondered that but it is also a different screen. I can't find anything that relates to "=SMTP:" problem is that Google filters out most the characters and just searches based on SMTP and there are a billion results for that. Am I just being stupid and missing something simple?

I wondered that but it is also a different screen. I can't find anything that relates to "=SMTP:" problem is that Google filters out most the characters and just searches based on SMTP and there are a billion results for that. Am I just being stupid and missing something simple?

So I built a SBS2011 VM a week ago to see what would happen and I get the same thing.. Any one got any ideas? I should say that I can connect my 3G devices no problem, it's just outlook that does not work.

I think the issue is here.. Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Test Steps ExRCA is attempting to test Autodiscover for GSmith@Gsmith.biz. Testing Autodiscover failed. Test Steps 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://Gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=remote.GSmith.biz, Issuer: CN=gsmith-SBS2011-CA. Validating the certificate name. The certificate name was validated successfully. Additional Details Host name gsmith.biz was found in the Certificate Subject Alternative Name entry. Certificate trust is being validated. Certificate trust validation failed. Test Steps ExRCA is attempting to build certificate chains for certificate CN=remote.GSmith.biz. A certificate chain couldn't be constructed for the certificate. Additional Details The certificate chain couldn't be built. You may be missing required intermediate certificates. Attempting to test potential Autodiscover URL https://autodiscover.Gsmith.biz/AutoDiscover/AutoDiscover.xml Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=remote.GSmith.biz, Issuer: CN=gsmith-SBS2011-CA. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name autodiscover.gsmith.biz doesn't match any name found on the server certificate CN=remote.GSmith.biz. Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to contact Autodiscover using the HTTP Redirect method failed. Test Steps Attempting to resolve the host name autodiscover.Gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 80 on host autodiscover.Gsmith.biz to ensure it's listening and open. The port was opened successfully. ExRCA is checking the host autodiscover.Gsmith.biz for an HTTP redirect to the Autodiscover service. The redirect (HTTP 301/302) response was received successfully. Additional Details Redirect URL: HTTPS://AUTODISCOVER.GSMITH.BIZ/AUTODISCOVER/AUTODISCOVER.XML Attempting to test potential Autodiscover URL HTTPS://AUTODISCOVER.GSMITH.BIZ/AUTODISCOVER/AUTODISCOVER.XML Testing of this potential Autodiscover URL failed. Test Steps Attempting to resolve the host name autodiscover.gsmith.biz in DNS. The host name resolved successfully. Additional Details IP addresses returned: 123.243.73.235 Testing TCP port 443 on host autodiscover.gsmith.biz to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Test Steps ExRCA is attempting to obtain the SSL certificate from remote server autodiscover.gsmith.biz on port 443. ExRCA successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=remote.GSmith.biz, Issuer: CN=gsmith-SBS2011-CA. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name autodiscover.gsmith.biz doesn't match any name found on the server certificate CN=remote.GSmith.biz. Attempting to contact the Autodiscover service using the DNS SRV redirect method. ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method. Test Steps Attempting to locate SRV record _autodiscover._tcp.Gsmith.biz in DNS. The Autodiscover SRV record wasn't found in DNS. Tell me more about this issue and how to resolve it