Benny Tucker's community posts

I had a similar experience myself. The fix for me was to open the properties of "C:\Program Files (x86)\Remote Utilities - Viewer\rutview.exe", and under the compatibility tab, make sure to check the box, "Run this program as an administrator. Fixed it for me. YMMV.

I just thought that I would post a couple of notes that someone might find useful. In Conrad's blog highlighting the new RU app, He mentioned that the bluetooth keyboards were not supported as of yet. I have found however, that if you click on the keyboard in the quick action menu, that you can type all you want in a normal Windows application. I have been invoking the keyboard fr om the quick action menu, and then minimizing the keyboard wh ere only the "F" and special keys are showing. That let's you have access to most of the normal desktop except the very bottom edge.
Also, it might be helpful for others to know that a bluetooth mouse also works very will in this app. I have found that the touch option in the quick action menu works best for this. It doesn't recognize right mouse clicks, but for all intents and purposes, it works great for pointing on the remote screen in this way.
Hope this helps someone.

WOW !!!
That is a beautiful upgrade. I just tried it on iPhone and iPad. What a major improvement....
Kudos to the RU Team. All the features I've tried so far works really well...

I have some machines that I do this same thing. What works for me is to use the auto-hide function of both Remote Utilities toolbar and also the RDP on the other machine.
When I want to log off the RDP session, I just position the cursor near top of screen outside of the area that the Remote Utilities toolbar would activate, but within the area that the RDP toolbar would activate.
Hope that makes sense !!

Hi Pauline,
You can add me to the list of users that cannot get the host install to an XP machine. Same results as the above responders. The Microsoft troubleshooter tool mentioned above, is for Windows 10-11.
Rolling back to 10.x.x.x solves the problem.

If both PC's are on the same network, I would try a direct connection using IP addresses instead of Internet ID. I only use the Internet ID for my PC's that are off site, and even then I usually try to set them up for direct connection if possible.
Hope that helps.

Good evening RU.
Just a couple of questions related to the Linux host.
1. I'm brand new to Linux, but I do have one machine with Ubuntu running at the moment.
My question is, can the Windows version of Viewer be used to connect to this machine, or does it have to be the Linux version? I tried this scenario last evening, and the Ubuntu host would show up in both my RU Server, and also in the viewer it showed as online, but not logged in.
As soon as I clicked on the connection to connect, the status would immediately change to offline.

2. The X11 protocol is not compatible with my version of Ubuntu, on my current older machine. The version of Ubuntu I have is the latest desktop version, but the computer it's installed on is Windows 7 era.
After enabling X11, it crashed Ubuntu, and the only way to get it back was to perform recovery actions to re-enable Wayland.
I'm trying to learn all I can about Linux. Just mostly wanted to know if the Win Viewer would play nice with the Linux host?
Thank You for your time!!
Benny

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.

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.

I don't know your setup, but I solved a similar problem with my networks by changing the network cards interface metric to a lower number that my other virtual adapters. I had been running OpenVpn on all my computers, and during initialization it would alter the routing tables. So, after setting my main network adapter to use the interface metric to 1, my WOL started functioning perfectly, even the "Using other Host" function works perfectly now. Hope that helps.

Edit: Also forgot to mention that one of the prerequisites for this to work within the same network is that it must be a direct connection.