Most "the new server doesn't work" problems are the same few settings. Go down this list before the staff start using the new server, not after.
1. Fixed IP and a clear name
- Give the server a fixed IP, or a DHCP reservation on the router, so it never changes.
- Use a short computer name with no spaces. Everyone will type it.
2. Network profile and sharing
Get-NetConnectionProfile
The office network should be Private. If it says Public, fix it:
Set-NetConnectionProfile -NetworkCategory Private
Enable-NetFirewallRule -DisplayGroup "File and Printer Sharing"
Enable-NetFirewallRule -DisplayGroup "Network Discovery"
3. Can the server open the PCs, and the PCs the server?
Test both directions. The older PCs can often open the new server, while the server cannot open them, because Server 2022 blocks guest logons and requires SMB signing. See the server can't open other PCs' shared folders.
4. SQL Server
- Is TCP/IP enabled, with a fixed port (1433) and the firewall open? See ERP can't find SQL Server.
- Are the SQL logins in place? A database restored from the old server does not bring its logins.
- Is Mixed Mode authentication on, if your software uses
saor SQL logins? - Change the programs' connection strings to the new server, and prefer TCP. See named pipes or TCP.
Test from a different PC, not from the server:
Test-NetConnection SERVER -Port 445
Test-NetConnection SERVER -Port 1433
5. Remote access
- Do not forward port 3389 on the router. See never open Remote Desktop to the internet.
- If you add a VPN, check afterwards that the server still finds PCs by name. See VPN breaks computer names.
6. Antivirus
Quick Heal, Seqrite and similar tools have their own firewall that can block SQL, file sharing or Remote Desktop even when Windows allows it. If a port is open in Windows but a test still fails, check the antivirus.
7. Backups
- A backup that runs every night is not the same as a backup that restores. Restore one now, beside the live data, and open it. See how to check your backups really restore.
- For SQL Server Express, which has no built-in scheduler, see how to automate SQL Server Express backups.
8. Restart once and test everything again
Restart the server and wait two minutes. Then re-run the tests above. Some problems appear only after a reboot, for example a service that doesn't start, or a VPN that changes DNS on start. It is much better to find them now than on Monday morning.
Related guides
- Ping Works, but the New Windows Server Can't Open Other PCs' Shared Folders
- After Installing a VPN, the Server Can't Find Office PCs by Name
- ERP Can't Find SQL Server: 'PC\SQLEXPRESS' Not Found (Error 26 or 40)
- Named Pipes or TCP for SQL Server: Which Should Your ERP Use?
← All troubleshooting guides