Member Avatar for hayesr3

To all,

First post from a newbie. I have a Firewalled server that my customers use to connect via VPN to transfer data to us. We are considering a move within the same building, but would need to move the server. Are there white papers or protocols somewhere that would help me understand the process of moving? We are a small company and only have a single Windows 2008 Server.

Also, I believe the move automatically means we have a new IP address, which would alter the VPN connection, correct?

Thanks for any thoughts or pushes in the right direction.

  • 2 Contributors
  • 2 Replies
  • 111 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by hayesr3

Dani AI

Generated

A concise, practical checklist for moving a single Windows Server 2008 inside the same building (answers for ; clarifies ’s “same setup” case).

Before you touch anything

  • Inventory current network settings and services (static IP, gateway, DNS, firewall/NAT rules, VPN type). Capture screenshots of the NIC properties and your edge firewall/router config.
  • Do a full backup and a System State backup so you can recover AD/DNS/Certificate stores if needed. Use Windows Server Backup or wbadmin for a quick image/System State export.
  • Export any SSL/IPsec certificates used by VPN (if SSTP or cert-based L2TP/IPsec). Document VPN client settings (endpoint IP vs hostname, auth method).

What to expect and how to avoid client breakage

  • Whether your public IP changes depends on the ISP/uplink and what hardware terminates the WAN. If the edge device or public circuit changes, the public IP will almost certainly change and VPN clients that target an IP will fail. Avoid this by using a stable DNS name (public A record or dynamic DNS) in VPN profiles so you can update DNS instead of every client. If you use SSTP, make sure the cert’s subject name matches that DNS name.

Move-day steps (brief)

  • Gracefully shut down services, label cables and ports, and restore the same static IP (if the new wall jack/VLAN is identical).
  • Bring the server up, verify NIC info and routing:
ipconfig /all
route print
netstat -an | find "LISTEN"
  • Confirm port/NAT forwarding on the edge firewall (PPTP: TCP 1723 + GRE; L2TP/IPsec: UDP 500, UDP 4500 + ESP; SSTP: TCP 443). Check RRAS/Remote Access service and Windows Firewall rules.

Quick troubleshooting

  • Ping gateway, then public DNS name. Use nslookup to verify public A records. Check Event Viewer for RRAS/VPN errors. If clients can’t connect, confirm the edge device is forwarding the correct ports/protocols and that the VPN certificate (if used) still validates.

Useful Microsoft refs: ipconfig command docs and Windows Backup (wbadmin) docs for System State backups:

Keep a rollback plan (restore backup, reconnect to original jack) and schedule the move during a maintenance window.

Member Avatar for steveaj

are you going to use anothe server.... i mean migration of server or just changing the location with same setup

Member Avatar for hayesr3

Just changing the loaction with the same setup.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.