Hoping some people can advise.
Rolled out a new servers last weekend.
We have two servers as example below:
Mainserver1 - Domain Controller - 192.168.1.1
Mainserver2 - Exchange 2013 - 192.168.1.2
Using exchange connectivity test, autodiscover fails to find domain or anything. Nothing is successful.
If i ping this address though it resolves to the correct IP address of the firewall.
The firewall has HTTP and HTTPS being forward to the Domain controller 192.168.1.1
I am not an expert with DNS or IIS but I am thinking that I need to do one of the following:
1. Go into the firewall and allow traffic for HTTP and HTTPS to 192.168.1.2 in addition to 192.168.1.1
2. Add a DNS entry to 192.168.1.1 pointing autodiscover towards 192.168.1.2.
On top of this, I am not sure if I need to do anything in IIS so not entirely sure what the best method is to get this resolved.
Grateful if anyone has the time to help me get it resolved as I am sure its pretty straight forward.
My internal outlook clients are also having trouble connecting.
Before I go ahead and confirm this record change could I just confirm the following:
Running Get-ClientAccessServer | FL AutoDiscoverServiceInternalUri from Exchange shell returns:
Do I need to make the 'Host offering this service:mail.mydomain.com/autodiscover/autodiscover'????
Essentially I want clients to connect externally via web app
Configure my internal cert and autodiscover to match so they work.
Does that sound right?
I was check in my test lab , that is perfect working in internally. Put Host offering this service : autodiscover.testdomain.com
and also HTTP redirect Autodiscover in the IIS to OWA URL . Here is the example.
- Edited by libra_ali786 Wednesday, November 13, 2013 3:44 PM
Still no luck with this.
This is the scenario in more detail and I would appreciate any help someone can give to help resolve.Server1 – Domain Controller
Far to much time wasted:
Server2 – Exchange Server
Exchange 2013 server setup fresh but clients internally cannot connect to the server using Outlook. So far I can confirm the following:
I created a self signed cert with loads of entries including:
On running :
Get-ClientAccessServer :: FL AutoDiscoverServiceInternalUri
the following is returned:
If I ping autodiscover.myexternaldomain.com the IP address is correctly resolved so I can get to the firewall.
The firewall has a rule that allows HTTP and HTTPS to the domain controller.
The domain controller has a SRV record within which reads:
What am i missing??? Anyone know?
Input the https://autodiscover.testdomain.com/autodiscover/autodiscover.xml in IE and see whether code 600 is returned. If so, it means autodiscover works fine.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact email@example.com
TechNet Community Support