7,649
edits
Changes
Jump to navigation
Jump to search
Ignoring the SSH tunnel worked fine: Connect to 192.168.2.202::5902 using either realVNC or the TightVNC client.
→Connection Issues
ufw status
Status: inactive
The localhost port seems to be open and listening just fine:
So, presumably, there must be something wrong with the tunnel itself.
'''Ignoring the SSH tunnel worked fine: Connect to 192.168.2.202::5902 using the TightVNC (or RealVNC, etc.) client.'''
===RDP===
