I'm relatively new to VNC and after playing around with it a little, I managed to have a friend succesfully log into a gnome session on my suse linux 9.0 machine on :1. However, now I'm trying to do the same thing in reverse - VNC to his windows XP machine from my Suse machine, but for some really silly reason, tightVNC doesn't know how to go out through a gateway on it's own - I've got to tell it how to do that ... (why?) Here's tighvnc's documentation on VNCviewer:

http://www.tightvnc.com/vncviewer.1.html

Well, so, I try to do: "vncviewer -via 192.168.1.1 <my friend's WAN IP>:0"
and I get:
"ssh: connect to host 192.168.1.1 port 22: Connection refused
vncviewer: Tunneling command failed: /usr/bin/ssh -f -L 5599:67.161.223.178:5900 192.168.1.1 sleep 20."

So what can I do? I don't have the slightest clue what the details of that error above means... Also, My friend and I both have routers, and we both have ports 5900-5910 fowarded. And it's a linksys router, so yes, 192.168.1.1 is the gateway IP.

Anyone know what I need to do to correct this?

I think this is your problem here. I don't use TightVNC, so I'm not exactly sure how it works, but it looks like it is trying to establish a ssh tunnel and then run VNC through that. However, it is trying to establish that ssh tunnel with your router, not your friends XP box.

Looking at the TightVNC page, I'm guessing that if you use your friends WAN IP address as the "gateway" that might allow the connection. So what I mean is:

vncviewer -via <my friend's WAN IP> <my friend's WAN IP>:0

Ok, found the issue.
I did try that option, but it couldn't seem to find my freind's WAN IP, just like when I simply did:
vncviewer <my friend's WAN ip>:0
BUT, I got that command to work simply by having my friend disable the windows XP firewall. Didn't need any of that gateway stuff after all. Thanks anyhow, it' looks like that's all it needed.