Benny Tucker's community posts

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.

A couple of questions:
1. When you say that you bypassed your router, do you mean that you opened a port for RU ?
2. Are both computers on the same network ? RU version WOL only works on the same network.

If you are connecting over VPN, try using the IP address instead of domain name. That has worked for me in the past.

Bill Mullen wrote:



Please consider adding a means to "ring" the remote computer - play a wav file or something to turn the users attention to the screen.

You could try this. Remote Execute "C:\windows\media\notify.wav". Or use whatever sound file you want. Only drawback is either you or person at remote has to close the wav player's window... :-) :-)

This might be a longshot, and there are several "if's", involved. But it might be worth a try if the conditions are met.
1. IF you use the RDP feature of Remote Utilities, then the remote computer at least has that capability.
The idea here is that you can use the native RDP server built into Windows. Which brings up IF #2.
2. IF you have used this feature in RU, then you would need to open a port in the remote computers router, since the RU host is not running. Ideally, you would know how to access this router over the web.
Then you could possibly telnet/SSH into the router to open the port. IF, you don't know the wan IP address to access the router, you could probably get this when your remotes post to your website. Most control panels for the web management allow for logging of all IP addresses that connect to your site, along with other details about the connection.
3. If there is anyone there that could possibly help you out, all you would need to do is get them to download the host from RU, and run it with default settings. On my remotes that wouldn't finish installation, I copied the host msi to the machine, then ran the msi, and it detected that a previous installation needed to finish first, I agreed to that, and it finished the install without problem.

That's about all I can offer. I Hope that it might be of use to you...
Benny

Thank You for your response Conrad. Everything is up and running now, and it's working GREAT !!!
Really love this powerful software package !!!

Hello Conrad;
First of all, let me say that I finally got everything working. However, it wasn't all smooth sailing. I guess I must be in the minority, but this upgrade for me was a struggle. Below, I'll describe what happened, and the solutions that worked for me.
1. The upgrade to 6.6.0.2 was flawless. All of my viewers, hosts, and server upgrades went smooth as silk. No problems whatsoever.
2. The following day, I tried upgrading to 6.6.0.3. That's when the wheels fell off.
On my main viewer machine "Windows 7", I tried installing the viewer. Got the errors described in another post. Following the directions in the other post, I tried to uninstall viewer using the Windows Control Panel Programs and Features. This didn't work, as Windows couldn't find the necessary uninstall files. I eventually uninstalled viewer using the uninstall viewer shortcut in the "All Programs"-"Remote Utilities-Viewer" folder, then manually deleting the config_4.xml file. Re-booted machine, then reinstalled viewer. Success !! EXCEPT, General Address book was there but was now empty..... Solved this by restoring a backup from day before... Thank You for this automatic backup feature. Viewer required complete re-configuration, including license key. I guess all of that was in the config file I deleted. OK, viewer is at this point operational, Full Control, File Transfer etc worked fine. Until....
3. Click on RDP file to open rdp connection... Would not work. Got more errors, couldn't open .rdp file.
Every computer in my address book was like this for RDP. Could not even open the file using MS RDP. Opened the files in notepad, and each and every one of my .rdp files were corrupted. Only the top 4-5 lines in the file were visible, and it looked like a foreign language instead of the usual parameters.
I just happened to backup the whole viewer folder before upgrading, in case I wanted to downgrade. At this point, I copied my backups back into the rdp folder. After trying to open another rdp connection, it corrupted that file instantly. I didn't click on any other rdp connections in viewer, until I could figure out what was going on. I finally figured out that the files were being corrupted, as soon as I right click on a connection and select "Properties". Didn't even have to go to the RDP tab. As soon as properties for that connection was selected, bang, the file was corrupted. The only work around I found for this, was to open the properties dialog for the connection, leaving that dialog up while I navigated to my backup, and copy/paste the file back into the rdp folder, then finally closing the properties dialog box. This finally got my RDP connections working, however, I had to do this for each and every one of my connections. Now I feel good about this particular viewer, except I had to do this whole procedure to my other  two viewers as well. They all did this exact same thing. One other Win 7 machine and 1 old XP machine.
4. Upd ated RU server, the only problem was, I got the errors about it needing to uninstall the previous version, but the Control Panel uninstall didn't work for that either. Uninstalled using the same procedure as for viewer. Not as painful, but I did have to use a different remote software to get at my RU server to do the work, as the server is in another location.
5. Several of my hosts would not completely install upgrade using the remote install tool. Again, another remote software was used to complete the uninstall-reinstall of the new version.
Finally, I got everything up and running smoothly again. I really do like the new viewer, more accurate online/offline status, search tool, and the ability to se t the connection type for double click in the viewer. This upgrade was nowhere near as easy as the previous upgrade, but I guess it might just be my setup, as I haven't seen any other posts in the forum talking about these problems.
Thanks again Conrad. Still love this software...

Thank You, Thank You, Thank You !!! That is awesome Conrad... Much appreciated !!!

Conrad wrote:

I can assure you that we are not greedy :) It's only that we cannot always implement all that we (and our customers) want as fast as we would like to. That's software development - it always takes more time than initially planned.

Thanks Conrad; You have a fine product, and the price it great !!!

Hello Conrad,
I have tried your suggestions above, and still no dice. It seems that no matter what I try, the parameter winposstr:s:0,1,300,70,1450,900, gets changed to default winposstr:s:0,1,0,0,1600,900, no matter how I try to save it. All other parameters remain unchanged. With a direct connection, I can click on the .rdp file itself and everything works correctly. It's only when I use the viewer to connect, that the values get overwritten. I can't figure out where the viewer is picking up the default values from. I know that the last two parameters "1600,900" is the screen resolution of the viewer computer.
Thanks Conrad for your help.