QuickBooks Error 6123, 0: Troubleshooting Lost Connections to Company Files

November 7, 2026 7 min read

QuickBooks Error 6123, 0 triggers when QuickBooks Desktop loses communication with your company file during opening, upgrading, or restoring from a backup. The error dialog states: “Connection to the company file has been lost.” This failure stems from broken network handshakes, out-of-sync Network Data (.ND) files, firewall blocks, or domain security conflicts between your workstation and the host server. You can resolve Error 6123, 0 by running the QuickBooks File Doctor, restoring backups locally, or regenerating your network support files.

Fast-Fix: The 45-Second Solution

To resolve QuickBooks Error 6123, 0, rename your network support files and restart the database service. Open the folder containing your company file on the host machine, locate the files ending in .ND and .TLG, and rename them to .ND.old and .TLG.old. If this error occurs while restoring a backup (.QBB), copy the backup file directly to your local C:\ drive before restoring rather than restoring across a network share or USB drive.

Quick Status & Triage Snapshot

  • Data Risk Tier: Low. The error indicates an interrupted connection between the client software and the database manager. It does not mean your accounting records are corrupt.
  • Multi-User Impact: Can affect a single workstation if network settings or local permissions are corrupted, or all workstations if the host server’s database service dropped.
  • Common Triggers: Restoring a .QBB backup across an active network share, antivirus programs severing active database ports, domain controller authentication drops, or corrupt .ND files.
  • Estimated Fix Time: 10 to 20 minutes.

Technical Anatomy: Why the Handshake Breaks

When QuickBooks opens a company file over a local network, it relies on a multi-tiered communication process:

  1. The Network Request: The workstation client launches qbw32.exe and reads the companion Network Data (.ND) file to discover the host server’s IP address and database port.
  2. The Authentication Token: The workstation presents credentials to the QuickBooks Database Server Manager (qbdbmgrn.exe). If the workstation and server reside on a Windows Active Directory domain, the user’s domain security token must clear folder permissions on the server.
  3. The Database Attachment: The database service attaches the .QBW file to the engine and keeps an open communication channel through port 8019 and dynamic database ports.

Error 6123, 0 occurs when this connection breaks mid-stream. If an antivirus scanner terminates the network thread, if a firewall rejects the port handshake, or if you attempt to restore a backup across a network path where file locking is restricted, QuickBooks halts and displays the error.

Is Your Data at Risk?

Your financial ledgers are safe. Because Error 6123, 0 represents a communication drop rather than structural table corruption, your company file remains intact.

However, if this error appeared while updating your company file to a newer QuickBooks version, do not force-terminate the application during the conversion phase. Let the installer finalize or return an error code before closing the window, and always verify that you have a verified backup copy of your un-upgraded file before proceeding.

Diagnostic Flowchart: Error 6123, 0 Decision Path

Start: Error 6123, 0 appears
 │
 ├──> Did the error occur while restoring a backup (.QBB)?
 │     ├── YES ──> Move the .QBB to the local C:\ drive and restore it locally.
 │     └── NO  ──> Proceed to multi-user / network troubleshooting.
 │
 ├──> Does the error occur on all workstations or just one?
 │     ├── ONE WORKSTATION ──> Check workstation hosting settings & local firewall.
 │     └── ALL WORKSTATIONS ──> The host server database service or .ND file is failed.
 │
 ├──> Rename .ND and .TLG files on the server and rescan with Database Server Manager.
 │     ├── Resolved? ──> Complete.
 │     └── Persists? ──> Run QuickBooks File Doctor via the QuickBooks Tool Hub.
 │
 └──> If domain environment: Verify Windows user permissions and local admin rights.

Step-by-Step Repair Guide

Follow these steps in order, testing file access after each step.

Step 1: Isolate and Restore Backups Locally (If Restoring a .QBB)

If Error 6123, 0 occurs while restoring a backup, network latency or server security restrictions are interrupting the decompression process.

  1. Close QuickBooks Desktop on the workstation.
  2. Navigate to the network share, external hard drive, or flash drive where your .QBB backup file is stored. For flash drive issues, see External Drive Fix: Cannot Restore .QBB Files from USB or External Storage.
  3. Right-click the .QBB file and select Copy.
  4. Paste the file directly onto your local drive, such as C:\Users\Public\Documents\.
  5. Launch QuickBooks Desktop and go to File > Open or Restore Company.
  6. Select Restore a backup copy, click Next, and browse to the local .QBB file on your C:\ drive.
  7. Restore the company file to a local destination folder.
  8. Once restored and verified, you can safely move the resulting .QBW file back to your central network server share.

Step 2: Turn Off Hosting on All Client Workstations

A frequent cause of Error 6123, 0 is host conflicts—situations where a client workstation attempts to host the database instead of the dedicated server.

  1. Open QuickBooks Desktop on the workstation displaying the error.
  2. In the “No Company Open” window, click the File menu at the top left.
  3. Hover over Utilities.
  4. If you see the option Host Multi-User Access, do not click it. This confirms hosting is already turned off on this machine.
  5. If you see Stop Hosting Multi-User Access, click it immediately and confirm with Yes.
  6. Repeat this verification on every client workstation across your office. Only the dedicated server should have hosting enabled.

For detailed steps on auditing workstation configurations, refer to Multi-User Fix: How to Turn Off Hosting on All QuickBooks Workstations.

Step 3: Rename Damaged .ND and .TLG Support Files

Corrupted .ND (Network Data) files contain stale IP addresses or port tables that break the connection handshake.

  1. Access the computer or server where your company file is stored.
  2. Open Windows File Explorer and browse to the folder hosting your .QBW file.
  3. Locate the companion files sharing your exact company name:
    • CompanyFileName.qbw.nd
    • CompanyFileName.qbw.tlg
  4. Right-click CompanyFileName.qbw.nd and rename it to CompanyFileName.qbw.nd.old.
  5. Right-click CompanyFileName.qbw.tlg and rename it to CompanyFileName.qbw.tlg.old.
  6. Open the QuickBooks Database Server Manager on the server, go to the Scan Folders tab, and scan the folder to regenerate a clean .ND file.

To see step-by-step instructions for safely handling support files, see our guide on Manual Fix: Renaming .ND and .TLG Files to Resolve 6000-Series Errors.

Step 4: Run QuickBooks File Doctor

The automated File Doctor utility diagnoses and repairs broken Windows permissions, firewall port blocks, and network connection drops.

  1. Download and install the latest version of the QuickBooks Tool Hub.
  2. Launch the Tool Hub and select Company File Issues from the left-hand tabs.
  3. Click Run QuickBooks File Doctor.
  4. In the drop-down menu, select your company file (or browse to find it).
  5. Select Check your file and network, then click Continue.
  6. Enter your QuickBooks administrative password and proceed.
  7. Allow the tool to test and repair network handshakes (this process may take 5 to 15 minutes).

If the automated repair identifies complex internal issues, review our deep-dive on The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor.

Differential Diagnosis: Error 6123 vs. Error H202

  • Error 6123, 0 vs. QuickBooks Error H202: Troubleshooting Server Communication Failures: Error H202 occurs specifically when a workstation cannot resolve the server’s IP address or reach the Database Server Manager over the network. Error 6123, 0 occurs when an established session drops unexpectedly or during specific operations like file conversions and backup restorations.
  • Error 6123, 0 vs. File Path Length Limits: If Error 6123, 0 only occurs when restoring, ensure the target file path contains fewer than 210 characters and contains no non-standard symbols (, ?, <, >, |).

Hard Stop: Windows Domain Controller and User Rights

If Error 6123, 0 persists despite running File Doctor and resetting .ND files, inspect your network domain settings. If your server is a Windows Domain Controller, QuickBooks services may drop authentication tokens when authenticating non-domain local accounts.

Log in to both the server and workstation using a Windows Domain Administrator profile. If the file opens without error under the administrator profile, your standard Windows user account lacks the necessary folder read/write/modify permissions or security group policies on the server’s shared folder.

QuickBooks Error 6000, -82: Unblocking Connections to the Hosting Server

August 22, 2026

QuickBooks Error 6000, -80: Resolving Data Damage in Your Company File

July 2, 2026

QuickBooks Error 6000, -77: Resolving Incorrect Company File Path Errors

July 2, 2026