QuickBooks Multi-User Error Guide
QuickBooks Cannot Communicate with the Company File
Your workstation is displaying: "Error: Cannot communicate with the company file due to a firewall" or "QuickBooks software on your computer is unable to communicate with the company file on [SERVERNAME]"
This error message is an umbrella — it appears when any part of the connection between a workstation and the server hosting the company file breaks down. The firewall is specifically named in the message, but at QuickFix Bookkeeping we see this error caused by five different root causes — and only one of them is the firewall.
The QuickFix Bookkeeping Distinction
This error message blames the firewall — but the firewall is only one of five causes. Diagnosing the right one first cuts resolution time from hours to minutes.
The five causes — and how to tell them apart in 2 minutes
1. Hosting misconfiguration
Clue: affects all workstations simultaneously. Server likely has hosting off, or a workstation has hosting on.
2. QuickBooks services stopped
Clue: appeared after server reboot or Monday morning. All workstations affected.
3. Firewall blocking ports
Clue: appeared after new antivirus or Windows update. File opens locally on server but not from workstations.
4. Folder permissions wrong
Clue: specific users affected but not others. QBDataServiceUser lacks Full Control.
5. Stale or corrupted .ND file
Clue: appeared after server migration, IP change, or company file moved to new folder.
Start with your clue
Match your situation to a clue above, then jump directly to that method below. Do not start at Method 1 if the clue points elsewhere.
What Is the "Cannot Communicate with Company File" Error?
Error type
Network communication failure
QuickBooks Desktop · Multi-user mode
Overlaps with H-series and 6000-series errors
What it means
This error appears when a QuickBooks workstation attempts to open or access a company file stored on another computer (the server) and fails to establish the connection. It is a generic network communication failure message that QuickBooks shows when any part of the connection path is broken — which is why matching the symptom to the cause before troubleshooting is so important.
Your company file is safe. This is a connection error, not a file damage error. The .QBW file on the server is intact — only the access path is broken.
How This Error Appears — Common Variants
"Error: Cannot communicate with the company file due to a firewall."
The most common variant. Firewall is mentioned but is not always the actual cause.
"It appears the QuickBooks software on [SERVERNAME] is set up to allow shared access to the company file, but the QuickBooks software on your computer is unable to communicate with it."
Typically caused by hosting misconfiguration or firewall.
"QuickBooks is unable to open the company file on the network."
Often caused by .ND file corruption or permissions issue.
How to Fix — Match Your Clue to the Right Method
Use the clue from the box above to go directly to the relevant method. If your clue is unclear, start with Method 1 — it is the most broadly effective first step.
METHOD 1
Run QuickBooks File Doctor
Best first step — diagnoses and fixes automatically
QuickBooks File Doctor runs a simultaneous check on both company file integrity and network connectivity, automatically fixes firewall port exceptions, and identifies hosting and permissions issues. It is Intuit's own diagnostic for this error and resolves a significant portion of cases without manual intervention.
1
On the server computer, open QuickBooks Tool Hub → Company File Issues → Run QuickBooks File Doctor.
2
Select your company file from the dropdown (or Browse to find it). Choose Check your file and network. Enter your QuickBooks admin password. Click Next and let the scan run — up to 15 minutes.
3
Test multi-user access after the scan regardless of the tool's report — File Doctor often resolves the issue even when the result message says it could not fix everything.
QuickFix tip: Run File Doctor from the server, not from a workstation. File Doctor needs server-level access to fully diagnose and repair firewall permissions and network data files. Running it from a workstation gives it less access and produces less complete results.
METHOD 2
Fix Hosting — One Server, All Workstations Off
Clue: all workstations affected simultaneously
Hosting misconfiguration is the most common cause of this error when all workstations are affected at once. Only one machine — the designated server — should ever have hosting enabled. This needs to be verified on every computer on the network.
1
On each workstation (not the server): Open QuickBooks without opening a company file. Go to File → Utilities. If you see "Stop Hosting Multi-User Access" — click it. Workstations must show "Host Multi-User Access" (i.e., hosting is off).
2
On the server: Open QuickBooks. Go to File → Utilities. Confirm "Stop Hosting Multi-User Access" is shown — this means hosting is ON. If it shows "Host Multi-User Access" — click it to enable hosting.
3
On the server: go to File → Utilities → Stop Hosting Multi-User Access → Yes → File → Utilities → Host Multi-User Access → Yes. This resets the hosting service entirely and often resolves lingering communication errors after the hosting toggle.
4
Test multi-user access from each workstation: File → Switch to Multi-User Mode.
METHOD 3
Restart QuickBooks Services on the Server
Clue: appeared after server reboot or Monday morning
If the error appeared after the server was restarted, a Windows update ran overnight, or it surfaces every Monday — the QuickBooks Windows services stopped and were not set to restart automatically. This is a 5-minute fix.
1
On the server, press Windows + R → type services.msc → Enter.
2
Find QuickBooksDBXX (e.g. QuickBooksDB34 for 2024) and QBCFMonitorService. Right-click each → Restart. If either shows Stopped → right-click → Start.
3
Double-click each service → set Startup type to Automatic → Apply → OK. This permanently prevents the Monday morning recurrence.
METHOD 4
Configure Firewall Port Exceptions for QuickBooks
Clue: appeared after new antivirus or Windows update
Windows Firewall or a third-party security product is blocking the ports QuickBooks uses for multi-user communication. Running the Database Server Manager scan from Tool Hub automatically configures the correct exceptions — try this before manual firewall configuration.
1
Automatic route: On the server, open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager → Start Scan. The scan creates correct firewall exceptions automatically alongside fresh .ND files.
2
Quick test: Temporarily disable Windows Firewall on the server and test multi-user access. If the error clears — the firewall is confirmed as the cause. Re-enable and add manual exceptions instead of leaving it disabled.
3
Manual exceptions: In Windows Defender Firewall → Advanced Settings → create Inbound and Outbound rules for TCP ports 8019 and 55373–55378. Also add program exceptions for QBW32.exe, QBDBMgrN.exe, and QBCFMonitorService.exe.
METHOD 5
Set Correct Folder Permissions for QBDataServiceUser
Clue: specific users affected, not all workstations
The QuickBooks Data Service user account — QBDataServiceUserXX — must have Full Control over the company file folder. If it lacks permission, the Database Server Manager cannot serve the file to workstations. This is particularly common after a Windows account reset or a server OS reinstall.
1
On the server, navigate to the folder containing the company file. Right-click → Properties → Security → Edit.
2
Look for QBDataServiceUserXX in the list (XX = your QB version year). If not present — click Add, type QBDataServiceUser, click Check Names, and add it. Set permissions to Full Control. Click Apply → OK.
3
Also ensure QBDataServiceUserXX is a member of the local Administrators group: open Computer Management → Local Users and Groups → Groups → Administrators → Add the QBDataServiceUser account.
QuickFix tip: QBDataServiceUser permissions issues are most common after a Windows Server OS upgrade, a new hard drive install, or any event that resets local user accounts. The account is recreated by QuickBooks installation but its permissions in the company file folder are not automatically restored — they must be set manually.
METHOD 6
Rename .ND File and Rescan
Clue: appeared after server migration or IP change
The .ND (Network Descriptor) file stores the network path QuickBooks uses to locate the company file. If the server's IP address changed, the server was renamed, or the company file was moved to a different folder — the .ND file contains a stale path and the communication error follows every time QuickBooks tries to connect.
1
Navigate to the folder containing the company file on the server. Find YourCompany.QBW.ND and YourCompany.QBW.TLG. Right-click each → Rename → add .OLD to the end.
2
Open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager. Click Start Scan on the company file folder. Fresh .ND and .TLG files are created with the correct current network paths.
3
Restart QuickBooks on the server and all workstations. Test multi-user access.
Quick Reference — Match Your Clue to the Fix
| Your clue / situation |
Most likely cause |
Go to |
| No clear clue — start here |
Unknown — let the tool diagnose |
Method 1 — File Doctor |
| All workstations affected simultaneously |
Hosting misconfiguration |
Method 2 — fix hosting |
| Appeared after server reboot or Monday morning |
QB services stopped |
Method 3 — restart services |
| Appeared after new antivirus or Windows update |
Firewall blocking ports |
Method 4 — firewall exceptions |
| Only certain users affected — not all workstations |
Folder permissions |
Method 5 — QBDataServiceUser |
| Appeared after server migration, rename, or file move |
Stale .ND file |
Method 6 — rename .ND |
Frequently Asked Questions
The error message says "due to a firewall" — does that mean the firewall is definitely the cause?
No. Intuit includes "due to a firewall" in the error message as a common possibility, but this wording has misled many users into spending hours on firewall settings when the real cause was a stopped service, a hosting misconfiguration, or a permissions issue. Use the clue-matching framework at the top of this page first. If the error appeared after a Windows update and disappeared when you temporarily turned off the firewall — then yes, the firewall is the cause. If not, check the other causes before touching firewall settings.
How is this error different from H202 or H505?
H202, H303, and H505 are more specific sub-codes within the same family of errors. The "Cannot communicate with the company file" message is the umbrella error that QuickBooks shows when it cannot determine which specific H-series sub-code applies — or when the failure happens at a layer below the H-series detection logic. In practice, if you see a specific H-code, go to that specific page. If you see the generic "cannot communicate" message without an H-code, use this page's clue-matching framework to diagnose the cause.
Is my company file at risk when this error appears?
No. The "Cannot communicate" error is a network access failure — QuickBooks cannot reach the company file over the network, but the file itself on the server is completely unaffected. It is the same as being unable to open a website: the website's files are intact, you just cannot connect to it. No data is corrupted, lost, or altered by this error. The company file is accessible directly on the server while the workstation connection issue is being resolved.
How do I prevent this error from recurring?
Five practices eliminate most recurring occurrences. Set QuickBooks services (QuickBooksDBXX and QBCFMonitorService) to Automatic startup so they survive server reboots. Ensure only the server has hosting enabled — verify this every time a new workstation is added to the network. Assign the server a static IP so that the .ND file's network path remains valid after any server restart. Add permanent QuickBooks firewall exceptions rather than temporarily disabling the firewall. And maintain the QBDataServiceUser's Full Control permissions on the company file folder. At QuickFix Bookkeeping we configure all five of these as standard during any new QuickBooks multi-user network setup.
Related QuickBooks Multi-User and Network Errors
Team Can't Access QuickBooks?
Company File Unreachable.
Let's Restore Access Today.
Certified Intuit ProAdvisors · QuickBooks Network Specialists
When the "cannot communicate" error persists after running through the methods above, it almost always indicates a layered network configuration issue — firewall rules interacting with permissions, or a domain policy overriding local settings. At QuickFix Bookkeeping, our certified ProAdvisors diagnose multi-user access errors remotely and get your team back into QuickBooks in a single session.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Company file accessible today.
