VNC Issues

[shadow_man]

Hi guys need help vncing into my home box from the office - router at home is Netgear DG834G.

netstat -an |find /i "listening"

TCP 0.0.0.0:5500 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5800 0.0.0.0:0 LISTENING

Those are the ports for vnc are they not and both are open are they not?

Router is setup to forward all inbound traffic on those ports to 192.168.0.4 - my windows box running tightvncserver, when I connect to my router from home I can login/edit settings etc, but when I try tightvnc in to the router ip i get a "failed to connect to server".

What am I missing here?

Thanks
J

 

[Azrael]

First things first, do you have a password setup on your VNC server? You can't connect without one begin configured.

 

[Peon]

Manually set port TCP 5900 and make sure no encryption plugins are used. What VNC server software are you using?


Peon

 

[shadow_man]

I am using tightvnc for both server and client - password is set....

J

 

[Azrael]

I am using tightvnc for both server and client - password is set....

J

Ok then, just confirm your settings on your router to the ones on this page.
TighVNC normally defaults to port 5900, but you can change it in the setup.

 

[proximiti99]

I'm not sure if it's gonna work the way you expect... I've had a similar setup, but when I connect to my office PC it takes forever to display the contents, even with a 4MB line ;(

 

[shadow_man]

Have done that - thats the guide I used - cant seem to see any log on my router of vnc trying to connect other than some idiot trying a DOS attack against my vista box on friday.

Cant see work blocking those ports as you can see above they seem to be open on my work machine, not sure about works routers - dont have access - but they run realvnc and there doesnt seem to be an issue....

Thanks
J

 

[ghalied]

Cant see work blocking those ports as you can see above they seem to be open on my work machine, not sure about works routers - dont have access - but they run realvnc and there doesnt seem to be an issue....

Thanks
J

Try a pathping and tracert and check the last leg, where does the connection fail then go from there.

 

[shadow_man]

Do I need to enable "respond to ping on internet wan port" for vnc?

with regards to a tracert - you mean from my work machine to my home box?

 

[Peon]

You need to port forward TCP 5900. By the way, Linux or Windows?

 

[shadow_man]

Windows box at work, windows / linux box at home

Xp on both home/work / Kubuntu on home linux box.

Xp box at home has .04 and kubuntu box .06 - have setup portforwarding to .04 for 5500/5800/5900 to forward .04 (home win box) - do I need to add any static routing other than the firewall/services tabs?

Port forwarded 5900/5800/5500 - but i dont see anything in router logs about work pc even attempting connection - maybe ive done something wrong i doubt it could post screenies if that would help.

http://mybroadband.co.za/photos/showphoto.php?photo=2637
http://mybroadband.co.za/photos/showphoto.php?photo=2638

J

 

[Peon]

And the firewall on the individual computers is also disabled?

 

[shadow_man]

Yeah, thing is in my logging on router I cant even see any attempt to vnc in - nothing.

So its weird...
J

 

[Avatar_5]

Have you tried another client? I had similar problems, using TightVNC Portable from work, and every time I tried to connect it threw the port number suffix away... Downloaded RealVNC and it worked first try.

 

[shadow_man]

Hmmm just tried realvnc client from work to connect to my home tighvnc win xp machine but it timed out - can x client not work with y server or ?

J

 

[ghalied]

I'd suggest keeping the client and server the same just to eliminate incompatability, your work router or firewall appliance might not allow traffic to the outside on those ports.