QuickBooks Error -6123, 0 -- Network and Firewall Connection Failures

Error -6123, 0 blocks opening or restoring a company file across a network; our engineers walk through resolving hosting and firewall conflicts to restore access.

QuickBooks Error -6123, 0 is one of the most frequently encountered 6000-series errors when a company file is stored on a network share, a NAS device, or another computer in a multi-user environment. The error interrupts the connection between the workstation and the company file before QuickBooks can finish opening or restoring it. In the majority of cases our engineers resolve, the underlying cause is a hosting configuration conflict, a firewall blocking database communication, or a damaged .ND (Network Descriptor) file — not corruption in the company file itself.

What the Error Message Says

The full dialog displayed by QuickBooks reads:

"Connection Error: We're sorry. QuickBooks could not open the company file. Error (-6123, 0)."

In some scenarios the message includes the additional phrase: "QuickBooks encountered a problem and needs to close." The error can appear when opening a company file, restoring a backup, or upgrading a file to a newer QuickBooks version across a network path.

What the Code Means

The -6123 component signals that QuickBooks was able to locate the company file on the network but could not complete the handshake required to lock and open it. The 0 indicates that no secondary sub-code was returned. This distinguishes the failure from a missing-file error and points specifically to a communication or permissions breakdown between QuickBooks Database Server Manager and the workstation requesting access.

What Triggers It

Our engineers see Error -6123, 0 most often in these scenarios:

• Multi-user hosting is enabled on more than one computer. QuickBooks allows only the server machine (the computer physically storing the file) to host multi-user access. When a workstation also has hosting turned on, conflicting database services prevent the file from opening.
• Windows Firewall or third-party security software blocks QuickBooks ports. QuickBooks Database Server Manager communicates over specific TCP ports. If those ports are closed, the connection times out and returns -6123, 0.
• Damaged or stale .ND files. The Network Descriptor files tell QuickBooks how to reach the company file on the network. If these become corrupted or point to an old server path, QuickBooks cannot establish a connection.
• The company file is stored on a NAS device or mapped drive that does not run a supported operating system for QuickBooks hosting.
• A backup (.QBB) file is being restored directly from removable media or a network location rather than from a local drive.

How to Fix It

Scenario 1: Hosting Conflict (Most Common)

1. On every computer in the setup, open QuickBooks and go to File > Utilities.
2. Check whether Host Multi-User Access appears on the menu. If you instead see Stop Hosting Multi-User Access, hosting is currently ON on that machine.
3. Hosting must be ON only on the server computer — the machine where the company file physically resides. On every workstation, select Stop Hosting Multi-User Access and confirm.
4. Restart all computers and attempt to open the file again.

Scenario 2: Firewall Blocking QuickBooks Ports

1. On the server computer, open QuickBooks Database Server Manager (found in the QuickBooks program folder).
2. Select Scan Folders and add the directory containing the company file, then click Scan. Confirm the scan reports the correct number of company files found.
3. Configure Windows Firewall to allow QuickBooks through: open Windows Defender Firewall > Allow an app through firewall and verify that all QuickBooks entries are checked for both Private and Public networks.
4. If third-party antivirus or security software includes its own firewall, add QuickBooks and its database management components to the exclusion list, or temporarily disable the firewall to test whether it is the cause.

Scenario 3: Damaged .ND Files

1. On the server computer, navigate to the folder containing the company file.
2. Locate the .ND file with the same name as the company file (for example, CompanyFile.QBW.ND).
3. Rename the file to CompanyFile.QBW.ND.OLD.
4. Run QuickBooks Database Server Manager and scan the folder so a fresh .ND file is generated.
5. Open the company file from the workstation again.

Scenario 4: Restoring a Backup Over the Network

1. Copy the .QBB backup file from the network share or USB drive to the local desktop of the computer performing the restore.
2. Restore from that local copy.
3. Once the restore completes successfully, move the resulting .QBW file to the server folder and run a folder scan in Database Server Manager.

How to Prevent It Recurring

Our engineers recommend designating a single computer as the database server and documenting it for all users. Periodically re-run the Database Server Manager folder scan after any Windows update, QuickBooks upgrade, or folder relocation. Keep firewall exclusions current whenever QuickBooks is updated to a new year version, since the executable paths and port requirements can change between releases.