Migrating to New Server causes network applications to crash

Question

I have had this happen now twice, and the common denominator seems to be me:

Windows Server Essentials (DC, GC, FSMO Roles)

Windows Server Standard

I add the server to the domain and check the domain health... (DCDiag) everything is fine.

I take my time creating shares on the new machine, setting permissions (usually cleaning up share sprawl, etc.), and move the shared drives over to the new server via GPO Drive Assignment changes. This usually takes days, not weeks, but never immediately.

I set up DHCP in failover mode, and change settings to point to the new server for DNS

I check DNS to make sure both servers see each other in the registered Name Servers.

This all seems to work without a hitch.

Except the network apps that were working fine on the old server... and work fine on the new server... just randomly kick out when I shut off the old server.

I turn the old server back on... no worries.

I removed the old server by moving it's FSMO roles. No errors, and a quick check shows all roles assigned to the new server.

I check the DNS on the new server - it only points to itself and the forwarders only go outward to the Internet.

I drop the original server to a member server by removing AD from it's services using Server Manager.

After making the original server a member server, the same problem still appears... Fine until I turn it off.

I have turned it off permanently, and let the system sit, no correction over time.

I have checked in the DNS Manager and did find that a reverse DNS had the original server as a name server still. I removed this from the DNS Manager.

The problem persisted.

I noticed that the reverse lookup of the Desktop machine from itself was failing.

I have now gone in and manually changed one Desktop client to not use netbios, and to manually add the Domain.local to the DNS settings in her network definition, and left the rest DHCP.

I am letting the user test and should know something later today on whether or not that had an effect.

I have had a similar problem on almost the same exact scenario on another client site. I suspect that I am doing something/missing something during migration, but I cannot think what. I have gone back over the migration guides and I think I am doing everything except using the "automatic data migration" tools from MS. Does anyone have a clue or had the same issues?

Answer 1

The problem turned out to be Drive Mappings with the Replace option left on after the migration.

Moving to Update mappings resolved the problem.

Thank you for your time and especially your willingness to help.

Answer 2

Hello,

It seems that you are experiencing issues with network applications after migrating servers. While the exact cause may vary, here are a few suggestions to troubleshoot the problem:

1. Verify DNS settings: Double-check the DNS settings on both the new server and the client machines. Ensure that the DNS configuration is correct and that all servers and clients can resolve each other's names.
2. Check firewall settings: Review the firewall settings on the new server and ensure that the necessary ports for the network applications are open. Make sure that the firewall is not blocking any incoming or outgoing connections.
3. Test connectivity: Use tools like ping or nslookup to test the connectivity between the client machines and the new server. Verify that there are no network connectivity issues or latency problems.
4. Monitor event logs: Monitor the event logs on both the client machines and the new server for any error or warning messages related to the network applications. This can provide insights into the specific issues that are causing the applications to fail.

Hope this helps.

Best regards

Zunhui