Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Cannot connect to my computer with UltraVNC from internet.


  • Please log in to reply
1 reply to this topic

#1 sjvirchow

sjvirchow

  • Members
  • 84 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Lincoln Nebraska
  • Local time:11:29 AM

Posted 14 September 2011 - 09:24 PM

Here's the situation. I've got a Cisco E2000 running Tomato which automatically updates DynDNS with my external IP Address, since it's dynamic.

I can use a loopback connection to connect, and I can connect from other computers on my LAN, but I can't connect using the hostname that I set up on DynDNS (xxxxxxxx.dyndns0-remote.com:5800)

I've configured Tomato to forward ports 5800 and 5900 to the IP Address associated with my computer on the LAN. (192.168.x.x), however every open port check website (canyouseeme.org) says that port 5800 and 5900 are both still closed, not open like they should be.

What am I doing wrong? Is it because the hostname on DynDNS is set to re-direct to my ISP's dynamically issued IP Address, and since my computer's IP is an internal IP address (192.168.x.x) it can't obviously re-direct properly?

Help!
Hardware: The parts of a computer that can be kicked.

BC AdBot (Login to Remove)

 


#2 sjvirchow

sjvirchow
  • Topic Starter

  • Members
  • 84 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Lincoln Nebraska
  • Local time:11:29 AM

Posted 14 September 2011 - 10:05 PM

Fixed. Turns out it was my software firewall blocking the ports.
Hardware: The parts of a computer that can be kicked.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users