Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1426
  • Last Modified:

Exchange 2010 Autodiscovery url wrong on external use

Hello.
I have a wierd problem with my Exchange setup.

It started with users having problem using the Out Of Office function in outlook. I could use it without problem when located inside the domain but external users cant!

When I check the Autodiscovery url from an internal account (inside the domain) it shows up correct;
https://mail.domain.com/autodiscover/autodiscover.xml

But when I check Test email AutoConfiguration from an external outlook it gives me
https://domain.com/autodiscover/autodiscover.xml

PS gives me this :
[PS] C:\Windows\system32>Get-ClientAccessServer | Select Name, *Internal* | fl


Name                           : EMAIL
AutoDiscoverServiceInternalUri : https://mail.domain.com/autodiscover/autodiscover.xml

Open in new window


Anyone got a suggestion?
0
tigerffs
Asked:
tigerffs
  • 4
  • 2
1 Solution
 
tigerffsAuthor Commented:
Also, when I check the external URL in PS it gives me
[PS] C:\Windows\system32>get-webservicesvirtualdirectory | FL ExternalURL


ExternalUrl : https://OLDSERVER.domain.com/ews/exchange.asmx

Open in new window


It is pointing to the old exchange 2003 server, could this be the issue?


EDIT: I did set the externalURL to the correct one, it does not help me with the AutoDiscovery though
0
 
MASTechnical Department HeadCommented:
Try creating an A record 'autodiscover.domain.com' in your external DNS poiting to your external exchange IP
0
 
MASTechnical Department HeadCommented:
Change the external URL to

ExternalUrl : https://externalname.domain.com/ews/exchange.asmx
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
tigerffsAuthor Commented:
Really I just want to change the URL for autodiscovery for external use of outlook, pointing a fault adress seems like an shortcut.
0
 
tigerffsAuthor Commented:
abbasiftt:
I did that but it had no impact on the problem :(
0
 
tigerffsAuthor Commented:
Where does outlook get this AutoDiscovery link from? I need to be able to change it somewhere, but where!? For internal use = OK
External use = NOK
0
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
Create an "A" record in your public DNS called autodiscover and point it to your firewall with public IP. Get the firewall to forward 443 port traffic to this IP to your CAS server.

There is no setting for this. Outlook looks up the autodiscover record in the email domain of yours. So, if your email is user@domain.com, Outlook checks to find https://autodiscover.domain.com/autodiscover/autodiscover.xml

All you need to do is setup record in public DNS and route it to CAS.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now