TMGpro01
asked on
Moving RDP/TS Server to New Building.
Hello,
I have been asked to move a Terminal Server/RDP server that is a VM machine on a Server that serves also as a DC within two days! The server and their Dell Sonicwall TZ400 will be moved across the city to a temporary location but they still want it accessible to employees during the interim. Honestly, I am not certain what all settings I will need to change to point the employees to the new IP address on the sonicwall and server. I am aware they will need to adjust the IP/port on their RDP clients individually, but I need some direction as to what on the firewall and/or the Physical and VM server to make this work. I do have available static IPs at the new location.
I have tried using the trusty Google, however I only find ways to trransfer license and CALs etc, but that is not the case. I am just physically moving the server and firewall from one location to the next with no hardware changes other than ISP/IP address. Any assistance is greatly appreciated.
Thanks!
I have been asked to move a Terminal Server/RDP server that is a VM machine on a Server that serves also as a DC within two days! The server and their Dell Sonicwall TZ400 will be moved across the city to a temporary location but they still want it accessible to employees during the interim. Honestly, I am not certain what all settings I will need to change to point the employees to the new IP address on the sonicwall and server. I am aware they will need to adjust the IP/port on their RDP clients individually, but I need some direction as to what on the firewall and/or the Physical and VM server to make this work. I do have available static IPs at the new location.
I have tried using the trusty Google, however I only find ways to trransfer license and CALs etc, but that is not the case. I am just physically moving the server and firewall from one location to the next with no hardware changes other than ISP/IP address. Any assistance is greatly appreciated.
Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The client's use the IP address directly so I will have to inform them of the new IP address but the same port. You are correct in nothing behind the door changing. I think where it stands I will have to change the static IP address and the subnet mask on the X1 Interface on the Dell Sonicwall to reflect the new ISP and then the rest should fall into place. Sounds right?
Thank you all for your help.
Thank you all for your help.
At your registrar change your DNS A record TTL record to perhaps 30 minutes. the day of the move change the ip address in the A record to point to your new IP address. Pack up and move the hardware to the new location. Plug it in and shortly the users that try and connect to remote.example.com will get the new ip address
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I just wanted to post on here for you all to have reference for future questions and situations. Below is what I did to accomplish this as it appears to be working as intended for now.
After moving the Firewall and RDP Server from a Comcast modem to AT&T Uverse modem, I had to take the following actions.
Connect locally to the firewall from the RDP Server, after there I had to use a static IP from my block that I had on hand. The AT&T used at /29 CIDR so I had to convert that to the 255.255.255.248 and input their DNS servers 1 and 2 as well as my target IP address. After I configured this, the firewall was recognized on the Modem. "The firewall was not recognized prior to this because there was a subnet overlap issue so forcing these changes on the Static settings was key."
After the modem recognized the MAC address of the firewall, I had to create a Pinhole/DMZ to allow all applications. Creating this allowing the port assigned to the RDP Server to began accepting login requests. After the changes were made, I rebooted the network completely and after its powering up, the services worked. Just to clarify what AT&T told me regarding default blocked ports. They said that on DHCP Public IP addresses the port 3389 is default turned off on business and all residential servers. However since it was a business and I had static IP addresses, no ports are blocked unless requested.
Thank you all for your contributions!!!
Best,
James
After moving the Firewall and RDP Server from a Comcast modem to AT&T Uverse modem, I had to take the following actions.
Connect locally to the firewall from the RDP Server, after there I had to use a static IP from my block that I had on hand. The AT&T used at /29 CIDR so I had to convert that to the 255.255.255.248 and input their DNS servers 1 and 2 as well as my target IP address. After I configured this, the firewall was recognized on the Modem. "The firewall was not recognized prior to this because there was a subnet overlap issue so forcing these changes on the Static settings was key."
After the modem recognized the MAC address of the firewall, I had to create a Pinhole/DMZ to allow all applications. Creating this allowing the port assigned to the RDP Server to began accepting login requests. After the changes were made, I rebooted the network completely and after its powering up, the services worked. Just to clarify what AT&T told me regarding default blocked ports. They said that on DHCP Public IP addresses the port 3389 is default turned off on business and all residential servers. However since it was a business and I had static IP addresses, no ports are blocked unless requested.
Thank you all for your contributions!!!
Best,
James
ASKER
Interim means this is temporary, but in a few weeks I will have to make the same move again to the permanent location.
I am literally picking up the Firewall and server that is in use now, hooking them up at a temporary location and turning them back on. Non of the hardware is going to change except it will be connected to a new modem which will not have the same Public IP address that it has now. There are not any firewall to firewall VPN's that I can see. I just logged into the firewall and do not see any tunnels active or even configured. The clients will be off site, as in they are working from home during this time period and will be using RDP Clients on their computers to remote into the TS/RDP Server.