![]() ![]() So yes, I can ping 127.0.0.1 as well as its IP address 192.168.22.10 from both admin and client accounts.Īgain I believe this is a startup race condition with QBCFMonitorService and DNS Server on Windows 2016 Server with RDS. Please understand this is technically not over a physical network since it is Windows Server 2016 with Remote Desktop Services (RDS), although it does utilize network sockets. Now go to the workstation affected by the error and open the command prompt window. Type IPConfig, press Enter, and you will get the IP address of the server computer. Manually starting QBCFMonitorService fixes everything proving hosting is on and not the root cause. Without delay, go to the server computer and open the command prompt by running the CMD command using the Run dialog box. Again manually starting the service fixes the issue proving the firewall is not misconfigured.Ģ. Port 8019 is open as well as the “dynamic port”: 62979. ![]() It is configured correctly by both Quickbooks installation and verified here. Configure you firewall port to open 8019. I have reviewed the page you linked which lists three suggestions for if QBCFMonitorService is not running:ġ. I have already tried Quickbooks File Doctor. No sign of why the service does not start up. I can’t find any logs pointing to anything useful, nothing in Event Viewer or log files in Intuit directories. Only my self discovered DNS server delay startup seems to work and I worry that may not someday if it is a weird race condition. ![]() I’ve re-installed, clean installed, removed older versions running in parallel, everything. It is not a firewall issue – that would not cause the service to not start or crash. Quickbooks support told me change Logon user as “System” and to set the recovery options to restart (unlimited). What is going on here? This is a fairly typical install, single server running typical services, DNS, Remote Desktop, Remote Access VNC. I tried reserving the ports (both UDP
0 Comments
Leave a Reply. |