QuickBooks Error 6000-82: Network Connection Lost to Company File
Quick Answer:
Error 6000-82 occurs when the network connection to QuickBooks company file is lost or interrupted. Fix it by deleting the corrupted .ND file, using UNC paths instead of mapped drives, and running Database Server Manager to rescan the folder.
What is QuickBooks Error 6000-82?
QuickBooks Error 6000-82 is a network connectivity error that occurs when the connection to the company file is lost or interrupted during operation. This typically happens when the .ND (Network Data) configuration file becomes corrupted, the network connection drops, or the file path changes while QuickBooks is accessing it.
Error 6000-82: Network connection lost to company file
QuickBooks lost connection to the server or network path hosting the company file.
Symptoms:
- •Error 6000-82 when opening company file from network
- •File works locally but fails over network
- •Intermittent connection drops during use
- •Error appears after network changes
- •Cannot access company file from workstations
Resolution Steps:
- 1.Delete corrupted .ND configuration file
- 2.Use UNC path instead of mapped drives
- 3.Run Database Server Manager scan
- 4.Verify network connectivity and stability
Quick Fix for Error 6000-82 (7 Minutes)
Fastest Solution
- On server: Navigate to company file folder
- Delete the .ND file (e.g., CompanyFile.qbw.nd)
- Open QuickBooks Database Server Manager on server
- Click "Scan Folders" → Select company file folder → "Scan"
- Wait for scan to complete (new .ND file created)
- On workstation: Use UNC path (\\\\servername\\folder) not mapped drive
- Open company file - error should be resolved
Detailed Solution Steps
Ensure no one is using the company file:
- Close QuickBooks on server computer
- Close QuickBooks on all workstation computers
- Verify no QuickBooks processes running in Task Manager
- If processes remain, end QBW32.exe and QBDBMgrN.exe
Important: All users must close QuickBooks before deleting .ND files. Active connections will prevent file deletion or cause new errors.
Remove the corrupted network data file on the server:
- On the server, navigate to the company file folder
- Enable viewing of hidden files:
- Open File Explorer → View tab → Options
- View tab → Show hidden files, folders, and drives
- Uncheck "Hide extensions for known file types"
- Click OK
- Locate the .ND file (same name as company file + .nd)
Example:
MyCompany.qbwMyCompany.qbw.nd- Right-click the .ND file → Delete
- Also delete .TLG file if present (MyCompany.qbw.tlg)
- Empty Recycle Bin
What This Does
Regenerate network configuration files:
- On server: Start → All Programs → QuickBooks → QuickBooks Database Server Manager
- If not installed, download and install QuickBooks Database Server Manager
- Go to "Scan Folders" tab
- If your company file folder is not listed, click "Add Folder"
- Browse to company file location → Select folder → OK
- Select the folder in the list → Click "Scan"
- Wait for scan to complete (may take 2-5 minutes)
- Verify new .ND file was created in company file folder
Scan completed successfullyFiles scanned: 1New .ND files created: MyCompany.qbw.ndUse UNC paths instead of mapped drives for better reliability:
Why This Matters:
Mapped drives (Z:, Y:, etc.) can disconnect or change, causing Error 6000-82. UNC paths (\\\\servername\\folder) are more stable and don't depend on drive letter assignments.
- On workstation, determine the UNC path to company file:
Bad: Z:\QuickBooks\MyCompany.qbw (mapped drive)Good: \\SERVER1\QuickBooks\MyCompany.qbw (UNC path)- To find UNC path from mapped drive:
- Open Command Prompt
- Type:
net use Z:(replace Z: with your drive letter) - Look for "Remote name" in output - this is the UNC path
- Open QuickBooks on workstation
- File → Open or Restore Company → Open a company file
- Type the UNC path in the file name box
- Click Open
Ensure stable network connection to server:
- On workstation, open Command Prompt
- Ping the server by name:Command Promptping SERVER1
- Verify you get replies with low latency (< 10ms on LAN)
- Test continuous ping for stability:Command Promptping SERVER1 -t
- Let it run for 1-2 minutes - watch for packet loss
- Press Ctrl+C to stop - check statistics
- If packet loss > 5%, investigate network issues
Network Instability
Verify Error 6000-82 is resolved:
- On workstation, open QuickBooks
- File → Open or Restore Company
- Open company file using UNC path
- File should open without Error 6000-82
- Switch to multi-user mode: File → Switch to Multi-user Mode
- Perform test transactions to verify stability
- Repeat on additional workstations if needed
Why Does Error 6000-82 Occur?
Root Causes
- Corrupted .ND Configuration File: Network data file becomes damaged due to improper shutdown or network interruption
- Unstable Network Connection: Intermittent network drops, packet loss, or high latency causing connection failures
- Mapped Drive Disconnection: Using mapped drives (Z:, Y:) that disconnect or become unavailable
- Server Path Changes: Server name, share name, or folder path changed after initial configuration
- Network Timeout: Slow network or server response causing QuickBooks to timeout during file access
- Firewall Blocking: Firewall temporarily blocking QuickBooks Database Service connections
How to Prevent Error 6000-82
Best Practices:
- Always use UNC paths (\\\\servername\\folder) instead of mapped drives for company files
- Maintain stable wired network connections (avoid WiFi for QuickBooks if possible)
- Close QuickBooks properly (File → Close Company) before shutting down computers
- Don't rename server, change share names, or move company files without updating all workstations
- Run Database Server Manager scan after any server configuration changes
Frequently Asked Questions
What causes QuickBooks Error 6000-82?
Error 6000-82 occurs when the network connection to the QuickBooks company file is lost or interrupted, typically due to corrupted .ND configuration files, unstable network connections, or incorrect network path configurations (mapped drives vs UNC paths).
What is the difference between 6000-82 and 6000-83?
Error 6000-82 indicates lost network connection during operation (network-related). Error 6000-83 indicates file corruption or locked network data files (file-related). Both require deleting .ND files, but 6000-83 may also need File Doctor repair.
Will deleting the .ND file delete my data?
No, deleting the .ND file is completely safe. The .ND file only contains network configuration settings, not your financial data. Your company file (.QBW) remains intact. Database Server Manager will automatically recreate the .ND file with correct settings.
Should I use mapped drives or UNC paths?
Always use UNC paths (\\\\servername\\folder) for QuickBooks company files. Mapped drives (Z:, Y:) can disconnect, change letters, or become unavailable, causing Error 6000-82. UNC paths are more stable and reliable for network file access.
Can WiFi cause Error 6000-82?
Yes, WiFi connections are less stable than wired Ethernet and can cause intermittent network drops leading to Error 6000-82. For QuickBooks multi-user mode, wired connections are strongly recommended to prevent connection issues.
Related Resources
Need Professional Help?
If you're still experiencing Error 6000-82 after following these steps, or need help with network configuration, our QuickBooks network specialists are here to help.
Get Expert Support