cancel
Showing results for 
Search instead for 
Did you mean: 
seguse
Level 2

QB Loading Slow (Different Subnets)

We have QuickBooks Enterprise 20.0 w/ Database Manager installed on a brand new server (on a domain) with IP address 10.10.10.30/24. The default gateway is the firewall at 10.10.10.1. End users are in 10.10.100.x/24 with their default gateway of 10.10.100.1 which is the firewall. The firewall is doing routing-on-a-stick with a downstream trunk port to a Cisco 3850. When the end user (not on a domain but soon to be) is in the same subnet as the servers it opens the company file fast (within 5 seconds) yet when the end user is in a different subnet it takes over 1-2 minutes to open the company file. What would be causing this? Another thing I could try to do is move the layer 3 routed interface down on the Cisco 3850 and see if it gives any different result.

 

Things I've tried/verified:

-network traffic is very low

-disabled all anti-virus

-disabled windows firewall

-made sure allow traffic between firewall zone are good

-made sure .nd file has correct server ip address

-folder permissions are good

-took wireshark packet captures (not seeing anything standing out)

Solved
Best answer January 25, 2020

Best Answers
seguse
Level 2

QB Loading Slow (Different Subnets)

After hours of troubleshooting I finally found the solution. Changing the end user's preferred DNS server to the domain controller IP address and not 8.8.8.8 fixed the issue (I also mapped the share using the fully qualified domain name (FQDN). Even though mapping the share using the IP address QuickBooks was for some reason using DNS (not sure how or why) and causing the long delay. I went back and re-mapped using IP address (not FQDN) and it was also fast.

View solution in original post

1 Comment 1
seguse
Level 2

QB Loading Slow (Different Subnets)

After hours of troubleshooting I finally found the solution. Changing the end user's preferred DNS server to the domain controller IP address and not 8.8.8.8 fixed the issue (I also mapped the share using the fully qualified domain name (FQDN). Even though mapping the share using the IP address QuickBooks was for some reason using DNS (not sure how or why) and causing the long delay. I went back and re-mapped using IP address (not FQDN) and it was also fast.

View solution in original post

Need to get in touch?

Contact us
Sign in for the best experience
Ask questions, get answers, and join our large community of QuickBooks users.
Sign In / Sign Up