Quick answer

When QuickBooks cannot connect to the company file server, the workstation fails at one of three layers: it cannot resolve the server name, cannot reach the host, or cannot open the shared folder. Test the server by name and by IP, repair the .ND connection file, then check hosting, services, firewall and share permissions.

What a "cannot connect to server" failure means

In multi-user mode, QuickBooks Desktop splits into two roles. The server stores the .QBW company file and runs the QuickBooks Database Server Manager. Every other PC is a workstation that opens that file across the network. When a workstation cannot connect, the company file never opens.

The timing of the message tells you a lot. A failure that appears instantly usually means the workstation cannot find the host name or the shared folder. A failure that appears after a 10–30 second pause usually means the host was found but the connection was blocked by a stopped service, an off hosting mode or a firewall rule.

This is broader than error H202, even though the two share causes. H202 appears when you switch to multi-user mode and the multi-user channel is blocked. A cannot-connect failure appears earlier: the workstation never establishes a path to the host. Start here when the error names the server, says the network path was not found, or appears before the company file opens.

Symptoms you will recognize

  • QuickBooks reports that it cannot connect to the server, or Windows reports that the network path was not found when you browse to the share.
  • The company file opens on the server itself but not from any workstation, or only one workstation is affected.
  • Multi-user access works after a reboot, then fails again within minutes or the next morning.
  • ping server-name fails, while ping against the server's IP address succeeds.

Common causes, ranked by how often they appear

  1. Name resolution breaks. The server switched from a static IP to DHCP, was renamed, or a stale DNS or hosts entry points at an old address.
  2. Multi-user hosting is off, or running on the wrong computer. A workstation that starts hosting in alternate mode takes ownership of the file and locks everyone else out.
  3. QuickBooks services are stopped. QuickBooksDBXX and QBCFMonitorService must be running on the server for workstations to connect.
  4. The firewall blocks the connection. QuickBooks needs TCP port 8019 plus the dynamic port shown in Database Server Manager, along with program exceptions.
  5. Share or folder permissions are wrong. The QBDataServiceUserXX account needs Full Control of the company-file folder and the network share.
  6. The .ND connection file is stale. QuickBooks writes host information into a network data file next to the company file, and a bad copy blocks the connection.
  7. The network isolates the computers. A VPN tunnel, a different subnet or wireless client isolation prevents the two machines from talking. Intuit does not recommend VPNs for QuickBooks Desktop.
  8. Antivirus blocks QuickBooks. Real-time scanning of the shared folder can interrupt the connection after it starts.

Before you begin

You need administrator rights on both computers, the server's host name, and ten to twenty minutes. Ask everyone to close QuickBooks before you restart services or change hosting, because a restart disconnects open sessions.

Back up before you change anything. Copy the whole company-file folder to another computer, including the .QBW, .ND, .TLG and .DSN files. Renaming support files is safe in normal cases, but a current copy is your recovery point if a permission change goes wrong.

How to fix QuickBooks cannot connect to the company file server

1

Test the server by name and by IP address

On the affected workstation, open Command Prompt and run ping server-name, then ping the server's IP address. On the server, run ipconfig /all and note the IPv4 address and host name. If the IP replies but the name does not, name resolution is broken. If neither replies, the computers cannot reach each other.

Next, type the UNC path \\server-name\share-name into the File Explorer address bar. A UNC path reaches the share directly, without a mapped drive letter that Windows can reassign. If the share opens, permissions are fine and the problem is inside QuickBooks.

2

Fix name resolution

Give the server a static IP address or a DHCP reservation so its address never changes. Confirm the host name in Settings → System → About on the server, and make sure no other computer on the network uses the same name.

If the name still fails from one workstation, add a temporary mapping to that workstation's hosts file at C:\Windows\System32\drivers\etc\hosts: one line with the server's IP address and host name. Save it with administrator rights, then fix DNS so you do not depend on the entry.

3

Rebuild the .ND connection file

On the server, open the folder that holds the company file. Find every file with the same base name and the extensions .ND, .TLG and .DSN, such as company.qbw.nd. Rename each one by adding .old to the end, so QuickBooks must write a fresh copy.

These files describe the connection and logging configuration; they are not your accounting data. QuickBooks recreates them the next time the company file opens or Database Server Manager scans the folder, which clears connection data that points at an old host name or IP.

4

Confirm that only the server hosts multi-user access

On the server, open QuickBooks, go to File → Utilities, and confirm Host Multi-User Access is selected. If the menu shows Stop Hosting Multi-User Access, hosting is already on; leave it alone.

On every workstation, open File → Utilities and select Stop Hosting Multi-User Access if it appears. A workstation that hosts takes ownership of the file in alternate hosting mode and locks out every other computer. Press F2 to check the hosting state shown in Product Information.

5

Start and repair the QuickBooks services on the server

Run services.msc on the server and find QuickBooksDBXX, where XX is your version year plus ten; QuickBooks 2023 uses QuickBooksDB33. Set Startup type to Automatic, confirm the status is Running, and start the service if it is stopped.

Open the Recovery tab and set Restart the Service for first, second and subsequent failures. Repeat for QBCFMonitorService. These services are the backbone of the hosted connection; when either one stops, workstations drop.

6

Open the firewall ports and program exceptions

On the server, open QuickBooks Database Server Manager and go to the Port Monitor tab. Note the port for your version. QuickBooks Desktop 2019 and later use TCP port 8019 plus a dynamic port listed there; 2018 uses 8019, 56728 and 55378–55382; 2017 uses 8019, 56727 and 55373–55377.

Create inbound and outbound Windows Firewall rules for those TCP ports. Also allow the QuickBooks programs themselves, including QBW32.exe, QBDBMgrN.exe, QBServerUtilityMgr.exe, QBCFMonitorService.exe and QBUpdate.exe. The full port list lives in the firewall and ports reference. If antivirus scans the shared folder, add it as an exclusion using the vendor's documented method.

7

Fix share and folder permissions

On the server, right-click the company-file folder and open Properties → Security. Give QBDataServiceUserXX — 29 for QuickBooks 2019, 28 for 2018, and so on for your year — Full Control of the folder. Then open the Sharing tab and grant the same account Full Control of the share, so permissions exist both on disk and over the network.

If the workstation still cannot browse the share, turn on Network discovery and File and printer sharing in the server's advanced sharing settings. The Database Server Manager guide covers the folder rescan.

8

Check the subnet, VPN and wireless settings

Compare the first three octets of the server's and workstation's IPv4 addresses; they must sit on the same subnet. A VPN or second router often puts the workstation on a different network, and wireless access points with client isolation block computer-to-computer traffic. Intuit lists VPNs, WANs, NAS devices and virtual machines as unsupported for QuickBooks Desktop.

If a VPN is required, ask your network professional to enable split tunneling so local traffic reaches the server directly, and confirm that the server's SMB file sharing port, TCP 445, is open across the tunnel.

9

Run the File Doctor network check

Install the QuickBooks Tool Hub on the workstation and run QuickBooks File Doctor from Company File Issues. Select the company file, choose Check your file and network, and enter the QuickBooks admin password. File Doctor tests the multi-user path and repairs several firewall and connection problems on its own.

If the connection still fails, open the Tool Hub's Network Issues tab on the server and run the Database Server Manager scan. The scan resets firewall permissions for the company-file folder and clears background blocks that manual checks miss.

Verify the fix

  1. From the workstation, confirm ping server-name returns replies with no packet loss.
  2. Open the UNC path \\server-name\share-name in File Explorer and list the company-file folder.
  3. Open QuickBooks on the workstation, open the company file, and switch to multi-user mode.
  4. Open the same file from a second workstation and post a test transaction, then delete it.
  5. Press F2 on the server and confirm the file and hosting information match your setup.

If QuickBooks still cannot connect

Recurring failures on one workstation usually come from that machine: a stale mapped drive, an old hosts entry, endpoint security or a failing adapter. Remove mapped drives and reconnect through the UNC path instead.

If every workstation drops several times a day, check the server's power settings. Sleep, fast startup and adapter power saving break idle connections. Set the server to never sleep and give its network adapter a static IP. When the file opens locally but never over the network, review hosting mode issues and the error 6000 repair order.

Prevention

  • Use a wired LAN connection for the server and give it a DHCP reservation or static IP.
  • Keep the server awake around the clock and disable sleep on its network adapter.
  • Restart both QuickBooks services after any Windows or QuickBooks update.
  • Never store the company file in OneDrive, Dropbox or another sync folder, and never host it from a NAS.
  • Rescan the company-file folder after moving the file or changing the network.

Frequently asked questions

How is this different from QuickBooks error H202?

H202 appears when you switch to multi-user mode and something blocks that channel. A cannot-connect failure happens earlier: the workstation cannot find or reach the host. The causes overlap, so start here with name resolution, the UNC path and the .ND file, and start with firewall and hosting checks for H202.

Why does ping work by IP but not by server name?

That is a name resolution failure, not a connectivity failure. The network path is healthy, but the workstation cannot turn the host name into an IP address. Give the server a static IP, correct the DNS record, or add a temporary hosts-file entry while you fix DNS.

Can I connect a QuickBooks Online company to a file server?

No. QuickBooks Online is a cloud product with no company file on your network, so there is no server to connect to and no multi-user hosting to configure. This guide applies to QuickBooks Desktop Pro, Premier, Enterprise and Accountant. If you are migrating, see the desktop to Online conversion guide.

Is it safe to delete the .ND file?

Do not delete it; rename it with an .old extension instead. The .ND file holds connection settings that QuickBooks rebuilds automatically, so renaming keeps a fallback while forcing a clean copy. Your transactions stay in the .QBW file and are not affected.

Sources & further reading