Windows Firewall Blocks QuickBooks Desktop: The Accepted Fix and Ports
Windows firewall rules can block QuickBooks Desktop and its company files; the accepted fix covers repair tools and manual port exceptions.
QuickBooks Desktop users on Windows keep running into the same obstacle: the operating system’s firewall blocks the network access the program needs, and error messages follow. A recently refreshed, formally accepted answer in the vendor’s Canadian English documentation lays out a three-stage fix, moving from repair tools to manual port exceptions. We went through the full procedure so you know what it involves before you touch a single setting.
The symptoms users report
The trouble usually appears when a company file opens, most often on a networked machine or in multi-user mode. Windows flags specific programs or files and denies them access, which produces an error message rather than a crash. The wording varies by version, but the trigger stays consistent: a firewall rule is holding the door shut.
That pattern matters for diagnosis. The block sits in the environment, not in the company file, so reinstalling the program rarely helps and repairing the file is only half the story.
Can the repair tools fix it on their own?
Intuit’s QuickBooks Tools Hub is the first stop. Install the hub, open it, and choose the Company File Issues section. From there, launch QuickBooks File Doctor. The tool can take up to a minute to appear, and if it never does, you can search for it from the Start menu and open it directly.
Inside File Doctor, pick your company file from the dropdown, or browse for it if it is not listed. Choose the option that checks both the file and the network, then continue and enter the QuickBooks admin password. Scan times run up to about five minutes and scale with file size.
One quirk deserves a mention. The scan can report itself unsuccessful even when it has fixed the problem, so the real test is reopening the company file afterward. If errors persist at that point, the accepted answer moves on to manual firewall configuration.
Manual port exceptions, version by version
The manual work happens in the advanced settings of Windows Firewall. From the Start menu, open Windows Firewall and select Advanced Settings. Create a new inbound rule, choose Port, make sure TCP is selected, and enter the specific local ports your version needs.
- QuickBooks Desktop 2020 and later: 8019, plus the dynamic port assigned at install.
- QuickBooks Desktop 2019: 8019, plus the dynamic port assigned at install.
- QuickBooks Desktop 2018: 8019, 56728, and 55378 through 55382.
- QuickBooks Desktop 2017: 8019, 56727, and 55373 through 55377.
If several versions live on the same computer, repeat the rule for each one. A single rule that covers only the newest install leaves the older years blocked. In multi-user setups, the machine hosting the company file is usually where these exceptions matter most.
Where do you find the dynamic port number?
Versions from 2019 onward do not rely on a published range. Installation assigns each one a dynamic port, a single number rather than a span, so that version gets exclusive use of it. The familiar 8019 entry still applies alongside it.
The assigned number lives in QuickBooks Database Server Manager. Open that utility from the Start menu, go to the Port Monitor tab, and note the port beside your version. That is the number your firewall exception needs. A Renew button can change the assignment, though only for 2019 and later; if you use it, visit the Scan Folders tab and scan again so the firewall permissions reset.
Do you need outbound rules as well?
The accepted answer mentions creating outbound rules after the inbound ones. On a default Windows setup, however, the firewall permits outgoing traffic, so the inbound exception is what usually clears the block. Outbound rules earn their keep only when third-party security software or a corporate policy restricts outgoing connections. We would treat them as conditional, not mandatory.
A few closing points
Two details round out the picture. The guidance sits in the vendor’s Canadian English help pages, yet nothing in it is specific to Canadian installs; any Windows machine running the desktop program follows the same port logic. And the fixed ranges for 2017 and 2018 never change, which makes those exceptions a one-time job.
The dynamic ports introduced with 2019 are the ones that catch people out, most often after a reinstall or a port renewal. Whenever the exception looks right but the error returns, check the Port Monitor tab again before assuming anything else broke.