Tim
asked on
DNS settings (Internal, External) - Exchange 2010 Autodiscover settings
I have a problem that I really don't know were to start on troubleshooting. Recently we migrated from Exchange 2003 to Exchange 2010 so we could eventually migrate to Exchange 2016. In the process of moving mailboxes I have encounter an issue with Autodiscover and don't know where the issue is. My users can connect to the Exchange server through the web but when they input their user name and password it does not take but when they log onto OWA they can access the server so there is a disconnect between Outlook and the server when trying to connect through the internet.
First, I went to our registrar on the internet and created an A record with Autodiscover pointing to our Public ip address for our Exchange server but when I run testconnectivity it tells me it cannot find a CNAME record for Autodiscover. I deleted the A record and created a CNAME record on the registrar but that didn't work either.
Our SMTP connection points to a Barracuda Spam appliance so I am thinking that is the name that is confusing the SSL connection but if so how do I include the Barracuda name into the SSL when configuring the SSL through Exchange 2010?
There is much help I need on this and really am having a hard time first finding where the problem lies.
First, I went to our registrar on the internet and created an A record with Autodiscover pointing to our Public ip address for our Exchange server but when I run testconnectivity it tells me it cannot find a CNAME record for Autodiscover. I deleted the A record and created a CNAME record on the registrar but that didn't work either.
Our SMTP connection points to a Barracuda Spam appliance so I am thinking that is the name that is confusing the SSL connection but if so how do I include the Barracuda name into the SSL when configuring the SSL through Exchange 2010?
There is much help I need on this and really am having a hard time first finding where the problem lies.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you clarify what's meant by "there is a disconnect between Outlook and the server when trying to connect through the internet."? Is your Outlook user outside the firewall and trying to connect to Exchange server and they weren't able to? How about when the user is internal, do they have the same issues? Can you post the exact error message the user was getting?
ASKER
I mean by that comment that Outlook will not connect to the exchange server when outside the network but when inside the network via VPN or physically it works fine and accepts the user name and password.
I checked the DNS externally and Autodiscover points the the public IP address of the new Exchange server. I also made sure Autodiscover is setup in IIS on the Exchange 2010 server. I did notice that the CNAME in our internal DNS server was pointed to the Barracuda spam server so I changed it to point the mail.server.com name.
Should I have the Barracuda set in the CNAME section on the registrar or should I remove it? It is currently pointing to mail.server.com. Maybe that is my issue if Barracuda does not need to be referenced.
I checked the DNS externally and Autodiscover points the the public IP address of the new Exchange server. I also made sure Autodiscover is setup in IIS on the Exchange 2010 server. I did notice that the CNAME in our internal DNS server was pointed to the Barracuda spam server so I changed it to point the mail.server.com name.
Should I have the Barracuda set in the CNAME section on the registrar or should I remove it? It is currently pointing to mail.server.com. Maybe that is my issue if Barracuda does not need to be referenced.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Note that I have set this up for many users to connect to the office from externally without issues. If your Outlook works fine when internal or via VPN then the problem is with Outlook Anywhere configuration.
If the problem is DNS related then you can bypass this by using direct IP (test by replacing the URL with IP in Outlook proxy settings). Failing this, then it's port issues (closed or no port forwarding) or other firewall rule issues. If both of these don't apply then the problem is with Autodiscover but that's unlikely because Outlook works internally or via VPN.
If the problem is DNS related then you can bypass this by using direct IP (test by replacing the URL with IP in Outlook proxy settings). Failing this, then it's port issues (closed or no port forwarding) or other firewall rule issues. If both of these don't apply then the problem is with Autodiscover but that's unlikely because Outlook works internally or via VPN.
ASKER
Thank you to all those who helped with this issue. There were many issues that were causing this problem external DNS, Internal DNS and Outlook config but due to your suggestions and help I was able to get this all corrected.
Glad to have helped tparus. Cheers!