This might be a long shot, because usually, we get WindX errors due to this issue. But might be related here...
On the Sage server, there are a bunch ephemeral ports that we open for Advanced and Premium.
At one point, we've done a network sniff to see what was causing this error, and we noticed that with every connection, Sage tries to connect to one of these high ports in addition to the actual application port. Having some or all of those blocked, could occasionally cause connection errors (in our experience WindX)
netsh advfirewall firewall add rule name="Sage 100 - Ephemeral Ports" protocol=TCP dir=in localport=30000-65535 action=allow(If they are super security sensitive, they can open these ports to the Sage client server farm only)
------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com | 877-888-5525
http://gotomyerp.com/------------------------------