F5F Stay Refreshed Power Users Networks Connection issue with VNC not resolved.

Connection issue with VNC not resolved.

Connection issue with VNC not resolved.

O
omaroli
Junior Member
14
08-31-2023, 01:31 AM
#1
Hello everyone, I'm facing issues linking to my TightVNC server from my mobile device via AndroidVNC. My internal IP works without problems, but connecting with my external IP results in connection errors like "VNC connection failed" or "Connection refused." The external IP is tied to a DDNS hostname, which isn't working. I checked port availability online and it appears open, but FreePortScanner says it's closed on my internal IP. Since the port forwarding is set up through Sagecomm, could you help clarify what's happening there? Thanks!
O
omaroli
08-31-2023, 01:31 AM #1

Hello everyone, I'm facing issues linking to my TightVNC server from my mobile device via AndroidVNC. My internal IP works without problems, but connecting with my external IP results in connection errors like "VNC connection failed" or "Connection refused." The external IP is tied to a DDNS hostname, which isn't working. I checked port availability online and it appears open, but FreePortScanner says it's closed on my internal IP. Since the port forwarding is set up through Sagecomm, could you help clarify what's happening there? Thanks!

S
SladeWilsonnn
Junior Member
18
08-31-2023, 05:20 AM
#2
Confirm the port was sent accurately and the internal IP addressed correctly.
S
SladeWilsonnn
08-31-2023, 05:20 AM #2

Confirm the port was sent accurately and the internal IP addressed correctly.

O
OctoberKnight
Member
153
08-31-2023, 07:17 AM
#3
It's set up for my computer's IP address. The port isn't the usual 5900, which helps with security. I'm running out of creative ideas.
O
OctoberKnight
08-31-2023, 07:17 AM #3

It's set up for my computer's IP address. The port isn't the usual 5900, which helps with security. I'm running out of creative ideas.

R
rosie2435
Senior Member
475
08-31-2023, 08:25 AM
#4
Examine the firewall configurations.
R
rosie2435
08-31-2023, 08:25 AM #4

Examine the firewall configurations.

T
Thorry20
Junior Member
42
09-01-2023, 06:35 PM
#5
It wasn't that simple—both the firewall and antivirus were disabled via certain services. The issue I encountered was when trying to connect, and I couldn't find any results by searching online. Spoiler: it was a problem.
T
Thorry20
09-01-2023, 06:35 PM #5

It wasn't that simple—both the firewall and antivirus were disabled via certain services. The issue I encountered was when trying to connect, and I couldn't find any results by searching online. Spoiler: it was a problem.

D
Dyversxy_
Junior Member
34
09-03-2023, 08:16 AM
#6
VNC is a risky communication method, regardless of the port chosen. It’s wise to route it via SSH or a VPN. That’s just my opinion.
D
Dyversxy_
09-03-2023, 08:16 AM #6

VNC is a risky communication method, regardless of the port chosen. It’s wise to route it via SSH or a VPN. That’s just my opinion.