Autodiscovery returning wrong server address

Hello every one!

I have recently installed a exchange server 2013 on windows server 2012 for testing purposes.
Everything works fine, i can send and receive mail, use OWA. But the problem is occur when i trying to configure outlook INSIDE organisation, on a pc, which is domain member.
Autodiscover returning wrong server address (something like guid) and wrong e-mail address (simething like :smtp=mail@domain.ru), and setup failing with error "there is no connection toexchange server...".

But, if i will make outlook configuration manualy, it works fine.

When i am trying to acces https://mail.domain.local/Autodiscover/Autodiscover.xml
i recive this mesage: <ErrorCode>600</ErrorCode>

If it is important i am using self-signed certificate. Can it be a reason?

Remote connectivity analyzer test results are fine, every test passed.
But in result, we can see the same:




<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>85b36064-bc81-4c07-bd63-ebc5bc5120a6@externaldomain.com</Server>
<ServerDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=85b36064-bc81-4c07-bd63-ebc5bc5120a6@externaldomain.com</ServerDN>
<ServerVersion>73C08204</ServerVersion>
<MdbDN>/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=85b36064-bc81-4c07-bd63-ebc5bc5120a6@externaldomain.com/cn=Microsoft Private MDB</MdbDN>
<ASUrl>https://mail-ffm.domain.local/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://mail-ffm.domain.local/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://mail-ffm.domain.local/OAB/f5427667-137c-42f3-ae18-35cc859ccef0/</OABUrl>
<UMUrl>https://mail-ffm.domain.local/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<PublicFolderServer>MAIL-FFM.domain.local</PublicFolderServer>
<AD>addc-ffm.domain.local</AD>
<EwsUrl>https://mail-ffm.domain.local/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://mail-ffm.domain.local/EWS/Exchange.asmx</EmwsUrl>
<EcpUrl>https://mail-ffm.domain.local/ecp/</EcpUrl>




What is wrong? 

December 17th, 2012 3:17pm

Hi,

Im having the same problem external, manual configuration works fine but autodiscover fails with cannot log on to the server.

I get the same long server address e.g "76485hf903494794hgt94uhr@domain.local" and the email address is e.g "smtp=admin@domain.local"

I have a bought cert so I think you can rule that out??

James.

Free Windows Admin Tool Kit Click here and download it now
December 17th, 2012 3:31pm

what firewall are you using? we had a sonicwall and had to configure this to route back in.
December 17th, 2012 3:32pm

There is no firewall on exchange server, there is no firewall on client, there is no fire wall between them.

And i am trying to connect from INTERNAL (domain) network.

Free Windows Admin Tool Kit Click here and download it now
December 17th, 2012 4:32pm

Yes BUT you are using auto discovery are you not?

so unless you have configured your internal DNS for your external DNS then outlook IS going OUT to come back IN??

e.g mail.mydomain.co.uk will be going out.

have you added the external address in /ecp, servers, edit the server, click outlook anywhere?

James.

December 17th, 2012 4:41pm

right, in /ecp, servers, edit the server, click outlook anywhere? at the bottom set BASIC. this fixed my problem JUST now.

James.

Free Windows Admin Tool Kit Click here and download it now
December 17th, 2012 4:51pm

James, sorry, I'm probably very slow in the moment, fatigue effect. =(

Did you mean settings, those shown on my screenshot?(FQDN cnanged)

Or we speak about settings of internal dns server?

However, there is no zones for externaldomain.com at internal dns server.

thanks!!

December 17th, 2012 5:02pm

Add the external address.

Free Windows Admin Tool Kit Click here and download it now
December 17th, 2012 5:05pm

It is already added.

it's look like mail.externaldomain.com

December 17th, 2012 5:09pm

if you ping the external address from the lan what IP you get?
Free Windows Admin Tool Kit Click here and download it now
December 17th, 2012 5:11pm

i get external ip.
December 17th, 2012 5:33pm

Hello,

Please run get-autodiscovervirtualdirectory | fl to check autodiscover settings.

Free Windows Admin Tool Kit Click here and download it now
December 18th, 2012 7:37am

[PS] C:\Windows\system32>get-autodiscovervirtualdirectory | fl


RunspaceId                      : a104207f-3723-4435-8e3d-93127c5a239e
Name                            : Autodiscover (Default Web Site)
InternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication   : False
WSSecurityAuthentication        : True
LiveIdBasicAuthentication       : False
BasicAuthentication             : True
DigestAuthentication            : False
WindowsAuthentication           : True
OAuthAuthentication             : True
AdfsAuthentication              : False
MetabasePath                    : IIS://MAIL-FFM.domain.local/W3SVC/1/ROOT/Autodiscover
Path                            : C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
AdminDisplayVersion             : Version 15.0 (Build 516.32)
Server                          : MAIL-FFM
InternalUrl                     :
ExternalUrl                     :
AdminDisplayName                :
ExchangeVersion                 : 0.10 (14.0.100.0)
DistinguishedName               : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=MAIL-FFM,CN=Servers,CN=Exc
                                  hange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organi
                                  zation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ffmedia,DC=lan
Identity                        : MAIL-FFM\Autodiscover (Default Web Site)
Guid                            : 6f37ac1e-7b14-442c-9845-eefede7bf59a
ObjectCategory                  : ffmedia.lan/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass                     : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged                     : 17.12.2012 18:40:16
WhenCreated                     : 17.12.2012 18:40:16
WhenChangedUTC                  : 17.12.2012 14:40:16
WhenCreatedUTC                  : 17.12.2012 14:40:16
OrganizationId                  :
OriginatingServer               : addc-ffm.domain.local
IsValid                         : True
ObjectState                     : Changed

December 18th, 2012 9:08am

Rudy,

What did you do to get this working?  I am getting the exact opposite results as you.  My autodiscovery works fine, but when I go to add a second Outlook Email account, the Exchange 2013 server name doesn't resolve.  After checking the settings of the default mail account that autodiscovered found I notice the server name is (GUID@domain.com).  I logged into multiple exchange accounts and the server name is different for each one!  Very frustrating as everything else is working great.

Path to this result:

Installed 2012 Server in VMware environment.  Installed Exchange 2013 to coexist in same domain with the help of Exchange 2010 SP3.  Moved Mailboxes over to new Exchange 2013 server.  Moved essentially everything off of the old Exchange Server and into the new Server.  Uninstalled Exchange 2010.  Issue still persists.

I am sure there is a better way I could have done the migration, but short of this issue everything is working great.  The only other issue I noticed is I have to manually type in this address for the ECP configuration:

https://exchange2013/ecp/?ExchClientVer=15

If anyone has any idea on how I can have my Outlook clients realize the correct Exchange Server name (not GUID@domain.com), it would be greatly appreciated.

Thanks,

Ray

Free Windows Admin Tool Kit Click here and download it now
February 24th, 2013 6:47pm

If anyone has any idea on how I can have my Outlook clients realize the correct Exchange Server name (not GUID@domain.com), it would be greatly appreciated.

Thanks,

Ray


Hi,

Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the users primary SMTP address

The above is taken from What's New in Exchange 2013, Exchange 2013 architecture section and so what you see is by design.

February 24th, 2013 7:22pm

Martina,

Thanks for your quick reply!  I realized after I posted that this functionality was removed to assist with load balancing, etc.  That being said, do you know how I can add a second Exchange Mail Account to Outlook?  In the past I would simply Add new account and specify Server Name and User Name which would resolve and I would be done.  I have tried manually using the GUID@Domain.com with the user name and it still does not resolve.

Let me know if you or anyone else has any ideas of a work around.

Thanks,

Ray

Free Windows Admin Tool Kit Click here and download it now
February 24th, 2013 8:02pm

Adding a second Exchange account in Outlook is not any different than before. Autodiscover should take care of the settings.
What's new in Exchange 2013 is that RPC over TCP has been removed and only Rpc over HTTP (Outlook Anywhere) is used and its more important than ever to have a certificate installed that is trusted by the clients.

The Original Poster in this thread used a Self-Signed Certificate and that was his problem.

February 24th, 2013 8:14pm

Martina,

No need to respond as I have figured it out.

https://hosting.intermedia.net/support/kb//default.asp?id=2295

The key was to:

Input Server Name as before along with user

Click more settings

Connection Tab

Tick Connect to Microsoft Exchange using HTTP

Tick Fast and Slow Network Options.

The site says to use Basic Authentication, but it appears to have defaulted back to NTLM.  Regardless - It works!

Thanks,

Ray

Free Windows Admin Tool Kit Click here and download it now
February 24th, 2013 8:16pm

hi,

im experiencing the same issue, how did you configure your sonicwall to route back?

any help would be greatly appreciated.

thanks in advance

Ajay Paul

May 14th, 2013 3:35pm

You have to create a hairpin / loobback nat

source:LAN
Rewritten source: Firewall IP
Destination: Exchange Pub IP
New destination: Exchange Private IP
ports: http + https

Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2015 11:35am

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

Other recent topics Other recent topics