Quickbooks MultiUser issue

We have a customer running QB Premier Edition 2016 and for the past year - sporadically - they will get H202 errors and cannot access multi-user functionality - it will run in single mode but not multi.  For the first few times after it started happening, we would reboot the server and it seemed to fix it.  However, when that didnt work, we did some research and it said to stop the DNS server, start the QBDatabase26 service and restart the DNS and it works.  Sometimes we can get for a couple of months and other times it happens a couple of times a week.  Is there a permanent fix?
Daren Anderson, MSISPresidentAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
Try the following:

1. Reinstall the Server Manager and scan for the file.
2. Get the Intuit Network Diagnostics, run it, and check for firewall or other connectivity requirements. We use this tool.
3. Upgrade to QB V2017 as some of these errors have been fixed in the newer version.
Daren Anderson, MSISPresidentAuthor Commented:
Yes when I first started getting the error, we used the Network Diagnostics tool - but nothing other than the Database server wasn't running came up - nothing about firewalls/DNS.  Also have scanned the file thru Server Manager.  I will check with them to see if they want to upgrade.
JohnBusiness Consultant (Owner)Commented:
We had the H202 errors with V2016 a few times and we worked with Intuit for the first 2 solutions here. V2017 has been a lot more stable and V2018 is due out very soon.
I've seen this issue before (DNS server QBDBManager port conflict).  While starting QB first will resolve the problem, it will come back on a reboot unless you do something to resolve it.

Take a look at this link:

The core to the solution there is:
netsh int ipv4 add excludedportrange protocol=udp startport=55368 numberofports=5

I don't recall if this was the method I used to resolve it, but it ought to work.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.