QuickBooks Error H606: Multi-User Mode Cannot Reach the Host

Last reviewed 2026-09-01 5 min read

When QuickBooks Desktop reports H606, the workstation cannot reach the file host. This page explains the cause and the repair steps to restore multi-user access.

QuickBooks error H606 blocks a workstation from opening a company file in multi-user mode. The file usually opens without issue on the host computer, but any computer that tries to reach it across the network is refused. Our engineers trace most H606 cases to the QuickBooks Database Server Manager service on the host. The repair belongs on the host, not on the workstation that shows the error.

The error message on screen

The exact dialog text varies slightly by QuickBooks year and edition. The most common H606 message reads:

QuickBooks is unable to open this company file because it is located on another computer and QuickBooks is not running on that computer.

Some releases append Error code: H606 under the same text. The wording can mention that the file is on another computer or that QuickBooks could not switch to multi-user mode.

The meaning of H606

H606 is an H-series connection error. In multi-user mode, the workstation sends a request to the computer that stores the .QBW company file. The request is handled by a Windows service named QuickBooksDBXX. The XX at the end matches the QuickBooks version year. H606 means the workstation reached the network but received no usable response from that service.

The company file is usually not damaged. The error describes a failed service connection, not a failed data file. That is why the file often opens in single-user mode on the host while other computers receive H606.

Common H606 triggers

The most common trigger is a stopped QuickBooksDBXX service on the host. The service can stop after a server reboot, an update, or a crash.

Other triggers include:

Hosting mode is switched off on the computer that stores the company file.
A firewall on the host blocks the QuickBooks database service.
The .ND file in the company file folder is missing, stale, or points to an old server name or IP address.
The workstation cannot resolve the host computer name on the network.
Windows share or NTFS permissions prevent QuickBooks from creating its working files in the folder.
The workstations are not on the same QuickBooks version and release as the host.

Repair steps for QuickBooks error H606

Work through these scenarios in order. Our engineers see the first scenario most often in H606 cases. Stop when a workstation can open the file in multi-user mode.

Scenario 1: The QuickBooks database service is stopped

Go to the computer that physically stores the company file.
Open Windows Services by typing services.msc in the Start menu.
Find the service named QuickBooksDBXX.
If the service is stopped, right-click it and choose Start.
If it is already running, right-click it and choose Restart.
Set the Startup type to Automatic so the service starts after a reboot.
Try the file again from a workstation in Multi-user Mode.

If the service is missing, repair the QuickBooks installation on the host or reinstall the QuickBooks Database Server Manager component from the QuickBooks install media.

Scenario 2: Hosting is switched off on the host

On the host computer, open QuickBooks Desktop without opening a company file.
Choose File, then Utilities.
If the menu shows Host Multi-User Access, select it.
If the menu shows Stop Hosting Multi-User Access, hosting is already enabled and you can leave it as is.
Test the file from the workstation.

Scenario 3: The file folder has not been scanned, or the scan is stale

On the host, open QuickBooks Database Server Manager.
Select Scan Folders.
Add the folder that contains the company file. Remove any old or duplicate folder entries.
Run the scan and wait for it to finish.
Browse to the company file folder and confirm a .ND file exists next to the .QBW file.
Test the file again in multi-user mode.

Scenario 4: A firewall is blocking the QuickBooks service

On the host, open Windows Defender Firewall.
Confirm the network profile is set to Private, not Public. A Public profile blocks the service by default.
Add an inbound rule and an outbound rule for the QuickBooksDBXX executable.
If a third-party security product is installed, add the same executable and the company file folder to its allow list.
Restart the QuickBooksDBXX service and test the connection.

Scenario 5: The .ND file points to the wrong server

On the host, browse to the folder that contains the company file.
Open the matching .ND file in Notepad.
Check the first line. It should be the current host computer name or a current IP address.
If the line shows an old server name or an old address, stop the QuickBooksDBXX service, delete the .ND file, restart the service, and scan the folder again.
Test the file from the workstation.

Scenario 6: Windows permissions or name resolution are failing

On the workstation, open a Command Prompt and ping the host by its computer name.
If the ping fails, the workstation is using a stale DNS or hosts entry. Correct the network path and test again.
When you open the file in QuickBooks, use the UNC path instead of a mapped drive letter. A mapped drive can keep pointing at an old server.
On the host, make sure the folder's Windows share permissions and NTFS permissions give the QuickBooks user Modify or Full Control access.
Restart the QuickBooksDBXX service and test the file once more.

Preventing H606 from returning

Choose one host computer for the company file and leave it on during work hours. Set the QuickBooksDBXX service to Automatic, and use the Recovery tab in Windows Services to restart the service after a failure.

Keep the company file folder in the Database Server Manager scan list. Rescan the folder after moving the file or after a server rename. Use the same QuickBooks version and release on the host and all workstations.

Finally, open the company file from a UNC path rather than a mapped drive. That habit removes one common cause of stale server references and stops H606 from returning after a server change.