How to Fix QuickBooks Error H202

QuickBooks Error H202 is a multi-user connectivity error that blocks workstations from opening a shared company file stored on another computer. It appears immediately when you attempt to switch to multi-user mode and signals that the current machine cannot establish a connection to the host computer running the QuickBooks Database Server Manager. This guide covers all fixes verified on QuickBooks Desktop 2022 through 2026 on Windows 10 and Windows 11. Note: Error H202 affects QuickBooks Desktop on Windows only; it does not apply to QuickBooks Online or Mac versions.

What Is QuickBooks Error H202?

QuickBooks Error H202 belongs to the H-series of multi-user errors, a group that also includes H101, H303, and H505. These errors all relate to failures in the multi-user network connection between workstations and the host computer that stores the shared company file.

H202 specifically means the workstation has located the host computer on the network but the connection request was refused or dropped. This is different from H101, where the workstation cannot find the host at all. When H202 appears, QuickBooks typically displays a message similar to:

"You need to use multi-user mode to access this company file. Make sure QuickBooks is installed on the server."

The error surfaces when switching to multi-user mode because that is the moment QuickBooks attempts to hand off file access to the Database Server Manager service on the host. If the firewall is blocking the required ports, if the QuickBooks services have stopped, or if the network descriptor file is outdated, the handshake fails and H202 appears.

Symptoms

You may be dealing with Error H202 if you notice:

• The error message appears immediately when switching from single-user to multi-user mode
• You cannot open the company file from a workstation even though the host computer opens it fine
• QuickBooks freezes or crashes on the workstation when trying to connect to the network company file
• The error appears on one or more workstations but the host computer operates normally
• Switching back to single-user mode on the workstation clears the error temporarily
• The problem started or worsened after a Windows Update or changes to firewall settings

Root Causes

1. Firewall Blocking QuickBooks Ports

Windows Firewall or a third-party security program may be blocking the ports QuickBooks uses for multi-user communication. QuickBooks requires ports 8019, 56728, and the range 55378-55382 to be open for inbound and outbound traffic. This is the most common cause of H202 specifically, because the workstation can reach the host but the connection is refused at the port level.

2. QBCFMonitorService or QuickBooksDBXX Not Running

Two Windows services must be active on the host computer at all times. QuickBooksDBXX (where XX corresponds to your version year) manages the multi-user database connections, and QBCFMonitorService monitors file access across the network. If either service has stopped, for example after a Windows Update or system restart, H202 appears on every workstation attempting to connect.

3. Corrupted or Missing .ND File

QuickBooks stores a Network Descriptor (.ND) file alongside the company file. This file tells QuickBooks where to find the host computer on the network. If the .ND file is corrupted, missing, or references an outdated IP address, workstations cannot establish a connection even when all services are running.

4. Incorrect Hosting Configuration

Multi-user mode requires that hosting is enabled only on the server (the host machine holding the company file) and disabled on all workstations. If a workstation accidentally has hosting enabled, it creates a network conflict that can trigger H202 or other H-series errors.

5. Unresolvable Host Computer Name or IP Change

If the host computer's IP address changed (common on networks that use DHCP instead of static IPs) and the .ND file or Windows hosts file still references the old address, workstations cannot locate the server correctly. DNS lookup failures produce the same result.

Before You Begin

• Confirm which computer is the host (the one where the company file is stored and where QuickBooks Database Server Manager is installed)
• Ensure you have administrator privileges on the host computer before starting
• Note your QuickBooks Desktop version year (2022, 2023, 2024, 2025, or 2026), as service names include the version number
• Back up the company file before making any system-level changes
• This guide applies to Windows 10 and Windows 11 only; QuickBooks Desktop is not supported on macOS for multi-user hosting
• Apply all fixes on the host computer first, then test from each workstation

Step-by-Step Fix

Work through these methods in order. Most H202 cases are resolved by Method 1 or Method 2.

Method 1: Run QuickBooks Database Server Manager (Tool Hub)

The QuickBooks Tool Hub's Database Server Manager rescans your company file, regenerates the .ND file, and refreshes firewall permissions in a single pass. This is the fastest and most effective starting point for H202.

1. Download the latest QuickBooks Tool Hub from the official Intuit support page
2. Run the installer (QuickBooksToolHub.exe) and follow the on-screen prompts
3. Accept the license agreement and complete the installation
4. Open QuickBooks Tool Hub from the Windows desktop icon
5. Click Network Issues in the left panel
6. Click QuickBooks Database Server Manager
7. Click Browse and navigate to the folder that contains your company file (.qbw)
8. Click Start Scan
9. Wait for the scan to complete. It will automatically repair the .ND file and update firewall rules
10. Click Close when the scan finishes
11. Open QuickBooks on each affected workstation and switch to multi-user mode to test

If the error clears after this step, you are done. If H202 persists, continue to Method 2.

Method 2: Verify QuickBooks Services Are Running

These steps must be performed on the host computer.

1. Press Windows + R, type `services.msc`, and press Enter
2. In the Services window, scroll to find QuickBooksDBXX using this version mapping:

- QuickBooksDB36 = QuickBooks 2026

- QuickBooksDB35 = QuickBooks 2025

- QuickBooksDB34 = QuickBooks 2024

- QuickBooksDB33 = QuickBooks 2023

- QuickBooksDB32 = QuickBooks 2022

1. Right-click it and select Properties
2. Set Startup type to Automatic
3. If the service status is not Running, click Start
4. Click the Recovery tab, set First failure to Restart the Service, then click OK
5. Repeat steps 2 through 6 for QBCFMonitorService
6. Close the Services window and test multi-user access from a workstation

If QuickBooksDBXX does not appear in the list, the Database Server Manager is not installed. Return to Method 1 and complete the Tool Hub installation on the host computer.

Method 3: Open QuickBooks Firewall Ports Manually

If Methods 1 and 2 did not resolve H202, a firewall rule is likely blocking the ports QuickBooks requires.

Add QuickBooks programs as firewall exceptions:

1. Open Control Panel > System and Security > Windows Defender Firewall
2. Click Allow an app or feature through Windows Defender Firewall
3. Click Change Settings (requires administrator privileges)
4. Click Allow another app
5. Browse to and add each of the following: `QBDBMgrN.exe`, `QBW32.exe`, and `QBCFMonitorService.exe`
6. Check both Private and Public for each program
7. Click OK

Add specific port rules for QuickBooks multi-user traffic:

1. In Windows Defender Firewall, click Advanced settings
2. Right-click Inbound Rules and choose New Rule
3. Select Port and click Next
4. Select TCP, enter `8019, 56728, 55378-55382`, and click Next
5. Select Allow the connection and click Next
6. Apply to all profiles (Domain, Private, Public) and click Next
7. Name the rule "QuickBooks Multi-User Ports" and click Finish
8. Repeat steps 2 through 7 for Outbound Rules
9. Test multi-user access from a workstation

Method 4: Correct the Hosting Configuration

Hosting must be enabled on the server only and disabled on all workstations.

On each workstation:

1. Open QuickBooks Desktop
2. Go to File > Utilities
3. If you see "Stop Hosting Multi-User Access", click it to turn hosting off on this workstation
4. If you see "Host Multi-User Access", hosting is already off; no change needed
5. Repeat on every workstation connected to the company file

On the host/server computer:

1. Open QuickBooks Desktop
2. Go to File > Utilities
3. If you see "Host Multi-User Access", click it to enable hosting
4. If you see "Stop Hosting Multi-User Access", hosting is already enabled; no change needed

After correcting hosting settings on all machines, test multi-user access. If H202 persists, continue to Method 5.

Method 5: Edit the Windows Hosts File

If the host computer's IP address has changed, workstations may not be able to resolve the server name correctly. Manually editing the Windows hosts file forces the correct IP mapping.

Step 1 - Get the host computer's IP address and name:

1. On the host computer, press Windows + R, type `cmd`, and press Enter
2. Type `ipconfig /all` and press Enter
3. Note the IPv4 Address under your active network adapter
4. Also note the Host Name at the top of the output

Step 2 - Edit the hosts file on each affected workstation:

1. Close QuickBooks on the workstation
2. Navigate to `C:\Windows\System32\Drivers\etc\`
3. Right-click the `hosts` file and open it with Notepad (run as administrator)
4. Add a new line at the bottom: `[host-IP-address] [host-computer-name]`
5. Save the file and close Notepad
6. Repeat on all affected workstations, then test multi-user mode

Method 6: Recreate the .ND File Manually

If the Tool Hub scan in Method 1 did not fully repair the .ND file, you can delete it manually and force QuickBooks to rebuild it.

1. On the host computer, open Windows File Explorer and navigate to the folder containing your company file (.qbw)
2. Look for a file with the same name as your company file but with the extension `.nd` (for example, `CompanyName.qbw.nd`)
3. Right-click the .nd file and select Delete (this is safe; QuickBooks will recreate it)
4. Open QuickBooks Tool Hub, click Network Issues, then click QuickBooks Database Server Manager
5. Click Browse, select the folder containing your company file, and click Start Scan
6. QuickBooks will create a fresh .nd file during the scan
7. Open QuickBooks on a workstation and test multi-user mode

H-Series Error Comparison

H202 is one of four H-series errors in QuickBooks Desktop. Use this table to confirm you are working on the right error code.

The fix steps for all four errors overlap significantly. If the error code changes after applying a fix, that indicates partial progress and points to a new specific cause to address next.

When to Call Support

Contact support directly if:

• Error H202 persists after completing all six methods above
• You see additional error codes alongside H202 (such as 6000-series errors), which point to database corruption rather than a network issue
• The error appears immediately after a QuickBooks version upgrade, which may indicate a compatibility issue between the new version and your current firewall configuration
• Your QuickBooks Desktop version is more than three years old and may have compatibility issues with current Windows updates

You can reach Intuit through the QuickBooks support phone number or through the Help menu inside QuickBooks Desktop.

Prevention Tips

• Assign a static IP address to the host computer so the .ND file never becomes outdated when DHCP reassigns addresses
• Keep QuickBooks updated. Intuit releases patches that include updated firewall rules; apply them promptly via Help > Update QuickBooks Desktop
• Check services monthly. Open `services.msc` on the host once a month to confirm QuickBooksDBXX and QBCFMonitorService are set to Automatic startup and are actively running
• Train team members not to enable "Host Multi-User Access" on their individual workstations; hosting belongs only on the server
• Run the Tool Hub Network Scan quarterly to refresh .ND files and firewall permissions before errors surface
• Back up the company file daily using the built-in QuickBooks backup tool so that any troubleshooting steps carry no data risk