URGENT HELP: New static IP address now cant remote access servers.

How are they accessing the servers? If you have been given a new static IP

You need to change MX, A records with the new IP if you use VPN tunnels you need to recreate the setup file to reflect the new ip

firewall-rules correct with the NEW Ip?
would be great if you can give some more information on your setup.

Ove

When you say remote sites are there firewalls between the 2? if so the rules on the firewall are more then likely natted with the old IP you need to look at the firewall rules and change every entry with the old ip to the new ip

I believe it is something to do with DNS records as I just got a call from someone that sent an email to me and it bounced back. So how do i change this?
Also the VPN tunnel will need to be altered, if someone can tell where i can look for the setting i will post em up.
Using Windows Server 2003.

Also there are two servers, one for exchange and storage the other is for terminal sessions.

OK who hosts your domain name? do a whois lookup you need to go to the person who managed your domains and tell them of the new IP change and get them to make the changes you then need to look on your firewall and change all records pointing to old ip to reflect the new ip

Which VPN tunnel do you use?

Your MX records - Mail Exchange records, A records for all domains you have i.e. outlook web access etx all these need changing to reflect the new IP you need to liaise with the whoever manages your domain or tell us the name of the domain and we will try to dig out

once you change the dns, you will need to wait a little while for it to update to all people trying to contact you - so dont expect it to work straight away.

Once your dns is fixed your vpn may also work - depends if it is contacting by IP or by name.

Do a MX lookup on your domain name for emails i.e @companymail.com

http://www.mxtoolbox.com/

You will see that it points to the old ip

Do the same for all other websites like owa etc and again they will point to the old ip, DNS and MX changes are not instant so you gotta start moving on this so the impact is not as big as your going to start loosing emails

Yep pointing to old IP, so is it as simple as ringing the ISP and telling them the  static IP has changed?

assuming your ISP is responsible for your DNS - this isnt always the case, but fairly likely.
do a whois lookup as suggested above to findout who is hosting your domain.

sometimes it is hosted by the company that has developed your website.

okay, DNS records has now been changed. However the IP address they had was differant to what came up on the lookup!? ISP says 1hr for the change. So we will see how it pans out in an hour. Appreciate ur quick responses!!! will come back in an hour.

make sure they idnt change your www address if that was hosted somewhere else.

no problem just give it sometime and check again

do a nslookup for the domain names and an mx lookup from time to time to see the changes you will be fine also please make sure your firewall rules reflect the new IP i.e. if your natting smtp connections for port 25 you need to make sure the rule on your firewall takes into effect the new public ip do the same for any other policies which show the old ip and you wont have any problems

yes as wolf says they are probably changing your www records did you specify mx record change?

the lookup address should be the one you need to change and should have the old ip static ip

ok well everyone can connect to the VPN, however remote desktop aint working.

but a weird thing happened, a user appeared under the tsadmin console and then it went to idle pretty much straight away and the users says it is telling him he cant connect.

Clear the session and try again monitor it then have a look at the event logs on the server and what do you spot?

are the users connecting to the terminal after connecting to the vpn.
how do they connect - with a full domain name eg terminal.company.com or just the internal name eg
terminal - or the internal server Ip address?

Ok it was a firewall rule that was blocking it, wrong port was open. Not getting emails from out side the domain now though, so i gather that will be another rule, any one know what port should be open for exchange?

25 SMTP

normally DNS-records are cached for a day or (also seen up to three days)...so due to the "time to life (ttl)" it will last that long until other mail-servers ask for your actual ip from the MX-record. So the next time email-flow should start.

Do you get onto your email-server from outside when trying :

telnet <yourNewIp> 25

from your home-computer ?
You normally should get a line starting with "220...<your mailserver>...ready"

If this works does:
telnet <yourMXDomainName> 25

also work?

Ove

still getting nothing from external emails.
I have the following rules setup in port forwarding;

- SMTP -
Protocol = TCP
Port Start + 25
Port End = 25
Port Map = 25
- DNS -
Protocol = UDP
Port Start = 53
Port End = 53
Port Map = 53

Right?

create a nat rule on your firewall for SMTP

From: Any
To: NAT Public IP - Private IP of exchange server
Port 25

Event log is showing issues with DNS - Event IDs - 5504 and 7062 seem to be quite regular.

http://support.microsoft.com/kb/920162

did you get your mx record updated also?

ok its to do with antivirus mail messenger service (trend mirco) I have to change the IP address with them as well cause at the moment the emails are sitting with them waiting to go some where. Hope fully that sorts it. Thanks everyone for your help.