ok. i have been using ultravnc for well over a year now and i never had a problem connecting or ANYTHING. i recently moved and the router used is different. however, port forwarding and firewall exceptions were the same.
since i moved i have not been able to use VNC from outside my network. i can connect fine if i use my LAN address 192.168.x.xxx whatever it may be. BUT when i try to connect using my WAN IP address i cant connect to the server.
here are some details:
router - DI 514 wireless although i am wired.
win XP SP 2
ULTRAVNC RV19 (whatever the newest one is)
also, i have tried DMZ'ing my PC but it is to no avail.
i have tried using both the server and HTTP connections from both my PC and one outside the network. nothing.
PLEASE help! i have been unable to use this for the last 2 months and have just about given up on it.
i also went ahead and tried another version of VNC...VNC. and it didnt work either.
thanks in advance...
just tried disconnecting the router and pluggin straight into the modem. worked fine. what i dont get is that the router will allow me to forward ports for other programs and works just fine. should i try changing the ports? is there something about this particular router? i can take screenshots of my router config and email them to anyone that wants to help me. i would rather not have to buy a new router but if i have to i have to. it is a pretty popular one so maybe someone else has had the same problems.
Celebrating the 22th anniversary of the UltraVNC: https://forum.uvnc.com/viewtopic.php?t=38031
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
bear with it (unconnectable)
Seems you already know where the link is that needs to be fixed.. its your router. Since you can plug in directly and it works fine.. that means XPSP2 isnt the culprit... this time lol.
This is what I found on the DI 514
On this router you must enable the "Virtual Server" ports.. but sounds like you got that working for other apps but I could be wrong and you are using the port triggering instead...
http://www.portforward.com/dlink/di-514 ... arding.htm
Firewalling could be disabling the port you are using for outbound connections ... check out - http://firewalling.com/dlink/di-514-ipfilter.htm
Since you know its your router to check the port and see if it is "open" you can use -
https://grc.com/x/ne.dll?bh0bkyd2
and specify the port you wish to check if it isnt the default.
have fun
This is what I found on the DI 514
On this router you must enable the "Virtual Server" ports.. but sounds like you got that working for other apps but I could be wrong and you are using the port triggering instead...
http://www.portforward.com/dlink/di-514 ... arding.htm
Firewalling could be disabling the port you are using for outbound connections ... check out - http://firewalling.com/dlink/di-514-ipfilter.htm
Since you know its your router to check the port and see if it is "open" you can use -
https://grc.com/x/ne.dll?bh0bkyd2
and specify the port you wish to check if it isnt the default.
have fun
-
Guest
ports are open
i used the port scanner from GRC that you provided and it states that the ports are indeed open. when checking 5800-5901 it states that the only two ports of those checked are 5800 and 5900. i have it set to the default port numbers.
i dont think it will help but ill try setting everything up for a different series of ports and see if i have better luck...is there any specific ones you think i should try?
thanks again for the info you have given me so far. i really appreciate it.
i dont think it will help but ill try setting everything up for a different series of ports and see if i have better luck...is there any specific ones you think i should try?
thanks again for the info you have given me so far. i really appreciate it.
Solicited TCP Packets: RECEIVED (FAILED) — As detailed in the port report below, one or more of your system's ports actively responded to our deliberate attempts to establish a connection. It is generally possible to increase your system's security by hiding it from the probes of potentially hostile hackers. Please see the details presented by the specific port links below, as well as the various resources on this site, and in our extremely helpful and active user community.
Unsolicited Packets: PASSED — No Internet packets of any sort were received from your system as a side-effect of our attempts to elicit some response from any of the ports listed above. Some questionable personal security systems expose their users by attempting to "counter-probe the prober", thus revealing themselves. But your system remained wisely silent. (Except for the fact that not all of its ports are completely stealthed as shown below.)
Ping Reply: RECEIVED (FAILED) — Your system REPLIED to our Ping (ICMP Echo) requests, making it visible on the Internet. Most personal firewalls can be configured to block, drop, and ignore such ping requests in order to better hide systems from hackers. This is highly recommended since "Ping" is among the oldest and most common methods used to locate systems prior to further exploitation.
Port
Status Protocol and Application
5800
OPEN! Unknown Protocol for this port
Unknown Application for this port
Solicited TCP Packets: RECEIVED (FAILED) — As detailed in the port report below, one or more of your system's ports actively responded to our deliberate attempts to establish a connection. It is generally possible to increase your system's security by hiding it from the probes of potentially hostile hackers. Please see the details presented by the specific port links below, as well as the various resources on this site, and in our extremely helpful and active user community.
Unsolicited Packets: PASSED — No Internet packets of any sort were received from your system as a side-effect of our attempts to elicit some response from any of the ports listed above. Some questionable personal security systems expose their users by attempting to "counter-probe the prober", thus revealing themselves. But your system remained wisely silent. (Except for the fact that not all of its ports are completely stealthed as shown below.)
Ping Echo: PASSED — Your system ignored and refused to reply to repeated Pings (ICMP Echo Requests) from our server.
Port
Status Protocol and Application
5900
OPEN! Unknown Protocol for this port
Unknown Application for this port
maybe that will help a bit?
Unsolicited Packets: PASSED — No Internet packets of any sort were received from your system as a side-effect of our attempts to elicit some response from any of the ports listed above. Some questionable personal security systems expose their users by attempting to "counter-probe the prober", thus revealing themselves. But your system remained wisely silent. (Except for the fact that not all of its ports are completely stealthed as shown below.)
Ping Reply: RECEIVED (FAILED) — Your system REPLIED to our Ping (ICMP Echo) requests, making it visible on the Internet. Most personal firewalls can be configured to block, drop, and ignore such ping requests in order to better hide systems from hackers. This is highly recommended since "Ping" is among the oldest and most common methods used to locate systems prior to further exploitation.
Port
Status Protocol and Application
5800
OPEN! Unknown Protocol for this port
Unknown Application for this port
Solicited TCP Packets: RECEIVED (FAILED) — As detailed in the port report below, one or more of your system's ports actively responded to our deliberate attempts to establish a connection. It is generally possible to increase your system's security by hiding it from the probes of potentially hostile hackers. Please see the details presented by the specific port links below, as well as the various resources on this site, and in our extremely helpful and active user community.
Unsolicited Packets: PASSED — No Internet packets of any sort were received from your system as a side-effect of our attempts to elicit some response from any of the ports listed above. Some questionable personal security systems expose their users by attempting to "counter-probe the prober", thus revealing themselves. But your system remained wisely silent. (Except for the fact that not all of its ports are completely stealthed as shown below.)
Ping Echo: PASSED — Your system ignored and refused to reply to repeated Pings (ICMP Echo Requests) from our server.
Port
Status Protocol and Application
5900
OPEN! Unknown Protocol for this port
Unknown Application for this port
maybe that will help a bit?
hell what you just showed me means -
A) port 5800 for the web viewer is open , but your router is set up to not respond to icmp echos.. good thing
and
B) port 5900 for the application viewer is open.. same as before on the router.
hmm
How are you trying to connect to this...?? what computer is trying to connect to it and what is its network configuration? Your server side is set up and looks like its raring to go.
I guess I dont know where you are located but I can try to help you if you like... I use skype and my email is kevin@kevinhodgeDOTcom.. change the DOT to a .
If you want I can try to help you and we can use skype to talk back and forth.. your call
A) port 5800 for the web viewer is open , but your router is set up to not respond to icmp echos.. good thing
and
B) port 5900 for the application viewer is open.. same as before on the router.
hmm
How are you trying to connect to this...?? what computer is trying to connect to it and what is its network configuration? Your server side is set up and looks like its raring to go.
I guess I dont know where you are located but I can try to help you if you like... I use skype and my email is kevin@kevinhodgeDOTcom.. change the DOT to a .
If you want I can try to help you and we can use skype to talk back and forth.. your call