Troubleshooting
Fixes for the problems small offices hit with Windows Server, SQL Server and remote access.
Each guide starts with the symptom you see and ends with the fix. They come from real office setups, so the steps are the ones that worked.
Network and file sharing
Ping Works, but the New Windows Server Can't Open Other PCs' Shared Folders
The new Windows Server 2022 can't open a PC's shared folder though ping and port 445 work. Guest logons and SMB signing are the cause. The fix.
Read the fix →After Installing a VPN, the Server Can't Find Office PCs by Name
After installing Tailscale or another VPN, the server reaches PCs by IP but not by name. The VPN took over DNS. How to check it and turn it off.
Read the fix →SQL Server
ERP Can't Find SQL Server: 'PC\SQLEXPRESS' Not Found (Error 26 or 40)
ERP can't connect to SQL Server Express by instance name (error 26 or 40)? Turn on TCP/IP, fix port 1433 and start SQL Browser. Step-by-step fix.
Read the fix →Named Pipes or TCP for SQL Server: Which Should Your ERP Use?
Named pipes or TCP/IP to connect an ERP to SQL Server on a LAN? TCP on port 1433 breaks less often. Compare both and see how to switch.
Read the fix →Remote Desktop and VPN
Remote Desktop Won't Connect Even Though the Firewall Rule Is Right
Remote Desktop won't connect and the firewall allows port 3389? Nothing may be listening. Check the service, registry and port, and when to reboot.
Read the fix →Never Open Remote Desktop (Port 3389) to the Internet: What to Do Instead
Forwarding port 3389 exposes your server to password guessing and ransomware. Check if it is open, close it and use a VPN for safe remote access.
Read the fix →New server
New Windows Server 2022 for a Small Office: A Checklist Before You Move the ERP
Going live on a new Windows Server 2022? Check network profile, file sharing, SQL Server, firewall, remote access and backups first. Short checklist.
Read the fix →