I'm in the process of migrating a Windows server stack from a local datacenter to EC2, and I'm encountering some issues. My setup includes one Domain Controller (DC), one SQL Server, and one web server, all currently virtualized. I'm using the AWS Migration Service to create images, and so far, that part seems to be working well. However, I'm trying to launch the DC first, but there's something going wrong with the network interface of the server that's getting launched. I can't connect to the server at all, and although I can generate a screenshot indicating that it's online, I can't RDP into it or get a response from the serial console. The event logs suggest that DNS is not resolving any domain name calls. Just to test the network, I created a clean Windows server from an AWS AMI in the same VPC/subnet, and I can connect to that instance without a problem.
Here's what I've tried so far: adding an additional network interface, manually changing the DNS server NIC settings via the registry on the detached drive, and even setting up a temporary DC at the expected internal IP. I feel like I might need to tweak the DHCP option sets in the VPC or adjust the launch template for the new DC, but I'm at a loss and just trying random configurations now. Has anyone else successfully migrated a DC to EC2 and dealt with network or DNS issues during the initial phase? Thanks in advance for any insights!
2 Answers
It sounds like you're having a tough time! Consider establishing a VPN tunnel between your VPC and your on-prem setup. You could then launch a new Windows server and promote it to a new domain controller. Afterward, you can migrate your web and SQL servers using the application migration wizard, and finally demote the old DC. Also, check if you've statically configured the IP on your DC; that might be causing network issues if it's not getting the proper IP from the VPC. It's worth verifying the status checks for your EC2 instance as well.
You might want to change the IP to be DHCP assigned for troubleshooting. A static IP from your local network probably won't match the CIDR range of your VPC/subnet. It can cause connection problems if the DC is trying to use an IP that isn’t available in the new environment.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures