QuickBooks Multi-User Error Guide · H-Series
How to Fix QuickBooks Error H303
A workstation tried to open the company file in multi-user mode and received: "Error H303: This company file is on another computer, and QuickBooks needs some help connecting."
Error H303 is an H-series multi-user error. The message "this company file is on another computer" is diagnostic — the workstation knows where the file is but cannot reach it. At QuickFix Bookkeeping, that tells us immediately: start with hosting settings (a workstation is acting as a server), then move to the network data file and services if needed.
The QuickFix Bookkeeping Distinction
H303 is grouped with H101 and H505 by Intuit — they all have the same root cause. But H303 has a diagnostic detail the others do not: the workstation already knows where the file lives.
H202
Cannot find server
Workstation does not know where the file is. DNS/network problem.
H303
This page — can't reach it
Workstation knows where the file is — but cannot connect. Hosting or service issue.
H505
Server setup problem
Server was not set up correctly as a QB host from the start.
H101
Same family as H303
Another workstation has hosting enabled — same fix as H303.
The fix order for H303: (1) Check hosting — a workstation has hosting on. (2) Rename the .ND file and rescan. (3) Verify QB services are running on the server. (4) Add firewall exceptions. Work through in order — hosting misconfiguration resolves the majority of H303 cases in under 5 minutes.
What Is QuickBooks Error H303?
Error code
H303
H-Series · Multi-User Mode
Same family: H101 · H202 · H505
What it means
Error H303 means a workstation tried to open a company file stored on another computer (the server) in multi-user mode, but the connection failed. The workstation knows the file exists on the server — it is the connection itself that is blocked. The most common reason is that one or more workstations have multi-user hosting enabled when only the designated server should. The second most common reason is a stale or corrupted .ND (Network Descriptor) file that contains the wrong server address.
Your company file is safe. H303 is a connection error — the file on the server is completely intact and accessible from the server itself.
What Causes QuickBooks Error H303?
🖥️
Workstation Has Hosting Enabled
Primary cause — one or more workstations have "Host Multi-User Access" turned on. Only the server should host. When a workstation also hosts, it creates a network conflict that prevents other workstations from connecting to the server's version of the file.
📄
Stale or Corrupted .ND File
The .ND (Network Descriptor) file contains the server's address. If the server was renamed, its IP changed, or the company file was moved to a new folder, the .ND file points to an outdated location — causing H303 on every connection attempt from workstations.
⚙️
QB Services Not Running on Server
QBCFMonitorService and QuickBooksDBXX must be running on the server for workstations to connect. If these services were stopped (after a server reboot, Windows update, or antivirus action), H303 appears on all workstations.
🛡️
Firewall Blocking QB Ports
Windows Firewall or a third-party security product blocking the ports QuickBooks uses for multi-user communication (8019, 55373–55378) causes H303 on workstations. Most common after a new antivirus installation or a Windows update that resets firewall rules.
🔒
Folder Permissions Missing
The QBDataServiceUserXX account does not have Full Control over the folder containing the company file. The Database Manager cannot serve the file to workstations without these permissions — producing H303 even when the network and services are healthy.
🌐
DNS or IP Address Issue
QuickBooks uses the server's hostname to connect. If DNS cannot resolve the hostname to the correct IP, or if the server's IP has changed without a static IP assignment, workstations cannot reach the server and H303 appears.
How to Fix QuickBooks Error H303 — Step by Step
Start with Method 1 — hosting misconfiguration is the cause of the majority of H303 errors and is fixed in under 5 minutes.
METHOD 1
Fix Hosting — Turn Off on All Workstations, Confirm On at Server
Resolves majority of H303 cases — do this first
Only one machine on the network should have "Host Multi-User Access" active — the designated server. If any workstation also has it active, it creates a hosting conflict. This check must be performed on every computer on the network.
On each workstation (repeat on every workstation):
1
Open QuickBooks on the workstation — do not open the company file. Go to File → Utilities.
2
If you see "Stop Hosting Multi-User Access" — click it. This means the workstation had hosting enabled. If you see "Host Multi-User Access" — do nothing, this workstation is correctly configured.
On the server (the computer that stores the company file):
3
Open QuickBooks on the server. Go to File → Utilities. If you see "Stop Hosting Multi-User Access" — hosting is already on (correct). If you see "Host Multi-User Access" — click it to enable hosting.
4
Reset hosting on the server to clear any lingering state: go to File → Utilities → Stop Hosting Multi-User Access → Yes, then immediately File → Utilities → Host Multi-User Access → Yes. This resets the hosting service.
5
Test from a workstation: File → Open or Restore Company → Open a Company File and navigate to the server's company file. Then go to File → Switch to Multi-User Mode.
QuickFix tip: The most often-missed step is checking every workstation — not just the one showing H303. If any single workstation on the network has hosting enabled, it creates the conflict for all workstations, including ones that are not currently connected. Check each machine one by one before concluding the hosting check is complete.
METHOD 2
Rename the .ND File and Run Database Server Manager Scan
If server moved, renamed, or IP changed
The .ND file is a small configuration file that stores the network path QuickBooks uses to locate the company file. If it contains a stale path (old server name, old IP, old folder location), H303 fires on every workstation connection attempt. Renaming it and rescanning creates a fresh, accurate .ND file.
1
On the server, navigate to the folder containing the company file. Find YourCompanyFile.QBW.ND. Right-click → Rename → add .old to the end (e.g. YourCompanyFile.QBW.ND.old). The original is preserved as a backup.
2
Open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager. Click Start Scan on the folder containing the company file. The scan creates a fresh .ND file with the correct current server address and also configures firewall exceptions automatically.
3
Restart QuickBooks on the server and all workstations. Test multi-user access from a workstation.
METHOD 3
Verify and Restart QuickBooks Services on the Server
If H303 appeared after a server reboot
QuickBooks requires two Windows services running on the server to enable multi-user access: QuickBooksDBXX (the Database Manager) and QBCFMonitorService (the Company File Monitor). If either stopped — after a server restart, a Windows update, or antivirus action — H303 appears on all workstations.
1
On the server, press Windows + R → type services.msc → Enter. Find QuickBooksDB[XX] (XX = your version year) and QBCFMonitorService.
2
Right-click each service → Restart. If the status shows Stopped → right-click → Start. Then right-click each → Properties → Startup type → Automatic → Apply. This prevents recurrence after future reboots.
3
Test multi-user access from a workstation after both services are confirmed as running.
QuickFix tip: If QBCFMonitorService shows "Stopped" and clicking Start immediately stops it again — the service account (QBDataServiceUser) has lost permissions. Check that QBDataServiceUser is in the local Administrators group and has Full Control of the company file folder. This is the most common reason a service starts and immediately stops.
METHOD 4
Set Folder Permissions for QBDataServiceUser
If specific users or all workstations affected
The QuickBooks Database Manager runs under the QBDataServiceUser Windows account. That account must have Full Control over the folder containing the company file — without it, the Database Manager cannot serve the file to workstations and H303 results.
1
On the server, right-click the folder containing the company file → Properties → Security tab → Edit.
2
Look for QBDataServiceUser[XX] in the list (e.g. QBDataServiceUser24). If not present → click Add → type the account name → Check Names → OK. Set permissions to Full Control → Allow. Click Apply → OK.
3
Also confirm sharing is enabled: right-click the folder → Properties → Sharing tab → Advanced Sharing → check Share this folder → Permissions → Full Control for QBDataServiceUser. Click Apply → OK.
METHOD 5
Configure Firewall Exceptions for QuickBooks
After new antivirus or Windows update
If H303 appeared after a new security product was installed or Windows updated its firewall rules, the Database Server Manager scan (Method 2) should have created firewall exceptions automatically. If H303 persists, manual exceptions are needed.
1
Quick test: Temporarily disable Windows Firewall on the server and test multi-user access from a workstation. If H303 clears — the firewall is the cause. Re-enable and add permanent exceptions rather than leaving it disabled.
2
Add port exceptions: In Windows Defender Firewall → Advanced Settings → create Inbound and Outbound rules for TCP ports 8019 and 55373–55378.
3
Add program exceptions for QBW32.exe, QBDBMgrN.exe, and QBCFMonitorService.exe from the QuickBooks installation directory on both server and workstations.
METHOD 6
Test Network Connectivity with Ping
If all other methods pass but H303 persists
If hosting, .ND file, services, permissions, and firewall are all verified correct but H303 persists, the problem is at the network level — DNS cannot resolve the server name, or the IP is changing. A simple ping test confirms this in 60 seconds.
1
On a workstation showing H303, open Command Prompt. Type ping [servername] (use the actual name of your server computer). Press Enter.
2
If ping succeeds with 0% packet loss — the network path is clear and the H303 is caused by something else (return to Methods 1–5). If ping fails or shows packet loss — there is a DNS or network infrastructure issue that needs IT attention.
3
If DNS fails but IP ping succeeds: Open the Windows hosts file (C:\Windows\System32\drivers\etc\hosts) on each workstation and add a line mapping the server's hostname to its IP: 192.168.1.x SERVERNAME. This bypasses DNS entirely.
Quick Reference — Match Your Clue to the Fix
| Your clue / situation |
Most likely cause |
Start with |
| H303 on any workstation — no other clue |
Workstation has hosting on |
Method 1 — fix hosting settings |
| Server was renamed or IP changed recently |
Stale .ND file |
Method 2 — rename .ND, rescan |
| Appeared after server reboot or Monday morning |
QB services stopped |
Method 3 — restart services |
| Only specific users affected, not all workstations |
Folder permissions missing |
Method 4 — set QBDataServiceUser permissions |
| After new antivirus or Windows firewall update |
Firewall blocking QB ports |
Method 5 — firewall exceptions |
| All methods correct — still H303 |
DNS / network issue |
Method 6 — ping test + hosts file |
Frequently Asked Questions About Error H303
What is the difference between H303 and H202?
H202 means the workstation cannot determine where the company file is — it does not know the server exists or cannot resolve the server name at all. This is typically a DNS or network discovery problem. H303 means the workstation knows exactly which computer hosts the company file but cannot establish the connection — it knows where to go but cannot get there. H303 is typically a hosting configuration, .ND file, or services problem. Start with different fixes: H202 starts with network and DNS checks. H303 starts with hosting settings on all workstations.
Why do I need to check every workstation and not just the one showing H303?
A single workstation with hosting enabled causes H303 on all other workstations — not just itself. When a workstation has "Host Multi-User Access" turned on, it signals to the network that it is the host, creating a conflict with the actual server. Other workstations get confused about which host to connect to and fail with H303. The workstation that has hosting incorrectly enabled may not itself show the error — it may work fine while causing H303 for every other machine on the network. This is why checking every workstation is non-negotiable.
H303 comes back every Monday morning. Why?
The server is likely rebooting over the weekend (for Windows updates, scheduled maintenance, or overnight shutdowns) and the QuickBooks services — QBCFMonitorService and QuickBooksDBXX — are not set to start automatically. Every time the server reboots, the services stay stopped until manually started. The fix is Method 3: set both services to Automatic startup in Windows Services. That ensures they start with the server on every reboot, eliminating the Monday morning H303.
How do I prevent H303 from recurring?
Five practices prevent most H303 recurrences. Set both QuickBooks services to Automatic startup on the server — eliminating the post-reboot recurrence. Assign the server a static IP address so the .ND file's server reference never goes stale after a router DHCP lease renewal. Only install QuickBooks on the server to run as the host — never enable "Host Multi-User Access" on any workstation. Add permanent QuickBooks firewall exceptions on both server and workstations. Run the Database Server Manager scan after any server migration, folder move, or server rename to immediately refresh the .ND file.
Related QuickBooks Multi-User and H-Series Errors
Team Can't Access QuickBooks?
H303 Persisting After All Six Methods?
Let's Restore Multi-User Access Today.
Certified Intuit ProAdvisors · QuickBooks Network Specialists
A persistent H303 after hosting and .ND file fixes almost always points to a layered network issue — firewall rules interacting with service 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. Team back in QuickBooks today.
