Community

Hello:

Our long running Windows 10 installation had a power failure.
The four computers powered down, and restarted,
probably doing windows updates on the way back up.

The machines have been holding steady at version 7.1.7.0
Two of the machines came up fine and the HOST service is working fine,
I can connect to them.

Two others are reporting "cannot connect to server".  They have internet connectivity
confirmed by running a browser successfully to the web.
On one of these, I obtained a new Internet ID, but using this did not fix the connection to the
public server.

The IDs of the Hosts that cannot connect with your server are:
377 471 749 464
and
810 974 331 401  (brand new ID)

The IDs of the machines that are working are:
428-254-475-633
and
380-689-632-448

We have not seen a windows update trip this all up, but it is possible.
Could you check your side and see if those IDs have made attempts to connect?
Thanks!

For some reason, I have this issue regularly after a Windows Update. The only way to resolve the issue, for me anyway, is to have another remote access software installed, login, run, services.msc and restart the Remote Utilities -Host service. If you don't have another remote access software installed, perhaps you could talk someone through the process that is onsite.
Hope this helps.

Hi thanks for the tips.
Can you clarify what you mean by
"is to have another remote access software installed"
Do you mean re-install the host software?

Seems then Remote Utilities folks should have some sort of help item in their list of "how to repair your installation after a Windows update"

Hi Pauline.
You've been at this for a long time!

We have an ongoing operation and I prefer to hold my working installation steady at working versions unless required by your infrastructure.  As I said, two other machines are operational, these are at the 7.1.7.0 revision. So it can't necessarily be the version.

Can you confirm if the IDs identified as not working have accessed the servers and got rejected?

Thanks

The machines are in a school that we don't have access to until Monday.
So I'm hoping that this is a problem on the public server side and will be resolved
on your end so it comes up and just starts working again...
(this has been the case in the past)
DC

Ok Douglas, I understand. What I meant was having a secondary remote software to access the machines in question. A couple of ideas to bounce around if you have access to the router at the school. You could temporarily open a port for the native RDP protocol, if by chance the RDP service is running on those machines, then login and do as I mentioned earlier.
Another option, if you can log into one of the machines that are up and running, you can run Services.msc on that machine, then on the action tab, select "Connect to another computer". If you can get that to load the services for the offline machine, then you can turn on the Remote Utilities - Host service.
Hope that helps.

What would be your theory on why two other rather identical computers are functioning with the same existing installations?
You believe they didn't do the same windows update that the others did?
I HATE having to run around and update all the machines to match unnecessarily.