outlook over http does not work since isp changed
We have an SBS2003 Standard Edition DC plus a Terminal Server running Windows 2003 64-bit Server.
We have staff located at several physical sites who use Outlook to connect to the Exchange Server in SBS via Outlook Anywhere (connec to Exchange over HTTP).
We also have users who use REmote Desktop Connection to connect to the Terminal Server.
Last week we changed ISPs. I had our domain host (who was our previous ISP) change the MX records to the new IP address.
Interanally connected systems run Outlook and can all send and receive email to both internal and external email addresses, so I figure the MX forwarding must be working.
As soon as I swapped over to the new ISP, RDC stopped connecting....not surprising. I had users change the server address from the domain name to the new IP address and that worked straight away. However, now four days later, I still can't connect via RDC with the domain name. I think this sounds like some sort of DNS issue, but I would have thought the IP/domain combination would have propegated by now.
I also discovered today that none of our off-site users can connect to Exchange with Outlook Anywhere. This is a big problem.
Any help would be great!
Cheers,
Greg
We have staff located at several physical sites who use Outlook to connect to the Exchange Server in SBS via Outlook Anywhere (connec to Exchange over HTTP).
We also have users who use REmote Desktop Connection to connect to the Terminal Server.
Last week we changed ISPs. I had our domain host (who was our previous ISP) change the MX records to the new IP address.
Interanally connected systems run Outlook and can all send and receive email to both internal and external email addresses, so I figure the MX forwarding must be working.
As soon as I swapped over to the new ISP, RDC stopped connecting....not surprising. I had users change the server address from the domain name to the new IP address and that worked straight away. However, now four days later, I still can't connect via RDC with the domain name. I think this sounds like some sort of DNS issue, but I would have thought the IP/domain combination would have propegated by now.
I also discovered today that none of our off-site users can connect to Exchange with Outlook Anywhere. This is a big problem.
Any help would be great!
Cheers,
Greg
You can also use http://www.kloth.net/services/dig.php to check other DNS records for your domain to make sure everything that should be pointing to the new IP's are.
ASKER
Hmmm, so MX Toolbox tells me that the mail is being forwarded by the domain host, which I knew.
The MS connectivity tool failed to connect.
When I put the external IP of my router into the MX Toolbox, I got a mixed result, but the following could be helpful...
Warning - Reverse DNS does not match SMTP Banner
However, I am not exactly sure what to do with that info.
Cheers,
Greg
The MS connectivity tool failed to connect.
When I put the external IP of my router into the MX Toolbox, I got a mixed result, but the following could be helpful...
Warning - Reverse DNS does not match SMTP Banner
However, I am not exactly sure what to do with that info.
Cheers,
Greg
When I put the external IP of my router into the MX Toolbox, I got a mixed result, but the following could be helpful...If that is the IP that is sending your mail, then yes that is something you should address, but is not related to the original issue. Ask your ISP to change the PTR record for that IP to match the A record of your sending server.
Warning - Reverse DNS does not match SMTP Banner
Check out that last link that I posted and test your forward records, such as the hostname that you used in the connectivity test.
On a related note, you should create/modify SPF records for your sending domain(s) and put your sending server(s) IP's in there. Let's focus on the original problem for now.
ASKER
'Check out that last link that I posted and test your forward records, such as the hostname that you used in the connectivity test.'
I put in the doamin and got an IP back which is different to our current IP (from the new ISP). I then did a whois lookup on the IP address and it belongs to our old ISP.
So, as I suspected, our domain name is still being pointed to our old IP address. How can I get our domain pointed to the new IP?
Cheers,
Greg
I put in the doamin and got an IP back which is different to our current IP (from the new ISP). I then did a whois lookup on the IP address and it belongs to our old ISP.
So, as I suspected, our domain name is still being pointed to our old IP address. How can I get our domain pointed to the new IP?
Cheers,
Greg
Hi,
Have you checked name resolution for your domain?
From your a machine that is failing to connect see what you resolve for (say) smtp.yourdomain.com (obviously make that whatever you really are). It could be that they are using a DNS resolver that is still out of date. If so, they'll either have to using the actual IP until their resolver (their ISP likely) gets with it, or use a different nameserver.
Alan.
Have you checked name resolution for your domain?
From your a machine that is failing to connect see what you resolve for (say) smtp.yourdomain.com (obviously make that whatever you really are). It could be that they are using a DNS resolver that is still out of date. If so, they'll either have to using the actual IP until their resolver (their ISP likely) gets with it, or use a different nameserver.
Alan.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I contacted the new ISP to see if they could update DNS for our local domain and they pointed me back to our old ISP who still hosts our website and forwards our email. It was all up and working within minutes of making the request.
So, thanks Papertrip, for your help to work through this one.
Cheers,
Greg
So, thanks Papertrip, for your help to work through this one.
Cheers,
Greg
ASKER
Thanks Papertrip for helping me work through this problem. There were a few steps that we needed to follow to track down the source of the issue, but with your guidance we got there in the end....and I picked up a few more tools to add to my kit!
Thanks heaps,
Greg
Thanks heaps,
Greg
Check to see that the IP's of the MX record(s) is your new IP, and run an SMTP test as well to check for other potential issues.
You can also use https://www.testexchangeconnectivity.com/ to further test things such as ActiveSync/autodiscover/et