Exchange - Changing external static I.P, what needs to be done?

Posted on 2014-12-31
Last Modified: 2015-01-08
After an office move we have been dealt a new external i.p address

Our main server was receiving email fine before the move - I understand that we need to tell the DNS to point to the new I.P address rather than the previous address, which I did yesterday.

We still aren't receiving mail to the new address, should it take this long, is there anything else I need to check or change on the SBS 2008 (exchange) server? Or is it a case of just waiting a bit longer?

If I ping it does seem to be picking up the new i.p address but no 'reply'.
Question by:MadPC

Expert Comment

ID: 40525298
Is the port 25 opened (check FW also)?

run nslookup to check if the MX updated.
Depending on the MX timeout it might take up to 3 days for it to update worldwide.
LVL 13

Expert Comment

by:Andy M
ID: 40525314
Has your router been configured for the new IP or is it a new router? Is the IP address you have been given static or dynamic? (If it's dynamic speak to whoever provided it to get you a static IP otherwise email won't work correctly)

Typically the things to do would be:

1. Configure router for new IP address, test and ensure it is working (do a "whats my ip" from the server). If it's a brand new router configure port forwarding for port 25 and 443 to go to the exchange server.
2. Change MX/dns records so the primary mail record ( points to the new IP address.  
3. Await dns propagation - typically 24-48 hours depending on your domain host setup. I tend to find most major email providers/dns providers pick up the update within a few hours.

If you have access to a computer that's not on the same network as the server you could also run a telnet test to the IP/dns name to ensure mail flow is working.
LVL 76

Expert Comment

by:Alan Hardisty
ID: 40525343
You will also need to ask your ISP to setup Reverse DNS on your new fixed IP Address or some emails will start to bounce.


Expert Comment

by:Glenn M
ID: 40525647
Make sure on SBS you re-run the 'Configure E-mail and Internet Connection Wizard'. If you don't start seeing mail flow (which you should by now), run a DNSreport at and pay particular attention to the sections related to email. Any problems should be identified there.

Author Comment

ID: 40526623

First thing I should confess, in my original post i suggested that if I pinged it showed up the new I.P address - This isn't the case, or at least it isn't today - I may have made an error here as the new I.P is very close to the old one numerically.

@basil2912 - I've ran an nslookup, unfortunately it times out. Is there anyway to speed up the 72 hour process or at least find out if there is a way we can check progress of the change?

@Andy Morton - Nothing is different on the internal network, we have literally uprooted and moved all equipment to the new office, the only thing which has changed is the external (static) I.P address - I'm going to try telnet shortly to see what this throws up.

@Alan Hardisty - I've never heard of this before is it commonplace to do this? Our ISP hasn't changed, we are still with the same provider.

@Glenn M - I've ran the domain through, it threw up and error on the email
"All connections to Mailservers port 25 have failed. The standard port for SMTP transactions is 25, so your servers should be operating on that port. It is recommended that it be fixed in order for your mail service to operate properly. The Mail Servers that failed are: | failed message send with: failed cx open with: failed socket connect with: Operation now in progress

A telnet test also times out

Amy other suggestions welcomed!
3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.


Author Comment

ID: 40526799
As it turns out, I just checked the DNS records with the hosting provider and for whatever reason the record hadn't updated and was reporting the previous I.P address

I've just changed it (again) and it definitely seems to have saved now, I'll see how it goes, hopefully by tomorrow morning we should be good!

Author Comment

ID: 40528996

1. is still reporting the same error
"All connections to Mailservers port 25 have failed.


Telnet to the mail server is still unresponsive


Pinging the mail server I.P resolves to the updated address but the request times out


Re-running the 'Configure E-mail and Internet Connection Wizard' seems successful, although there is no issue with the internet connection, this doesn't solve the mail flow issue


If i put in to an off network browser/connection I get the IIS welcome screen


Running nslookup on the server reports 'unknown' but has a reference to the ISP


I can confirm the router is connected to the correct I.P and the server browser reports the correct I.P at
So, at the moment we are no further forward and the mail is not getting delivered - I'm totally at a loss with this so any other suggestions are very welcome!

It's been nearly 48 hours since the address was updated, is this just a waiting game?

Accepted Solution

Glenn M earned 500 total points
ID: 40529000
As per #4, if there is no issue with an Internet connection for browsing from the server and the ICW successfully completed but you can't telnet to the mailserver at the IP address you are supposed to have, that would lead me to believe that you don't actually have the new address yet.

To back up a bit and take the server config out of the equation, if you just connect a laptop directly to the router configured with the static IP you are supposed to be using, does it, in fact, work at that IP address?

An update for a DNS record should take no more than a couple of hours to propagate.

Assisted Solution

MadPC earned 0 total points
ID: 40529082
Cheers Glenn,

I think I've found the issue, apparently the 'Microsoft Exchange Transport' service wasn't started! I just started it and can telnet in no problem

It looks like for some reason that everytime the SBS is restarted that this service doesn't restart on its own for some reason, anyway that's a question for another day

interesting to learn that the DNS should only take a couple of hours to resolve, I'll bear that in mind if we switch I.P in future :)

thanks for all the suggestions!

Expert Comment

by:Glenn M
ID: 40529083
Glad you finally tracked it down.

Author Closing Comment

ID: 40537508
Found an issue with the Microsoft Exchange Transport service not starting automatically

Featured Post

[Webinar] Disaster Recovery and Cloud Management

Learn from Unigma and CloudBerry industry veterans which providers are best for certain use cases and how to lower cloud costs, how to grow your Managed Services practice in IaaS clouds, and how to utilize public cloud for Disaster Recovery

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Find out what you should include to make the best professional email signature for your organization.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now