Topic: PortForward Problems

[Byte]

Hi,

I'm having trouble setting up my portforwarding to allow access to vnc.

i installed the portforwarding rpm and setup the following

ext des 5900
des ip 192.x.x.x
des port 5900

and it doesnt work, i have look on here and found info but it doesnt seem to solve my problem, what am i doing wrong

thanks in advance for any help

Byte

[Terry Brummell]

If you are using your browser to try and access vnc make sure you forward port 5800 as well.  I have both ports forwarded and I can access via a browser or the vnc viewer.  
Remember, this must be tested from the WAN side of your SME, port forwarding does not forward on the LAN side.

Hope this helps,
Terry

[Byte]

ok thanks for pointers i was actually testing this from the lan side one question do i need the port opening as well as port forwarding?

again thanks for your input

Byte

[Terry Brummell]

Nope, just forward the port(s), the rest of it takes care of itself.

Terry

[Byte]

Terry im having quite bit of trouble here, heres how im setting it up

Ext des 5900

des ip 192.x.x.x (my internal machine with WinVNC App mode Running)
des port 0 (display :0 on internal machine)

then i go home and try  vnc into my machine at work using 192.x.x.x

is this right sorry if i sound stupid, have you got any  how-to's on this please


Thanks in advance for any help


Byte im stuck

[Serge Dutremble]

Remember that, as far as VNC is concerned, display 0 is equivalent to port 5900 (VNC Viewer) or port 5800 (Java client using web browser).

As far as SME and port forwarding are concerned, only the numbers 5900 and 5800 (for VNC display 0) must be used.  Configuring a port forwarding to port 0 is useless.

Also, remember that VNC is not excrypted if you use it this way.

I prefer (and recommend) to use the SSH port forwarding to get a tunnel and then connect using the host "localhost:0" for display 0.

Search the forums for instructions on how to do this (and much more) using a windows ssh client (putty is a very good one).

Serge.

[Byte]

ok will look into that thanks for your input Serge

Byte

[Terry Brummell]

Or you can use TightVNC, a more secure version of VNC, http://www.tightvnc.org

Terry


From their website:
Security and reliability fixes. Unlike the standard WinVNC, TightVNC Win32 server does not make it possible to grab plain-text passwords from the Properties dialog box. Also, a long-standing Win9x resource consumption problem of WinVNC is fixed in the TightVNC server.

[Terry Brummell]

Here it is in a nutshell:

1.  Using the Port Forwarding panel, forward External TCP ports 5800 & 5900 to the respective Internal Port and IP address of the machine running VNC.
2.  Make sure the machine running VNC is using Display 0.
3.  From an external internet connection, in your browser go to http://www.yourdomain.com:5800
3b.  If using just the VNC Viewer program, just enter the FQDN or External IP Adress
4.  Enter your Password (if so required) and go.

To test the copy of VNC internally, from another machine on the local LAN go to http://machineipaddress:5800

Hope this helped.

Terry

[Byte]

Hi,

Thanks for your time on this Terry i managed to get it workin on the web browser interface now.

Again thanks!

Byte