How can I set up remote assistance software without configuring firewall rules?

Click For Summary
SUMMARY

The discussion centers on setting up remote assistance using VNC without requiring users to configure firewall rules. The user initially attempted to connect using TightVNC and UltraVNC but faced issues due to incorrect connection directionality. The solution involved using the correct command for reverse VNC connections on the Debian box: xtightvncviewer -encodings "hextile copyrect" -listen -encoding tight -compresslevel 9 -quality 0, while running the uVNC Single Click server on the Windows VM. This setup successfully established a reverse connection, allowing remote control without firewall configuration.

PREREQUISITES
  • Understanding of VNC (Virtual Network Computing) protocols
  • Familiarity with IPTABLES and firewall configurations
  • Basic knowledge of Debian and Windows operating systems
  • Experience with remote desktop applications like UltraVNC and TightVNC
NEXT STEPS
  • Research "VNC reverse connection setup" for detailed guides
  • Learn about "IPTABLES configuration for remote access" to enhance security
  • Explore "Remote Desktop Viewer on Debian" for alternative remote access methods
  • Investigate "UltraVNC Single Click" for simplified remote support solutions
USEFUL FOR

This discussion is beneficial for IT support technicians, system administrators, and anyone seeking to implement remote assistance solutions without requiring end-user firewall configurations.

Routaran
Messages
447
Reaction score
94
Hello,
I'm trying to find a way to allow people to send me remote assistance requests so I can control their computer but without having them first configure firewall rules on their end. The simplest solution seems to be to setup a vnc server on my end, configure my firewall rules appropriately and then have the other end "call me"

From what I have read, this should be fairly simplistic. I'm supposed to just run some kind of vncviewer in listen mode and then the other side simply types in my ip address.
To test, I setup a Windows7 VM on my debian box. Downloaded the UltraVNC viewer on that system. Connectivity and Firewalls aren't the issue. I've temporarily set my IPTABLES default policy to accept and I've killed the firewall service on my windows VM box. Both devices can ping each other.

Then on my debian box, i first tried to use tightvnc
From what I read, the following command is what was supposed to use
Code:
xtightvncviewer -encodings "hextile copyrect" -listen

When i tried to initiate a connection from my windows vm using the VNC viewer in uvnc's single click package.
I supply my debian box's IP address with the default port but the vncviewer simply sits there and indicates that no data is being exchanged between client and server. I am unable to see or control the VM. When I terminate the listener process on my debian box, the windows vm says "other side gracefully closed connection"

Another suggestion I saw was to use the Remote Desktop Viewer application on debian in listen mode. On Debian side, the Remote Desktop Viewer application's window goes dark when I attempt a connection but the result is still the same. The connection window on the VM shows that no data has been exchanged and I cannot control or view the remote system.

I was wondering if there was a guide or an clear explanation on how to get this to work. I would appreciate some help

Cheers,
Routaran
 
Computer science news on Phys.org
I was able to resolve the problem. Monumentally stupid move on my part.
Normal VNC connections are viewer -> server
reverse VNC connections are server -> viewer -listen

What was I doing?
viewer -> viewer -listen

sigh. Little embarrassing, but it's working correctly now.
This is what I did to get it to work, so others don't make the same mistake I did.

On my debian box
xtightvncviewer -encodings "hextile copyrect" -listen -encoding tight -compresslevel 9 -quality 0

On my windows box, download uVNC Single Click from (http://www.uvnc.com/downloads/single-cl ... loads.html)
I ran winvnc.exe (the server) supplied a different VNC & View-only VNC passwords (you need some password, doesn't matter what)
Then, right click on the VNC tray icon and select add new client. Provide the IP/hostname for your listening box and connect!

Reverse connection established!
 
Glad you have it working. :)
 

Similar threads

  • · Replies 8 ·
Replies
8
Views
3K
  • · Replies 3 ·
Replies
3
Views
2K
  • · Replies 1 ·
Replies
1
Views
5K
  • · Replies 8 ·
Replies
8
Views
6K
Replies
1
Views
2K
Replies
2
Views
3K