QuickBooks Error H202: How to Fix the Multi-User Connection Error

If you're trying to open your company file in multi-user mode and got stopped cold, you're probably looking at this:

Error H202: This company file is on another computer, and QuickBooks needs some help connecting.

The file opens fine on the server. It just won't open from a workstation. That's the whole signature of H202: QuickBooks can reach the file locally but can't make the network jump to multi-user mode. Here's how to fix it.

What Causes Error H202

H202 is a connection error, not a file-corruption error. When you open a company file in multi-user mode, the workstation has to talk to the QuickBooks Database Server Manager on the machine that hosts the file. If that conversation fails, you get H202.

The usual culprits:

• The QuickBooks Database Server Manager service (QBDBMgrN) isn't running on the server
• A firewall or antivirus is blocking the ports QuickBooks uses
• Hosting is misconfigured — turned on in more than one place, or off on the server
• The workstation can't resolve the server's name or IP
• The .ND configuration file for your company file is damaged

Work through the fixes below in order. The first two resolve the large majority of H202 cases.

Fix 1: Run QuickBooks Database Server Manager on the Server (Works in Most Cases)

The server needs to be actively scanning the folder that holds your company file. If it isn't, no workstation can connect.

Do this on the server (the machine that stores the .QBW file):

1. Download the QuickBooks Tool Hub from Intuit's support page and install it on the server
2. Open Tool Hub and click Network Issues
3. Select QuickBooks Database Server Manager
4. Click Start Scan (if your company file's folder isn't listed, click Browse, add it, then scan)
5. When the scan finishes, click Close

The scan registers your company file folder with the database service so workstations can find it. Now go back to a workstation and try opening the file in multi-user mode.

If the Tool Hub flags your firewall during the scan, let it configure the firewall automatically — that handles most of Fix 3 for you.

Fix 2: Restart the QBDBMgrN Service (Quick Win)

If Database Server Manager is installed but the service stalled, restarting it often clears H202 immediately.

On the server:

1. Press Windows + R, type services.msc, and press Enter
2. Scroll to the service named:

   QuickBooksDBXX
   

   The XX is your version year — for example QuickBooksDB33 for QuickBooks 2023. The underlying process is QBDBMgrN.exe.

3. Right-click it and choose Restart
4. Make sure Startup type is set to Automatic

Then try multi-user mode from the workstation again.

Fix 3: Open the Firewall Ports QuickBooks Needs

If the service is running but workstations still can't connect, a firewall is almost certainly in the way.

The cleanest approach:

1. On the server, open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager
2. The tool can detect and add the required firewall exceptions automatically — let it

If you need to add the ports manually in Windows Defender Firewall → Advanced Settings → Inbound Rules, QuickBooks Desktop uses these port ranges by version year:

QuickBooks 2020 and newer:  8019, 56728, 55378-55382
QuickBooks 2019:            8019, XXXXX (dynamic), 56727, 55373-55377

Newer versions use dynamic ports. The reliable fix is to let Database Server Manager configure the firewall rather than guessing port numbers.

Add the same exceptions to any third-party antivirus or security suite — those often have their own firewall that Windows settings don't cover.

Fix 4: Set Hosting Correctly (Server On, Workstations Off)

Multi-user mode only works when exactly one machine hosts the file: the server. If hosting is turned on at a workstation too, the machines fight over the file and you get H202.

Check this on every machine. In QuickBooks:

1. Go to File → Utilities
2. Look at the hosting option:
   • On the server: you should see Stop Hosting Multi-User Access (meaning hosting is ON — leave it)
   • On each workstation: you should see Host Multi-User Access (meaning hosting is OFF — leave it). If a workstation instead shows Stop Hosting, click it to turn hosting off.

Rule of thumb: hosting on at the server, off everywhere else. Restart QuickBooks on each machine after changing this.

Fix 5: Make Sure the Workstation Can Reach the Server

If everything above checks out, the workstation may simply not be able to find the server by name.

On the workstation:

1. Press Windows + R, type cmd, and press Enter
2. Ping the server by name:

   ping SERVERNAME
   

3. If the ping times out, ping by IP address instead. If the IP works but the name doesn't, it's a name-resolution problem.

A quick reliable fix is to map the server's name to its IP in the hosts file. Open this file as administrator in Notepad:

C:\Windows\System32\drivers\etc\hosts

Add a line with the server's IP and name, save, and try multi-user mode again. Confirm both machines are on the same network and the server isn't asleep or off.

Fix 6: Recreate the .ND File

Each company file has a .ND (Network Data) file that tells QuickBooks how to reach it over the network. If it's damaged, multi-user connections fail.

The safest way to rebuild it is with File Doctor:

1. Open QuickBooks Tool Hub → Company File Issues
2. Click Run QuickBooks File Doctor (it can take a few minutes to load)
3. Choose your company file from the list (or Browse to it)
4. Select Check your file and network and click Continue
5. Enter your QuickBooks admin password and let it run

File Doctor repairs network configuration and regenerates the .ND file. If you'd rather do it manually, you can rename the .ND file (add .OLD to the end) while QuickBooks is closed, then reopen — QuickBooks recreates it. You won't lose company data; the .ND file only holds network pointers.

Still Stuck?

A few less common things worth checking:

• The file is on a NAS or external drive: Some network-attached storage devices don't run Database Server Manager well. QuickBooks officially supports hosting on a Windows machine. If your file lives on a NAS, that may be the real problem.
• Different QuickBooks versions across machines: All workstations and the server should run the same year and edition of QuickBooks. A 2022 workstation can't reliably join a 2023 server.
• Server went to sleep: If the host machine sleeps or hibernates, workstations lose the connection. Set the server to never sleep.

If you've worked through every fix and H202 persists, it's usually a deeper network or domain configuration issue. That's a reasonable point to bring in Intuit support or a local IT specialist who can look at your network directly.

One Alternative Worth Knowing About

If you're a solo founder and the only reason you're running QuickBooks in multi-user mode is that it's what you set up years ago — and errors like H202 keep eating your afternoons — it's worth knowing that the whole server-and-workstation model is optional.

Prosper is what I built for that situation: a web app, so there's no server to host, no ports to open, no .ND files, and no H202. It's $29/month, exception-based accounting for founders who don't want to become accountants — it auto-categorizes most of your transactions and only surfaces the ones that need a decision.

That said — if QuickBooks works for your setup and you just needed multi-user mode back, the steps above should get you connected.

Not professional tax or accounting advice. Consult a CPA for your situation.