Quick answer

QuickBooks error H202 means a workstation cannot reach the company file on the host computer. The usual causes are hosting turned off on the server, QuickBooks database services stopped, firewall rules blocking the connection, or a stale .ND network file. On the host PC, rescan the company-file folder with QuickBooks Database Server Manager, restart the QuickBooksDBXX and QBCFMonitorService services, and confirm only the server hosts multi-user access.

What QuickBooks error H202 means

H202 is a multi-user hosting error, not a data-damage error. The dialog carries the title Problem with multi-user hosting setup and reads: "Error code: H202. This company file is on another computer, and QuickBooks needs some help connecting." The Tell Me More button opens Intuit's troubleshooting article.

The host can still open the company file; the failure happens when a workstation selects File → Switch to Multi-user Mode and QuickBooks cannot complete the database connection. The network path to the file — not the file itself — is what broke. On Linux or Citrix hosting, H202 reads "QuickBooks could not open the file in multi-user mode. (H202)" instead, with different causes.

H202 belongs to a family of hosting errors. Error H505, H101 and H303 mean hosting is switched on somewhere it should not be; H202 means the connection itself is blocked. Intuit documents the family together because the fixes overlap.

What you seeWhat it usually meansStart with
H202 on one or two workstationsFirewall, service or name-resolution problem on those machinesSteps 2–6
H202 on every workstation after the server rebootsQuickBooksDBXX did not restart, or hosting is offSteps 1 and 3
H202 only after the file was moved or copiedStale .ND file or wrong folder permissionsSteps 7 and 8

Symptoms that come with H202

  • Workstations see the Problem with multi-user hosting setup dialog the moment they switch to multi-user mode, while the host PC opens the file normally.
  • The error often starts after a Windows update, server reboot, router change, or antivirus rollout that resets firewall or service settings.
  • Every workstation fails at once when the host is off, asleep, or has a new IP address.
  • One workstation may enter multi-user mode while others fail, pointing at that machine, not the file.

Common causes, ranked by how often we see them

  1. Multi-user hosting is off on the server, or on at a workstation. The computer that stores the file must be the only one hosting; a workstation that grabs hosting blocks everyone else.
  2. QuickBooks database services are stopped. QuickBooksDBXX and QBCFMonitorService must run on the server even when QuickBooks Desktop is closed.
  3. Firewall rules are missing or reset. Windows Defender Firewall and third-party tools block port 8019 plus a dynamic port on QuickBooks Desktop 2019 and later.
  4. Database Server Manager has not scanned the folder, so firewall permissions and the .ND file are not refreshed.
  5. The .ND file is stale or damaged. It remembers an old server name, path, or port after the file moves.
  6. Name resolution fails. Workstations cannot turn the server name into an IP address after a router or DNS change.
  7. Folder permissions changed. QBDataServiceUserXX or network users lost Full control on the company-file folder.
  8. The file sits on unsupported storage. Database Server Manager does not support NAS devices, and sync folders cause locks.

Back up first. Copy the entire company-file folder to another drive before you change services, permissions, or network files. Support files can be recreated; a current .QBW backup is your safety net.

Before you begin

  • Work on the server that stores the company file; most H202 fixes cannot be applied from a workstation.
  • Sign in with local administrator rights, and know the QuickBooks admin password for File Doctor.
  • Press F2 to confirm your version. QuickBooksDBXX uses your version plus 10 — QuickBooks Desktop 2023 uses QuickBooksDB33.
  • Plan 10 minutes if hosting or a service is the problem, and 30–60 minutes for firewall and name-resolution checks. See the multi-user network topic hub for related articles.

How to fix QuickBooks error H202

1

Confirm which computer should host the file

On the server, open QuickBooks and go to File → Utilities. If Host Multi-User Access appears, select it. If Stop Hosting Multi-User Access appears, leave it alone — the server is already hosting. On every workstation, do the opposite: open QuickBooks without a company file, go to File → Utilities, and select Stop Hosting Multi-User Access if it appears. This check resolves many cases that begin after QuickBooks is installed on a new PC; the hosting mode guide explains the options.

2

Rescan the company-file folder with Database Server Manager

Install the latest QuickBooks Tool Hub on the server, open it, select Network Issues, then QuickBooks Database Server Manager. If your company-file folder is listed, select Start Scan; if not, select Browse, point the tool at the folder, then start the scan. The scan repairs firewall permissions automatically and rebuilds the network data file in one to three minutes for a normal folder. Select Close, test multi-user mode from a workstation, and re-scan after any file move or rename.

3

Check the two QuickBooks services on the server

Open the Run box with Windows + R, type services.msc, and press Enter. Find QuickBooksDBXX and double-click it. Set Startup type to Automatic, confirm Service status is Running, then open the Recovery tab and set Restart the Service for first, second, and subsequent failures. Select Apply and OK, then repeat for QBCFMonitorService. If they are set to Manual, H202 returns after every reboot.

4

Run File Doctor's network check

In Tool Hub, select Company File Issues, then Run QuickBooks File Doctor. Select your company file, choose Check your Network (the top option), select Continue, and enter the QuickBooks admin password. The scan usually finishes within five minutes and catches a damaged .ND file and a broken firewall rule in one pass. It sometimes reports "unsuccessful" even when it repaired the connection, so test multi-user mode afterward.

5

Verify the firewall exceptions and the dynamic port

Open QuickBooks Database Server Manager and select the Port Monitor tab. Note the Port Number for your version: QuickBooks Desktop 2019 and later use port 8019 plus a dynamic port assigned at installation, while 2018 and 2017 use fixed ranges with port 8019. In Windows Firewall → Advanced Settings, confirm inbound and outbound TCP rules allow those ports on the server. If you select Renew to change the port, return to Scan Folders and select Scan Now so the rules and .ND file reset. Our firewall and ports guide has the full walkthrough.

6

Test the server name from each workstation

On the server, run ipconfig /all and note the Host Name. On a failing workstation, open Command Prompt and ping that name — for example, ping QB-SERVER. A clean reply means the network path is healthy. If the name fails but the server's IP address replies, the workstation cannot resolve the name; that is a network administrator task. Turn on Network Discovery and File and printer sharing on the server and each failing workstation.

7

Restore folder and Windows permissions

On the server, right-click the folder that contains the company file and open Properties → Security → Edit. Give QBDataServiceUserXX (for example, QBDataServiceUser33 for the 2023 version) Full control. On the Sharing tab, share the folder and give the same account Full control over the network. If workstations use a mapped drive letter, switch to the UNC path, such as \\Server\Share\CompanyFile.qbw, so a reassigned letter cannot break the connection.

8

Refresh the .ND network file

Close every QuickBooks window on the server, then open the folder that holds the company file. Find every support file with the same base name as your company file and the extensions .ND, .TLG and .DSN — for example company.qbw.nd — and rename each by adding .old. These files carry connection and transaction-log information, and QuickBooks recreates them. Reopen QuickBooks on the server, open the company file, then run another Database Server Manager scan so the network file is rebuilt before workstations reconnect.

Verify the fix

  1. Open the company file on the server first and switch to multi-user mode.
  2. On each workstation, open the file and switch to multi-user mode, then press F2 to confirm the file and hosting status.
  3. Post a test invoice or journal entry from one workstation, refresh it on another, then delete it.
  4. Leave a workstation connected for 15 minutes; connections that drop when idle point to sleep or Wi-Fi power settings on the server.
  5. Reboot the server once and repeat, because a fix that does not survive a restart is not finished.

If H202 keeps coming back

A recurring H202 after every reboot almost always means a service startup type, firewall rule, or dynamic port changed. Set the server to never sleep and give it a static or reserved IP address. If pings show packet loss, involve a network administrator — no QuickBooks setting fixes a failing switch, cable, or Wi-Fi link.

On Linux or Citrix hosting, H202 has its own causes, including a server set to its fully qualified domain name and client-side application virtualization; Intuit documents them in its H202 non-Windows Server article. If the file sits on a NAS or sync folder, move it to supported storage. Escalate to Intuit support or a qualified technician when the server cannot host the file, when services refuse to start, or when pings reveal a network fault.

Prevention

  • Install Database Server Manager on the server for every QuickBooks Desktop version in use, and scan folders after moving or renaming a company file.
  • Set QuickBooksDBXX and QBCFMonitorService to Automatic with restart-on-failure recovery.
  • Keep multi-user hosting on the server only, and recheck hosting after installing QuickBooks on a new computer.
  • Give the server a reserved IP, turn off sleep, and use wired Ethernet where possible.
  • Test multi-user mode from two workstations after every QuickBooks update, Windows update, or security software change.

Frequently asked questions

What is the difference between error H202 and error H505?

H505, H101 and H303 usually mean a workstation is hosting multi-user access when it should not be. H202 means the connection to the server is blocked — by a firewall, a stopped service, name resolution, or a stale .ND file. Check hosting first, then work through the connection fixes in order.

Does renaming the .ND file delete my company data?

No. Transactions live in the .QBW file. The .ND, .TLG and .DSN files only describe how QuickBooks connects and logs activity, and QuickBooks recreates them the next time the file is opened or scanned.

Why does H202 appear on only one workstation?

That points at that machine: a firewall rule, a stale mapped drive, or name resolution. Ping the server by name and by IP; if the IP replies but the name does not, fix resolution instead of touching the server.

Can I just turn off Windows Firewall to test?

You can briefly disable the firewall to confirm it is the blocker, but turn it back on immediately and create proper port rules instead. Third-party suites keep their own rules even when Windows Firewall is off.

Does QuickBooks Online ever show H202?

No. H202 is a QuickBooks Desktop multi-user hosting error. QuickBooks Online has no company file to host and no Database Server Manager, so a "multi-user" problem there is a user permissions or login issue. QuickBooks Desktop for Mac uses the QuickBooks Server app instead, so these Windows steps do not apply.

Sources & further reading