Keith Evans's community posts

Bundaberg Queensland Australia

Pinging id.remoteutilities.com [64.20.61.146] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.20.61.146:
   Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

my IT guys said they get similar answers, and we are large customer .. but typical

Just another update, seems our network was having issues with cloud connectivity for other programs we use also, we are a radio broadcast company Australia wide and we use iInet throughout so this issue seemed to affect other stuff also

Same here all back up and running ... and mine behind a corporate firewall, interesting...have to say good on Remote Utilities having a forum such as this that we can all participate

my agent error is showing connection time out port 443 id server timeout, which is behind our corporate firewall, which i that case is being blocked as to viewer when i restart all icons are offline ... and this is my error log once again port 443 which again i suspect is blocked on our network, IT have been very aggressive lately closing ports for security
18-10-2021__03:43:39__593 Connection #493784. Connection to "1.KIX Agnes Water NUC". Mode: <Authorization>. Connecting...
18-10-2021__03:43:39__593 InetConnection #493784. Internet connection to 1.KIX Agnes Water NUC (id70.remoteutilities.com:5655).
18-10-2021__03:43:49__598 InetConnection to internet-id server #493784 Error. Name: "1.KIX Agnes Water NUC", host: "id70.remoteutilities.com:5655". Exception class: "EIdConnectTimeout". Message: "Connect timed out.".
18-10-2021__03:43:50__648 Check ID Connection. Connecting...: "id70.remoteutilities.com:5655".
18-10-2021__03:43:59__603 InetConnection to internet-id server #493784 Error. Name: "1.KIX Agnes Water NUC", host: "id70.remoteutilities.com:443". Exception class: "EIdConnectTimeout". Message: "Connect timed out.".

one of the things iInet offers is static IPs which our network requires , but i am starting to think that it maybe Provider related also

yes sorry should have said that also, if i shut down viewer and restart it then correct no longer available

i have lodged a ticket with my IT dept , as now no connections work while i am on the network but what is interesting is while on my own connection if i have logged into the clients and the icon is green, then swap to corporate network i can reconnect to any previous logged in, so i suspect they have been playing with port blocking for security reasons, they have definitely blocked outgoing as soon as i connect the test clients in workshop to other network all works, so in my case not 100% sure this is an external issue

just a handy hint with Google create a new account specifically for the remote desktop usage that can stay logged in the background, the downside with Google is more susceptible to bandwidth issue etc, hence why i onle use it as a back, Remote Utilities is the best i have found, we even have a cooperate  [censored] account which apart from being horrendously expensive again is also bandwidth hungry

no agent running on my Viewer machine, i also use the Internet server for IDs, Running latest updates to Windows 10, there was an update recently , but after half my clients disconnected the other day and reconnected a few hours later, only my office client did not reconnect. all the clients are distributed around the country as they are used as playout machines for radio services. The remote units are running Windows 10 , but are locked down and do not receive and updates etc, they are all standalone with various connectivity methods, 4G dongles some on LAN etc, oh have Google remote desktop for them as a back door incase