Network Diagnostics: Resolving “Network Diagnostics Failed” in QBDBSM

October 27, 2026 5 min read

When running the QuickBooks Database Server Manager (QBDBSM) to prepare company files for multi-user access, you may encounter the alert: “Network Diagnostics Failed.” This warning means the database utility cannot verify that the host machine meets the network requirements for file sharing. When this test fails, client workstations cannot open company files over the network, frequently triggering H-series errors like H202 or H505.

Fast-Fix: Resolving “Network Diagnostics Failed”

To fix “Network Diagnostics Failed,” verify that QBCFMonitorService and the appropriate QuickBooksDBXX service are running in Windows Services and set to Automatic startup. Next, check the folder containing your company file to confirm that both Share and NTFS Security permissions grant Full Control to Everyone and the local QBDataServiceUser. Finally, restart the database manager and rescan the folder.

Quick Status & Triage Snapshot

  • Data Risk Tier: Low (diagnostic checks test permissions, registry entries, and services; your company data is not modified).
  • Multi-User Impact: Critical (client workstations cannot resolve the host database until the scan succeeds).
  • Common Trigger: Corrupted .ND support files, Windows firewall blocking dynamic ports, disabled background services, or restrictive folder security.
  • Estimated Fix Time: 10 to 20 minutes.

Technical Anatomy: What the Diagnostic Check Tests

When you click “Start Scan” in the QuickBooks Database Server Manager, the utility executes four distinct validation checks:

  1. Service Verification: It confirms that the version-specific database service (QuickBooksDBXX) is active and listening for connections.
  2. Path and Permission Audit: It verifies that the specified folder is shared across the network and that the operating system grants read, write, and execute permissions to the service account.
  3. Port Binding: It verifies that port 8019 and dynamic database ports (e.g., 55388–55397) are open and not hijacked by other applications.
  4. Network Descriptor Generation: It generates or updates the .ND file in the company folder, saving the server’s current IP address, computer name, and active port.

If any of these four components fail to respond, QBDBSM halts the process and returns the “Network Diagnostics Failed” status.

Step-by-Step Resolution Path

Follow these diagnostic steps in order to clear the failure.

Step 1: Verify and Restart QuickBooks Services

If the background database engine is paused or hung, network tests will immediately fail:

  1. On the host computer or server, press Windows Key + R, type services.msc, and press Enter.
  2. Locate the database engine service for your version:
    • QuickBooks 2026: QuickBooksDB36
    • QuickBooks 2025: QuickBooksDB35
    • QuickBooks 2024: QuickBooksDB34
  3. Right-click the service and select Properties.
  4. Set the Startup type to Automatic.
  5. Check the Service status. If it is stopped, click Start. If it is already running, click Stop, wait five seconds, and click Start.
  6. Switch to the Log On tab and confirm it is set to log on as Local System account (or the designated QBDataServiceUserXX account).
  7. Scroll down to locate QBCFMonitorService, set it to Automatic, and ensure it is Running.

If the database service refuses to stay active, consult Service Fix: Troubleshooting “QuickBooks Database Server Manager Stopped” or see QBCFMonitorService: How to Fix Service Startup Errors on Your Server.

Step 2: Delete Damaged .ND Files

A corrupted or locked Network Descriptor (.ND) file prevents QBDBSM from writing fresh configuration parameters:

  1. Open File Explorer and browse to the folder containing your company file (.qbw).
  2. Locate any files with the extension .ND (e.g., CompanyFile.qbw.nd).
  3. Right-click the .ND file and click Delete (or rename it to .ND.OLD).
  4. Also check for duplicate temporary lock files ending in .DSN or .TLG.OLD and remove them.

For a deeper look into the role of support files, see Manual Fix: Renaming .ND and .TLG Files to Resolve 6000 Errors.

Step 3: Repair Share and Security Permissions

QBDBSM flags network diagnostics as failed if the database user cannot modify files within the target folder:

  1. Right-click the folder where your company files are stored and select Properties.
  2. Go to the Security tab and click Edit.
  3. Verify that the following accounts are listed and have Full Control checked:
    • Everyone
    • SYSTEM
    • Administrators
    • QBDataServiceUserXX (matching your year)
  4. If an account is missing, click Add, type the name, click Check Names, and assign Full Control.
  5. Go to the Sharing tab, click Advanced Sharing > Permissions, and confirm that Everyone has Full Control.

For complete security configuration rules, review Data Security: How to Set Up QuickBooks Folder Sharing Permissions.

Step 4: Open Required Windows Firewall Ports

If the Windows Defender Firewall blocks port binding, diagnostic tests cannot verify communication:

  1. Press Windows Key + R, type wf.msc, and press Enter.
  2. Click Inbound Rules > New Rule.
  3. Choose Port > TCP.
  4. Enter the required ports for your software year (e.g., 8019, 55388-55397).
  5. Set the action to Allow the connection across all profiles, name the rule QuickBooks Database Ports, and click Finish.

For exact port ranges across every modern release, check Firewall Ports: Configuring Windows Firewall for QuickBooks 2024–2026.

Step 5: Re-Run the Folder Scan in QBDBSM

Once services are running, permissions are open, and corrupt descriptor files are removed:

  1. Open QuickBooks Database Server Manager.
  2. Under the Scan Folders tab, click Add Folder and select your company file folder.
  3. Click Start Scan.
  4. The scan will progress through the directory and finish with a status showing your company files and confirmation that multi-user hosting is operational.

What to Do If the Scan Still Fails

If “Network Diagnostics Failed” persists after following these steps:

  1. Reboot the Host: A pending Windows Update or stranded system process may hold exclusive handles on the folder. Restart the server.
  2. Move the File Temporarily: Create a new folder on the root of your hard drive (such as C:\QBTest), copy a clean company file into it, share the folder, and scan it with QBDBSM. If that scan succeeds, the issue lies in complex nested permissions on your original folder structure.

Closing the Books

The “Network Diagnostics Failed” notification is a safeguard that alerts you to service halts, blocked ports, or permission restrictions before users experience sudden dropouts. By systematically ensuring the QuickBooksDB service is running, clearing damaged .ND files, and verifying folder access rights, you can pass diagnostics and establish an uninterrupted multi-user network.

Version Mismatch: How to Update QBDBSM to Match Your QuickBooks Year

August 12, 2026

Troubleshooting “QuickBooks Database Server Manager Stopped”

July 2, 2026

QBDBSM: How to Install and Configure Database Server Manager

July 2, 2026