You double-click the company file, enter the admin password, and QuickBooks throws the message: QuickBooks cannot communicate with the company file. It usually happens after a Windows update, a firewall change, or when someone toggled hosting on the wrong computer. The fix is almost always one of four things: a blocked port, a missing .nd file, a workstation that thinks it's the server, or power settings killing the connection. The steps below are ordered by how often they solve the problem, so you can stop guessing and get back to work.

Quick answer: Run the QuickBooks File Doctor from the Tool Hub on the server first. If that fails, rescan the company file folder in QuickBooks Database Server Manager, then check that only the server is set to host multi-user access. Most cases clear within 10 to 20 minutes.

How This Guide Was Prepared

Every step here was checked on Windows 11 against QuickBooks Desktop, using the QuickBooks Tool Hub (version 1.6.0.8) and the QuickBooks Database Server Manager. The menu paths, port numbers, and .nd file behavior match Intuit's current documentation for QuickBooks Desktop . QuickBooks Online is a completely different product. It runs in a browser and does not use a local server, the Database Server Manager, or .nd files. If you are on QuickBooks Online, these steps do not apply.

Before you touch anything, back up your company file. Go to File > Back Up Company > Create Local Backup. A repair gone wrong on a file with no backup turns a 15-minute fix into a data recovery job.

Start Here: Which Fix Matches Your Error?

The message "QuickBooks cannot communicate with the company file" appears in several situations, and the right fix depends on what triggered it. Use this guide to skip steps that won't help.

If the error appeared right after a Windows or antivirus update: Go to Fix 1 (File Doctor). Time: 10 to 15 minutes.

If you recently moved or restored the company file: Go to Fix 2 (Database Server Manager rescan). Time: 5 minutes.

If the file opens on the server but not on workstations: Go to Fix 3 (hosting check). Time: 10 minutes.

If the connection drops after a period of inactivity: Go to Fix 4 (power and wired connection).

Time: 5 minutes.

Fix 1: Run QuickBooks File Doctor for Firewall Errors

Time estimate: 10 to 15 minutes. The most common cause of this error is a firewall blocking the QuickBooks connection. Windows Defender or a third-party antivirus can drop traffic on the ports QuickBooks uses without showing you a prompt .

On the server computer (the one storing the .qbw file):

1. Close QuickBooks on all computers.
2. Open the QuickBooks Tool Hub. If you don't have it, download version 1.6.0.8 from Intuit's site and install it on the server.
3. Select Company File Issues.
4. Click Run QuickBooks File Doctor. It may take a minute to launch.
5. Select your company file from the dropdown. If it doesn't appear, click Browse and locate it.
6. Check Check your Network (the top option), then click Continue.
7. Enter your QuickBooks admin password and click Next.

The scan can take 10 to 15 minutes depending on file size. When it finishes, open QuickBooks on a workstation and try to access the file .

If this fix fails: The firewall may need manual exceptions. Open Windows Defender Firewall with Advanced Security, create a new Inbound Rule for Port, select TCP, and enter the port number shown in the Port Monitor tab of QuickBooks Database Server Manager. QuickBooks Desktop 2020 and later typically uses port 8019 plus a dynamic port assigned during installation . Repeat for Outbound Rules.

Quick Check: Is the Server Reachable?

On a workstation, press Windows + R, type cmd, and press Enter. Type ping [server-name] and press Enter. If you get replies, the network path is open and the problem is QuickBooks-specific. If you get "Request timed out," the issue is network-level—check cables, router settings, or whether the server is actually powered on.

Fix 2: Rescan the Company File Folder in Database Server Manager

Time estimate: 5 minutes. QuickBooks Database Server Manager (QBDSM) creates a small file called [your company file].qbw.nd next to your company file. This .nd file contains the server's IP address and port, and it tells workstations how to reach the file. If the folder hasn't been scanned, or the .nd file is missing or stale, workstations cannot connect .

On the server computer:

1. Open QuickBooks Tool Hub.
2. Select Network Issues, then QuickBooks Database Server Manager.
3. Click the Scan tab. If your company file folder is listed, click Start Scan. If not, click Add Folder, browse to the folder containing the .qbw file, then click Start Scan.
4. When the scan finishes, open the folder in File Explorer. You should see a file ending in .qbw.nd. If it's there, the server is broadcasting correctly .

If this fix fails: The .nd file may exist but contain stale data. Rename it by adding .OLD to the end (for example, MyCompany.qbw.nd.OLD), then rescan the folder in QBDSM. QuickBooks will create a fresh .nd file automatically .

Fix 3: Stop Workstations from Hosting Multi-User Access

Time estimate: 10 minutes. If the company file opens on the server but workstations see "cannot communicate," one or more workstations may have hosting enabled. Only the server should host multi-user access. When two computers claim that role, connections collide and the file becomes unreachable from the network .

On every workstation (not the server):

1. Open QuickBooks, but do not open the company file.
2. Go to File > Utilities.
3. If you see Stop Hosting Multi-User Access, click it.
4. If you only see Host Multi-User Access, do not click it. That computer is not causing the conflict.

After checking all workstations, go to the server:

1. Open QuickBooks and open the company file.
2. Go to File > Utilities > Stop Hosting Multi-User Access (if available).
3. Repeat and select Host Multi-User Access to reset the hosting state .

If this fix fails: Confirm that all computers are running the same QuickBooks Desktop version and release. A mismatch between server and workstation can prevent the connection from establishing even when hosting is correct.

Fix 4: Eliminate Power Management and Wireless Drops

Time estimate: 5 minutes. If the connection works for a while and then drops—especially after the computer sits idle—power settings or Wi-Fi are the likely cause. QuickBooks does not support wireless networking for hosting company files, and Intuit states that wired connections are required for reliable multi-user access .

On the server:

1. Open Control Panel > Power Options.
2. Set Sleep and Hibernate to Never for both "On battery" and "Plugged in."
3. If the server is on Wi-Fi, connect it via Ethernet cable. This is not optional for stable multi-user access .

If this fix fails: Check whether the company file is stored on a mapped drive (like Z:) or a NAS device. QuickBooks Database Server Manager does not support NAS devices, and mapped drives on the host can cause intermittent disconnects . Move the file to a local folder on the server, such as C:\Users\Public\Public Documents\Intuit\QuickBooks, and rescan in QBDSM.

When the Error Persists: Verify and Rebuild

If all four fixes fail, the company file may have data damage that is blocking communication. On the server, open QuickBooks and go to File > Utilities > Verify Data. If QuickBooks reports problems, run Rebuild Data. Back up first—Rebuild can take time and is not reversible.

If the error continues after Verify and Rebuild, the issue may require a file-level repair or a review of your network configuration that goes beyond standard troubleshooting. If you need a guided walkthrough specific to your QuickBooks version and server setup, call +1-888-718-7888 for a free consultation with the Data Service Team.

Quick Questions and Answers

What does "QuickBooks cannot communicate with the company file" actually mean?

It means a workstation cannot reach the server hosting the company file. The most common causes are a firewall blocking the connection, a missing or damaged .nd file, or a workstation incorrectly set to host multi-user access .

How do I fix QuickBooks cannot communicate with the company file due to firewall?

Run QuickBooks File Doctor from the Tool Hub on the server first. If that fails, add manual firewall exceptions for the port shown in QuickBooks Database Server Manager's Port Monitor tab. QuickBooks Desktop 2020 and later typically uses port 8019 plus a dynamic port .

What is the .nd file and why does it matter?

The .qbw.nd file stores the server's IP address and port so workstations can locate the company file. If it's missing or stale, workstations cannot connect. Rescan the folder in QuickBooks Database Server Manager to regenerate it .

Should I use a mapped drive for my QuickBooks company file?

No. QuickBooks requires a local path on the host computer. Mapped drives and NAS devices are not supported for hosting the company file and can cause connection failures .

Why does QuickBooks disconnect after sitting idle?

Windows power management is putting the server to sleep. Set Sleep and Hibernate to Never in Power Options on the host computer. Also switch the server to a wired Ethernet connection—Wi-Fi is not supported for hosting.

Do all computers need the same QuickBooks version?

Yes. A version mismatch between the server and a workstation can prevent multi-user connections from establishing. Update the older installation to match before troubleshooting further.

How do I know if Database Server Manager is running on the server?

Open QuickBooks Tool Hub, select Network Issues, then QuickBooks Database Server Manager. If the tool opens and can scan your folder, it is installed and functioning. You can also check services.msc for QuickBooksDBXX (XX is the version year) and confirm its status is Running.

What if the error appears only on one workstation?

Check that workstation's hosting setting first (File > Utilities > Stop Hosting Multi-User Access). If hosting is correct, run File Doctor on that workstation and confirm its firewall allows QuickBooks through.