Pepa Kokes's community posts

TBH, I would rather not break my current viewer settings :-). If you can confirm that the contents of "%APPDATA%\Remote Utilities Files" folder is all that I need to recover, I will try tomorrow (time permitting).

However, I think network issues are highly unlikely here, at least in the sense you probably mean them - I am using a set of direct connections over an SSL tunnel, and the tunnel has been tested and retested multiple times and is working perfectly. Plus, if it *was* a network problem, the host's callback connections window should not display "connected"...

In fact, I am completely baffled by the need of the hosts to actually provide *any* callback port. Obviously, the hosts are connecting to the viewer, but they are only connecting to one specific IP address and one specific port. They don't have any need for a local port setting, as any traffic should go over the connection they initiated.

Hi! I would appreciate an update to the "Callback connection"help page ( https://www.remoteutilities.com/support/docs/callback-connection/ ): While I got my first callback connection up easily, the second (to the same master machine) took several hours to get working. I checked and rechecked the master settings for both connections as well as the slave settings, but I couldn't get it to work - the second slave would connect to the master machine (and its Callback connection list said so), but I couldn't control the machine from the master. It turns out that on the second connection, the callback port must be different than that of the first connection. I don't see why - servers are able to handle a number of requests on the same port at the same time, but Remote Utilities require that the ports be distinct. When I finally figured it out, the second callback connection started to work immediately.