Davd Cichy's community posts

Thanks for the follow up.  In my opinion, it would be worthwhile for your organization to inquire of CloudFlare as to WHY, they are blocking the IP address of your identity server.  I think it is by accident b/c your base domain name is NOT being blocked.

CloudFlare is becoming quite dominant as a DNS provider at 1.1.1.1 and provides faster name resolution than even Google.  You don't want them accidentally crippling your service.

Also, I have now been forced to STOP using their DNS service and the protective benefits it afforst just so I can continue to run Remote Utilities.

Just to verify and close out this issue, it WAS CloudFlare's DNS servers that were COLD blocking your id.remoteutilties.com address.

I reverted our DNS to Google's 8.8.8.8 and 8.8.4.4 and all of my remote hosts started showing up again.

If id.remoteutilities.com must be reachable, then this has to be the root cause of my issue.  I cannot ping this URL at all.  My network (at the moment) is blind to it completely.

As you can see from that attached image, I can ping REMOTEUTILITIES.COM all day long, but NOT id.remoteutilties.com.

Turns out we are using CLOUDFLARE for DNS and while can resolve https://www.remoteutilities.com, they are 100% blocking

ID.remoteutilities.com

. So, I'm going to either have to get CloudFlare to add id.remoteutilities.com to their list or change my DNS provider

I have a paid starter license and have been using Remote Utilities for a couple of years now.  I run the installed version of Viewer (not portable) on both Windows 7 and Windows 10.

Fr om time to time, Viewer reports that every single host is offline when they are not.  I have tried everything when this happens to get Viewer to refresh and find the online hosts to no avail.

Everything includes suspending or stopping any/all running firewall and virus protections software, KILLING any/all instances of RUTVIEW.EXE, running the viewer portable version, adding a new connection to see if that will find a known running host, logging off the current windows user and back on .

NONE of these things work.  The ONLY way I can get RUTVIEW.EXE to start behaving correctly is to freaking reboot my PC which sucks when I am developing code and have a 100 browser windows open.

WHY does this keep happening?

Any suggestions on how to reset RUTVIEW and get thing working without rebooting my computer?  This has been consistently happening for two years.  I am on 6.10.

Also, I saw another post wh ere the moderator suggested trying to PING

id.remoteutilities.com

. I tried that and it FAILED. I can ping remoteutilities.com no problem, but now with the id. prefix.