QuickBooks® Error H303: Company File Network Location
Quick Answer:
Error H303 occurs when QuickBooks® cannot locate the server hosting your company file on the network. Fix it by verifying network connectivity, updating the Windows hosts file with the server IP address, and configuring Database Server Manager.
What is QuickBooks® Error H303?
QuickBooks® Error H303 is a network connectivity error that occurs when a workstation cannot locate or reach the server computer hosting the company file. This is different from Error H202 (which indicates communication problems) — H303 specifically means QuickBooks® cannot find the server at all on the network, often due to DNS resolution issues or incorrect network configuration. For a complete setup guide, see our Multi-User LAN Setup guide.
Error H303: Company file on another computer
QuickBooks® cannot locate the server hosting the company file on your network.
Symptoms:
- Error H303 when opening company file from workstation
- Cannot connect to server computer
- File works on server but not on workstations
- Error message mentions company file is on another computer
Resolution Steps:
- 1.Verify network connectivity and server availability
- 2.Check DNS resolution and computer name
- 3.Update hosts file with server IP
- 4.Configure Database Server Manager
First Checks for Error H303
Start here
- Ping the server from workstation (Command Prompt: ping [server-name])
- If ping fails, get server's IP address (on server: ipconfig)
- On workstation, edit hosts file: C:\Windows\System32\drivers\etc\hosts
- Add line: [server-IP] [server-name] (e.g., 192.168.1.100 SERVER1)
- Save hosts file (requires admin rights)
- On server, run Database Server Manager and scan folders
- Try opening company file from workstation
Diagnostic order
Prove name resolution before you change anything
H303 means the workstation never located the host, so every fix below is only worth applying once you know which lookup failed. Test one boundary at a time and keep the output of each test.
- 1
Ping by name
From the workstation, ping the server by its computer name and then by its address, and record both results.
Evidence: A name that fails while the address replies proves the fault is name resolution, not the network.
- 2
Read the real address
On the host, run ipconfig for the IPv4 address and hostname for the computer name.
Evidence: A written-down address and name to test against.
- 3
Resolve it locally
Add that address and name to the workstation hosts file, then run ipconfig /flushdns.
Evidence: Ping by name now replies from the address you wrote down.
- 4
Re-join the file
Rescan the company-file folder with Database Server Manager on the host, confirm the firewall rules, then reopen in multi-user mode.
Evidence: A fresh .ND file next to the company file and a successful multi-user open.
Detailed Solution Steps
- Verify Network Connectivity.
Test if the workstation can reach the server:
- On the workstation, open Command Prompt (Windows + R → cmd)
- Type:
ping [server-computer-name] - Press Enter and observe the results
- If you get replies, the connection works but there may be DNS issues
- If you get "Request timed out" or "Could not find host", there's a connectivity problem
- Ensure both computers are on the same network and subnet
- Get Server IP Address and Computer Name.
Gather server information needed for configuration:
- On the server computer, open Command Prompt
- Type:
ipconfigand press Enter - Find "IPv4 Address" - this is your server's IP address (e.g., 192.168.1.100)
- Write down this IP address
- Type:
hostnameand press Enter - Write down the computer name (e.g., SERVER1 or QUICKBOOKS-SERVER)
- Update Windows Hosts File on Workstation.
Add server information to hosts file for DNS resolution:
- On the workstation, open Notepad as Administrator (right-click → Run as administrator)
- Click File → Open
- Navigate to:
C:\Windows\System32\drivers\etc - Change file type dropdown to "All Files (*.*)"
- Open the file named "hosts" (no extension)
- At the bottom of the file, add a new line:
hosts file entry192.168.1.100 SERVER1- Replace the IP and name with your server's actual IP and computer name
- Save the file (Ctrl+S)
- Close Notepad
- Restart the workstation or flush DNS:
ipconfig /flushdns
Important: Make sure there's at least one space (or tab) between the IP address and computer name. Both must be on the same line.
- Configure QuickBooks® Database Server Manager.
Ensure Database Server Manager is properly configured:
- On the server, open QuickBooks® Database Server Manager
- Go to the "Scan Folders" tab
- If your company file folder is not listed, click "Add Folder"
- Browse to and select the folder containing your company file
- Click "Scan" and wait for the process to complete
- Verify new .ND files are created next to your company file
- Verify Firewall Settings.
Ensure Windows Firewall allows QuickBooks® connections:
- On the server, open Windows Defender Firewall with Advanced Security
- Click "Inbound Rules" on the left
- Look for rules containing "QuickBooks®" or "QBW"
- If missing, create new rules for ports: 8019, 56728, and your version-specific ports
- For testing, you can temporarily disable the firewall to see if it's blocking
- Re-enable firewall after testing and create proper rules
- Test Connection from Workstation.
Verify the fix worked:
- On the workstation, ping the server again using computer name
- It should now resolve to the correct IP address
- Open QuickBooks® on the workstation
- Navigate to the company file (via network path or mapped drive)
- Open the file - it should open without H303 error
- Test basic operations to ensure proper connectivity
Why Does Error H303 Occur?
Common Causes
- DNS Resolution Issues: Workstation cannot resolve server computer name to IP address
- Network Configuration Changes: Server IP address changed but workstation still uses old address — see Server IP Change fix
- Server Name Changes: Server computer name was changed without updating network configuration
- Incorrect Workgroup/Domain: Computers not in same workgroup or domain
- Database Server Manager Not Running: Service stopped or not configured on server
How to Prevent Error H303
Best Practices:
- Use static IP addresses for servers hosting QuickBooks® company files
- Document server computer names and IP addresses for your team
- Pre-configure hosts files on all workstations during initial setup
- Avoid changing server computer names after QuickBooks® is configured
- Keep all computers in the same workgroup or domain
Frequently Asked Questions
What causes QuickBooks® Error H303?
Error H303 occurs when QuickBooks® cannot locate the server hosting the company file due to network connectivity issues, DNS resolution problems, or incorrect network path configuration.
What is the difference between H202 and H303 errors?
H202 means QuickBooks® can find the server but cannot connect properly due to firewall or Database Server Manager issues. H303 means QuickBooks® cannot locate the server at all on the network.
How do I find my server IP address?
On the server computer, open Command Prompt and type "ipconfig". Look for "IPv4 Address" under your network adapter - this is your server IP address (e.g., 192.168.1.100).
Do I need to update hosts file on every workstation?
Yes, if DNS resolution is the issue, you'll need to update the hosts file on every workstation that experiences Error H303. This only needs to be done once per computer.
Related Resources
Need Professional Help?
If you're still experiencing Error H303 after following these steps, or need help with complex network configurations, our QuickBooks® network specialists are here to help.
Get Expert Support