Rebuilding a Corrupt or Missing .ND File for QuickBooks Desktop Multi-User Access

When QuickBooks Tool Hub cannot repair a damaged network descriptor file, our engineers rebuild the .ND file from scratch and reconfigure database server hosting so every workstation reconnects cleanly.

When the QuickBooks Desktop network descriptor (.ND) file is missing or corrupted beyond what QuickBooks Tool Hub can resolve, multi-user access fails across every workstation on the network. The .ND file is a small text file that tells QuickBooks where the company file lives and which machine is hosting the database server. Without a valid .ND file, workstations cannot locate the company file over the network, even though the file itself is intact. Our engineers use the following playbook to rebuild the .ND file from scratch, reconfigure the database server, and validate multi-user access before rolling it out to users.

Phase 1: Assess the Current State and Back Up

Before modifying anything, we confirm that the problem is actually the .ND file and not deeper data corruption in the company file itself.

1. On the server machine, navigate to the folder containing the .QBW file.
2. Check whether a .ND file exists. It will have the same name as the company file but a .ND extension.
3. If the .ND file exists, open it in Notepad. A healthy .ND file contains the server name, IP address, and company file path in a structured format. Garbled or truncated content confirms corruption.
4. Create a verified backup of the company file (File ▸ Back Up Company ▸ Create Local Backup) before proceeding.
5. Note the exact folder path to the .QBW file and the server's computer name — both are needed in Phase 3.

Phase 2: Remove the Damaged .ND File

1. Close QuickBooks on all workstations and on the server.
2. In Windows Services, stop the QuickBooksDB service for your year version (for example, QuickBooksDB35 for 2024).
3. Delete or rename the corrupt .ND file. Renaming it to .ND.OLD preserves it as a rollback artifact.
4. Also delete or rename any .DSN files with the same base name as the company file.

Phase 3: Regenerate the .ND File

There are two methods. We always try the QuickBooks Database Server Manager first, then fall back to manual creation if the generated file is incomplete.

Method A — Database Server Manager:

1. On the server, open QuickBooks Database Server Manager (Start ▸ All Programs ▸ QuickBooks ▸ QuickBooks Database Server Manager).
2. Go to the Folder tab and add the folder containing the .QBW file.
3. Click Scan. The scan regenerates the .ND file and verifies that the database server can open the company file.
4. Review the scan report. Confirm it lists the company file with a status of "Monitored."

Method B — Manual Creation (if Method A fails):

1. Open Notepad on the server.
2. Construct the .ND file using the server name and company file path noted in Phase 1. The standard format includes the server's IPv4 address, the UNC path to the .QBW file, and the database server engine identifier.
3. Save the file with the exact same base name as the company file and a .ND extension, in the same folder as the .QBW file.
4. Restart the QuickBooksDB service.

Phase 4: Reconfigure Database Server Hosting

1. On the server, open the company file in QuickBooks.
2. Go to File ▸ Utilities. If the menu option reads Host Multi-User Access, hosting is currently off — click it to enable hosting on this machine. If it reads Stop Hosting Multi-User Access, hosting is already on; leave it as is.
3. Close the company file but leave QuickBooks open.
4. Confirm hosting is active: File ▸ Utilities should now show Stop Hosting Multi-User Access.
5. Switch to Single-User Mode if needed, then switch back to Multi-User Mode to confirm the server can host its own file.

Phase 5: Validate Access from Each Workstation

1. On the first workstation, map a persistent drive letter to the server's shared folder using the server's computer name (not the IP address, which can change with DHCP).
2. Open QuickBooks and select Open or Restore an Existing Company.
3. Browse to the .QBW file via the mapped network drive — not a recent-files list or a local shortcut.
4. Log in and confirm the mode indicator at the top reads "Multi-User Mode."
5. Repeat on every remaining workstation before declaring the rollout complete.

Rollback Points

• After Phase 2: If deleting the .ND file causes additional problems, restore the .ND.OLD file and stop the QuickBooksDB service. At this point nothing has changed in the company file itself.
• After Phase 3: If neither regeneration method produces a working .ND file, the folder-level permissions or firewall rules on the server are likely blocking the database engine. Check that ports 8019 (dynamic) and 56728 (static, year-dependent) are open in Windows Defender Firewall on the server.

Clean Outcome

A successful rebuild looks like this: the .ND file exists in the same folder as the .QBW file, opens cleanly in Notepad with readable content, the Database Server Manager scan reports the file as monitored, and every workstation can open the company file in Multi-User Mode simultaneously without error -6000 series codes or H-series errors.