We have a single windows 2008 sbs running exchange, which was working fine.
We have just upgraded our internet service to fibre, and along with this came a new router and a new static IP address.
We have updated our DNS records so that our mail is forwarded to the new public IP, and when checking with mxtoolbox, I can confirm that this change has been implemented correctly.
We can connect using OWA, and we can send mail just fine.
We are not receiving mail, and I am aware that the change to our dns may take some time to replicate for everyone, but when we run the smtp diag within mxtoolbox, it fails.
I can see that the IP address it is trying to connect to is correct, and we have opened up the ports on our new router for 443, 25, 80, 3389, and 987.
I know that we may not need all of these open, but that is what we have right now, all forwarded on to the local IP address of our exchange server.
Is it just that I need to give it time to replicate, or now that mxtoolbox confirms the correct public IP address for our server, should the smtp diag now work OK?
If it should, how can I trap this rather frustrating problem. Any assistance, would be appreciated.
I have also tried the Microsoft Connectivity Analyser and this too fails, but does not give any reason for doing so??