The SMC connects to my ALCATEL via "mock" Static IP setting as shown below: My second network is behind a SMC router (ip:192.168.1.254). I connect to the WAN via a Alcatel modem router (ip:10.0.0.254). I posted this earlier this morning to get some assistance, but I just found out that there's actually nothing wrong with my config, but due to a faulty RJ45.Īnyways I hope this post helps those who need assistance in a similar scenario. If you are running a viewer in 'listening' mode, where it accepts connections initiated by the server, it will listen for incoming VNC on port 5500. Most of the viewers, if given a display number larger than 99, will interpret it as a direct port number and will not add 5900. See the server's documentation for more details. The servers can be changed to listen on other ports if, for any reason, these are not suitable for you. Note that this is the HTTP port used for downloading pages and applets, but once the applet is running it uses 59xx for VNC just like any other viewer. In addition, VNC servers normally have a small and very restricted web server built in, which allows you to connect a browser to them and use the Java viewer. #VNC CONNECT THROUGH FIREWALL PC#So for most PC servers, the port will be 5900, because they use display 0 by default. The VNC protocol itself runs over this port. The most important one is 59xx, where xx is the display number. The exact port numbers depend on the VNC display number, because a single machine may run multiple servers. See below for information on the other port numbers used by VNC.Ī VNC server listens on two ports. So you could run WinVNC with a display number of 0 on machine snoopy, and with display 1 on machine woodstock, then set your router to send port 5900 to snoopy and 5901 to woodstock. If your internet access is through a router which does Network Address Translation, you may be able to configure the router to redirect particular incoming ports to particular machines. There's probably Java SOCKS support out there somewhere. It's a pity that Java within a browser doesn't automatically use SOCKS if the browser is configured to use it. It is straightforward, for example, to recompile the viewer source to include SOCKS support, or to make other special arrangements. Many modern firewalls will allow outgoing connections initiated from inside, so you can often access servers on outside machines. There is a good argument to be made for the fact that VNC is less of a security risk than X, so if your site doesn't allow X in or out it may still allow VNC. If you can configure these to include your VNC server, then you will be able to access it from anywhere in the world. Generally firewalls are designed to prevent incoming connections except to certain well-known machines and ports. It depends on your firewall, and whether you want to access a server inside your firewall from elsewhere, or a server outside your firewall from inside. Here's the section of the tightVNC FAQ on the issue: It's probably not the firewall in the broadband router that's the issue, but rather the NAT. You don't need 5800 if you don't use the web interface. You need to forward ports 5800 & 5900 for screen 0, the default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |