Benny Tucker's community posts

I can confirm the exact same problem that you have described. It's something to do with Windows 10/11. I cannot get it to work with anything newer than Windows XP. I have multiple networks in multiple loacations, and the only way to get it to work with the intermediate host is when waking the XP machine. All other machines in these networks just does not get the magic packet. Firewall maybe ? I don't know. I've tried firewall rules to allow the magic packets and it just doesn't work. I can send magic packets if I can log into another machine within the same lan and it works. Just not using the intermediate host option. Just won't work as advertised. I would like to know how to resolve this issue also.

This may be a shot in the dark, but what is the lease time for your DHCP server? If your modem is acting as the DHCP server, then your computer may be having trouble negotiating a new lease.

Also be sure to check under Server Configuration-Access and administration-Allow named pipes connection (local connection). Make sure it's checked...
Hope that helps !!
Benny

Ron, my best guess as to what happened has to do with the false positive anti-virus issues, as addressed in previous threads. I had a total of about 8 machines that Windows Defender and Security Essentials had quarantined. If you could get someone at the host machine to check the quarantine status of the rfusclient.exe file, and allow/restore it's operation, then restart the host or reboot the machine, you can probably save yourself a trip.
Hope that helps.
Benny

I actually have a similar setup with one of my machines. I have the viewer, host, and server all on this one machine. Works fine for me. Make sure that in your "host" settings for this machine, that you use an IP address of the machine itself under internet ID settings, custom server address. However, I have also opened the port in the router for this machine, so I am able to do a direct connection straight to the host whenever I'm at another location remoting into this machine.

Conrad, I have the same issues with Windows 10 machines. The only work around for this issue for me is to use Remote Desktop. I can log directly into a users desktop and not have to deal with the logon screen.
Using Full Control mode is out of the question with Windows 10 for me. One thing that does help with any version of Windows, if the user will allow it, is to adjust the performance parameters of Windows behavior. I turn off all "pretty effects and frills", such as fade windows in and out, annimations, slide open combo boxes, smooth scroll and other non essentials. Makes remote sessions much snappier.
Benny

I have the exact same issues. RDP for me is at minimum 5 times faster, sometimes up to 10 times faster than Full Control mode. I use both regularly, but with Full Control, I have to turn off the wallpaper and other extras, and then it still is slower that RDP. When I have several computers to work on at the same time, it's much easier to see the wallpapers, to help keep up with which computer I'm working on. Hopefully RU will find a way to speed up the screen re-draws, and fix the dropping connections as you mentioned. Otherwise, it works great !!!
Benny

Awe shucks. Remote Utilities does so many things well, I wouldn't quit using it if the ribbon behavior was changed back to the previous way. I just think it's so much easier for my work the way it works in the current version. Can't get rid of me that easy :-) :-)

Ron, I for one, prefer the way it works now. Sometimes in my list of connections I might have to do the same operation on multiple hosts. As it is now, I can just click down through my connection list and have each host ready to perform my tasks. Before, I would do as you say and click a connection, then click the connection type, click a connection, then click connection type, click........again, again, again. So, I really, really like the way it works now. Perhaps there could be a switch in settings to change the behavior on demand.
Benny

Yes, it is possible. I do it all the time. However, it will sometimes require heavy testing and configuration changes to make it work. I will try to get you started in the right direction.
First of all, what I use for sending the "Magic Packets", is available for download fr om Here.. If this is set up correctly, it works every time.
Next, most all of the information in Conrad's link above is correct, but there are a few things I would like to point out.
The article says that you cannot port forward the magic packet. This is untrue, as I have many computers in different networks across the internet, that I must wake up, and at the same time, not have every computer on the network wake up. You can set up a port forward for each computer using a different port number, and not have to trick your routers into sending a packet to all computers.
If your computer truly is S5 capable, then making sure it is turned on in BIOS, and for the network card in the computer. Also, most computer network cards require a wired connection for this to work. In most cases, wireless connection will not work, unless your computers have WWOL capabilities.
In the case of port forwarding the ports for WOL, one of the most often things overlooked, is the ARP table in the router itself. Most routers today will clear out the ARP table of IP addresses that it senses in no longer online. Usually this happens within a few minutes of turning off computer, up to an hour or more. To get around this, you must set permanent ARP mappings of IP addresses to MAC addresses. This is usually accomplished through a telnet/ssh utility. The problem here is if the router loses power or is rebooted, you must telnet/ssh back in and reset the permanent mappings. I use a script for this and it is not overly complicated. The commands go typically like this:
arp -s xxx.xxx.xxx.xxx yy:yy:yy:yy:yy:yy wh ere x is IP address, space, MAC address. You can find out the exact syntax by telnet/ssh into router and typing something like ARP /?
A dynamic IP address hostname is a MUST, unless you have static WAN IP addresses.
The software I linked to above, can be used for testing by installing it on remote computer, and set it to receive on the port that you're pointing to.  It's usually best to get it to work on the local network first, that lets you know if your computer is configured correctly to start up with WOL. Then move on to WAN and configure for that.
I hope this helps, and I'm sure I left some details out. But I will try to help you get this going.