Create a free Team What is Teams? Learn more. Ask Question. Asked 5 years, 5 months ago. Modified 1 year, 5 months ago. Viewed times. Didn't find any documentation on the topic. Improve this question. Andi Andi 21 4 4 bronze badges. Add a comment. Sorted by: Reset to default. Highest score default Date modified newest first Date created oldest first. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. I have a computer running TightVNC server.
It is on my home network. The computer it is installed on has a locally static ip address I am able to connect to this vnc server from my home network fine, but unable to connect from outside my network using the IP address that I see at www. I have forwarded port and to ip address But if I use canyouseeme. Lastly, you may want to double check that you have forwarded the correct protocol, I can't remember if it is TCP or UDP that is needed, but if you have one - try the other or both!
You need to use the IP address of your modem. Your router does address translation that sees your I do not know exactly how to set up TightVNC, but I do know that you need to be using your public address and not a private IP address.
Hope this gets you going in the right direction. According to this , you need to forward a as well. The IP you listed is assigned by the router. Instead of attempting to access this address, you need to get the IP address that you're router is assigned by the ISP. My IP address is Another solution to your problem would be to sign up for a domain name using DynDNS. What this allows you to do is access your home network using something like MyDomain. It is much easier to remember a name you came up with than those silly useless numbers.
I just tried canyouseeme. So it seems like a good tool. If it's saying your ports are still closed, your ports are still closed. This could be due to your ISP, or any device in your connection path. It could also be due to your VNC server not running, so make sure it's running before testing. Doesn't VNC add the display number to the port you select? The first display number is 1. Been awhile since I messed with VNC but just a thought.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Why can't I connect to my VNC server from outside my network? Ask Question. Asked 12 years, 6 months ago.
Modified 7 years, 4 months ago. Viewed 64k times. I am running Windows 7. Any suggestions? Improve this question. Arjan Did your ISP block ? You might want to check with them. Or try other ports. Are you using the TightVNC viewer or are you using the web based interface?
Is there anyway to do show the real IP in the titlebar? Improve this question. Add a comment. Sorted by: Reset to default. Highest score default Date modified newest first Date created oldest first. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Time to get on trend. Best practices to increase the speed for Next. Related 1. Hot Network Questions.
What I would like to do is start vncserver virtual-mode and get an IP linked to eth0 , but it automatically chooses wlan0. Interface "UP" means interface should have valid ip and if its ethernet interface then other end of ethernet wire should be connected to make link UP. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Learn more. Ask Question. Asked 5 years, 5 months ago. Modified 1 year, 5 months ago. Viewed times. Didn't find any documentation on the topic. Improve this question. Andi Andi 21 4 4 bronze badges. Add a comment. Sorted by: Reset to default. Highest score default Date modified newest first Date created oldest first.
Re: tightvnc not working with static ip address with dinamic IP. Re: tightvnc not working with static ip address Just something to take a look at It's easy to overlook or mis-configure one or the other. Also, although it should not make a difference with modern versions of almost any OS I would generally do a reboot after changing from dynamic to static addressing or vice versa to be certain that the local dns resolver cache and anything else is cleared.
HTH, Tony. See my previous post. Re: tightvnc not working with static ip address with static IP. With both static and dynamic try the following: ping -c 1 hometsa-comp Good luck. Re: tightvnc not working with static ip address static IP. Page 1 of 2 1 2 Last Jump to page:. Bookmarks Bookmarks Digg del. All times are GMT The time now is You will see a window allowing to choose which server to connect to. After entering the host name or its IP address and optionally a display number , choose "Connect".
On successful connection, you will be prompted for your password, and if the entered password is correct, finally you should see the remote desktop. Alternatively, you can start the viewer in the listening mode, by using the correspoding button in the "New Connection" window. In the "New Connection" window, you can use built-in context help. To get help on using a particular control, first click small question button in the window title bar, then click on that control.
Another way to obtain context help is to press F1 key while the keyboard focus is in the corresponding control. The VNC servers also contain a small Web server. If you connect to it with a web browser, the Java version of the viewer will be downloaded automatically, allowing you to access the remote desktop.
If you want to be able to access your computer after the reboot, make sure you're running WinVNC as a service, not in the application mode. This is a limitation that may be solved in future versions. In this case, old binaries will be replaced by the new ones during the reboot, and there will be no need to re-install the service. Please note that the installer should show you the reboot prompt at the end of the installation, otherwise you probably selected wrong installation directory.
There is a number of things that can prevent the machine to reboot correctly, and that can cause losing the control over the computer. Mouse over the icon shows IP addresses. Hint showing that TightVNC is running as a system service. Icon is shown in inverted colors when viewers are connected. Red border indicates that new client connections are disabled.
Hint showing the reason for disabling client connections. Using context help.
Below image shows 2 IP's (eth0 & wlan0) to access machine via VNC from. Image shows that there are 2 ip's(eth0 and wlan0) to access same. Answer for TightVNC versions 2.x: Open TightVNC configuration, choose Server tab, uncheck "Show icon in the notification area", press Ok. To show the icon. Moving the mouse over this icon shows the server mode and the IP address of the machine (which can be entered in the remote viewer to access this server).