Community
[ Closed ] viewer can't connect to host, all of a sudden
Links used in this discussion
Links used in this discussion
john kumpf,
User (Posts: 97)
Oct 27, 2026 11:59:25 pm EDT
Support level: Starter
I read the entire https://www.remoteutilities.com/support/kb/cannot-connect-using-internet-id-connection/
None of it applies. I was actively working on a remote host when it went down, so obviously, everything in that page was ok.
I am on previous version, v7.8.4.0. Please tell me that's not the problem.
I see that yesterday (10/26) you had an id-server problem and switched to a backup server.
https://www.remoteutilities.com/support/forums/forum1/3141-viewer-not-working-with-host-or-agent-connections
https://www.remoteutilities.com/support/forums/forum11/3136-remote-utilities-viewer-stopped-working
I suspect we have now switched back to the main sever.
Unfortunately I have already done ipconfig /flushdns and restarted the veiwer and same problem.
The viewer host says:
None of it applies. I was actively working on a remote host when it went down, so obviously, everything in that page was ok.
I am on previous version, v7.8.4.0. Please tell me that's not the problem.
I see that yesterday (10/26) you had an id-server problem and switched to a backup server.
https://www.remoteutilities.com/support/forums/forum1/3141-viewer-not-working-with-host-or-agent-connections
https://www.remoteutilities.com/support/forums/forum11/3136-remote-utilities-viewer-stopped-working
I suspect we have now switched back to the main sever.
Unfortunately I have already done ipconfig /flushdns and restarted the veiwer and same problem.
The viewer host says:
28-10-2026__03:57:46__888 Check ID Connection to internet-id error. Host: "id75.remoteutilities.com:5655". Exception class: "EIdConnectTimeout". Message: "Connect timed out.".
28-10-2026__03:57:56__897 Check ID Connection to internet-id error. Host: "id75.remoteutilities.com:443". Exception class: "EIdConnectTimeout". Message: "Connect timed out.".
28-10-2026__03:57:56__897 Check ID Connection to internet-id error. Host: "id75.remoteutilities.com:443". Exception class: "EIdConnectTimeout". Message: "Connect timed out.".
28-10-2026__03:57:56__897 Check ID Connection. Exit: "id75.remoteutilities.com:443".
28-10-2026__03:58:36__866 Check ID Connection. Connecting...: "id75.remoteutilities.com:5655".
john kumpf,
User (Posts: 97)
Oct 28, 2026 12:00:23 am EDT
Support level: Starter
FYI I posted the above at 11:58pm EST 10/27/2026.
john kumpf,
User (Posts: 97)
Oct 28, 2026 12:06:09 am EDT
Support level: Starter
Also, I can not check the status of the remote host because I am not physically at that location (which, I assume, is common when using this tool.)
Keith Hill,
User (Posts: 18)
Oct 28, 2026 12:31:43 am EDT
Support level: Pro
Same here, also starting tonight. A host I was actively working on dropped off and now can't register. The host log shows "Unable to connect to ID server. Address: id78.remoteutilities.com; Port: 443; Connect timed out" and also id75. id70, id71, id72, id75 and id78 all resolve to 172.241.164.247, and TCP 443 to that address times out from three different networks, including my own office, so it isn't local. Hosts already connected elsewhere are fine. A clean reinstall that generated a new ID gets assigned to the same pool and fails the same way.
Chris Guth,
User (Posts: 1)
Oct 28, 2026 1:04:50 am EDT
Support level: Free or trial
All of my computers are offline as well tonight.
Internet-ID: Unable to connect to ID server. Address: id75.remoteutilities.com; Port: 443; Connect timed out.(EIdConnectTimeout)
C:\Users\abcd>ping id75.remoteutilities.com
Pinging id.remoteutilities.com [172.241.164.247] with 32 bytes of data:
Reply from 172.241.164.247: bytes=32 time=70ms TTL=252
Reply from 172.241.164.247: bytes=32 time=70ms TTL=252
Reply from 172.241.164.247: bytes=32 time=70ms TTL=252
Reply from 172.241.164.247: bytes=32 time=70ms TTL=252
Ping statistics for 172.241.164.247:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 70ms, Average = 70ms
Internet-ID: Unable to connect to ID server. Address: id75.remoteutilities.com; Port: 443; Connect timed out.(EIdConnectTimeout)
C:\Users\abcd>ping id75.remoteutilities.com
Pinging id.remoteutilities.com [172.241.164.247] with 32 bytes of data:
Reply from 172.241.164.247: bytes=32 time=70ms TTL=252
Reply from 172.241.164.247: bytes=32 time=70ms TTL=252
Reply from 172.241.164.247: bytes=32 time=70ms TTL=252
Reply from 172.241.164.247: bytes=32 time=70ms TTL=252
Ping statistics for 172.241.164.247:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 70ms, Average = 70ms
Keith Evans,
User (Posts: 31)
Oct 28, 2026 1:56:17 am EDT
Support level: Plus
i also have lost connectivity, all my hosts showing offline.. correction just came back as i was typing
Edited:Keith Evans - Oct 28, 2026 1:57:30 am EDT
Conrad Sallian,
Support (Posts: 3297)
Oct 28, 2026 4:31:41 am EDT
Hello everyone,
Thanks for the reports and the logs, they helped.
Our public servers are working normally. A Host that went offline registers again on its own once its connection to the server goes through, as Keith saw, though on some networks this can take a while longer.
One heads-up: in the next few hours we'll be switching from our backup server back to our primary server, so some brief connectivity issues are possible. If a Viewer or Host machine shows offline afterwards, flushing the DNS cache on that machine resolves it. Open a command prompt and run
If a Host still shows offline tomorrow, please post its latest Host log lines here (with your Internet-IDs removed, since this forum is public).
Sorry for the trouble.
Thanks for the reports and the logs, they helped.
Our public servers are working normally. A Host that went offline registers again on its own once its connection to the server goes through, as Keith saw, though on some networks this can take a while longer.
One heads-up: in the next few hours we'll be switching from our backup server back to our primary server, so some brief connectivity issues are possible. If a Viewer or Host machine shows offline afterwards, flushing the DNS cache on that machine resolves it. Open a command prompt and run
ipconfig /flushdnsthen restart the Viewer (or the Host, from its tray icon).
It's not. The same timeouts were reported at the same time with 7.9.0.0, and the connections came back without any update.I am on previous version, v7.8.4.0. Please tell me that's not the problem.
If a Host still shows offline tomorrow, please post its latest Host log lines here (with your Internet-IDs removed, since this forum is public).
Sorry for the trouble.
Conrad Sallian,
Support (Posts: 3297)
Oct 28, 2026 5:04:41 am EDT
Hello everyone,
To keep everything about the Internet-ID servers in one place, we've opened a pinned topic: Internet-ID servers: status and issues. It has the latest status and what to do if your Viewer or Hosts show offline.
Please post any further reports there. We're closing this topic.
Thank you.
To keep everything about the Internet-ID servers in one place, we've opened a pinned topic: Internet-ID servers: status and issues. It has the latest status and what to do if your Viewer or Hosts show offline.
Please post any further reports there. We're closing this topic.
Thank you.
* Website time zone: America/New_York (UTC -4)