Hi all! I'm new to SuSE and I'm loving it! At work I want to be able to VNC into my machine at home. However, the only ports that are open to the outside world are 80 and 22. I would like to keep port 22 reserved for ssh and make port 80 reserved for VNC connections. My question is it possible to set up a secure connection to my machine at home via VNC on port 80? If so how would one set up VNC to connect via a secure connection on port 80? Thanks in advance! Jay
On 7/12/05, Jay Paulson
Hi all!
I'm new to SuSE and I'm loving it! At work I want to be able to VNC into my machine at home. However, the only ports that are open to the outside world are 80 and 22. I would like to keep port 22 reserved for ssh and make port 80 reserved for VNC connections. My question is it possible to set up a secure connection to my machine at home via VNC on port 80? If so how would one set up VNC to connect via a secure connection on port 80?
Thanks in advance! Jay
No need to use 80. What I do is to tunnel the VNC session over ssh.
From linux box - use -L option. From win/putty - there is configuration for tunnels.
So, forward any local (at work) port to the right remote port (at home), then set your VNC client to connect to the forwarded local port. Cheers Sunny
Op dinsdag 12 juli 2005 23:30, schreef Jay Paulson:
I'm new to SuSE and I'm loving it! At work I want to be able to VNC into my machine at home. However, the only ports that are open to the outside world are 80 and 22. I would like to keep port 22 reserved for ssh and make port 80 reserved for VNC connections. My question is it possible to set up a secure connection to my machine at home via VNC on port 80? If so how would one set up VNC to connect via a secure connection on port 80?
Thanks in advance! Jay
Use NX, it is easy to setup and creates a tunnel trough ssl. SUSE comes with FreeNX and the client can be downloaded from http://www.nomachine.com Once used to NX you won't go back to vnc! -- Richard Bos Without a home the journey is endless
On Wednesday 13 July 2005 00:03, Richard Bos wrote:
Op dinsdag 12 juli 2005 23:30, schreef Jay Paulson:
I'm new to SuSE and I'm loving it! At work I want to be able to VNC into my machine at home. However, the only ports that are open to the outside world are 80 and 22. I would like to keep port 22 reserved for ssh and make port 80 reserved for VNC connections. My question is it possible to set up a secure connection to my machine at home via VNC on port 80? If so how would one set up VNC to connect via a secure connection on port 80?
Thanks in advance! Jay
Use NX, it is easy to setup and creates a tunnel trough ssl. SUSE comes with FreeNX and the client can be downloaded from http://www.nomachine.com
Once used to NX you won't go back to vnc!
Sorry for stealing the thread, but.... I could never get NX to work. can you give us a Step by step setup? Jerry
-- Richard Bos Without a home the journey is endless
Op woensdag 13 juli 2005 06:58, schreef Jerry Westrick:
Sorry for stealing the thread, but....
I could never get NX to work. can you give us a Step by step setup?
What have you done, to get it to work? Which suse version, NX version. Where did you get it from, etc. -- Richard Bos Without a home the journey is endless
Use NX, it is easy to setup and creates a tunnel trough ssl. SUSE comes with FreeNX and the client can be downloaded from http://www.nomachine.com
Once used to NX you won't go back to vnc!
Sorry for stealing the thread, but....
I could never get NX to work. can you give us a Step by step setup?
I actually got it working on my SuSE machine and I can connect to it from my Windows box. I can't seem to connect to it from my Mac OSX box. :( Setp-by-Step 1) Download the rpm from www.nomachine.com or it should be in your package manager in SuSE (that's where I found it. It's a couple versions back and maybe what's causing my current problems). 2) Install the rpm 3) Run nxsetup --install --clean --skip-nomachine-key 4) Run nxserver --aduser <username> 5) Run nxserver --passwd <username> 6) Download the client and install on your remote machine. 7) Follow instructions and make sure you choose SSL encrypt on all data transfer option. 8) Connect to your remote machine. If you don't want to carry a key around with you make sure to install with the --skip-nomachine-key. I didn't do this the first time I set things up and it gave me a ton of headaches. I must have uninstalled and reinstalled everything like 5 million times because I couldn't find any documents on this stuff. Hope that helps!
On Tuesday 12 July 2005 05:30 pm, Jay Paulson wrote:
Hi all!
I'm new to SuSE and I'm loving it! At work I want to be able to VNC into my machine at home. However, the only ports that are open to the outside world are 80 and 22. I would like to keep port 22 reserved for ssh and make port 80 reserved for VNC connections. My question is it possible to set up a secure connection to my machine at home via VNC on port 80? If so how would one set up VNC to connect via a secure connection on port 80?
Thanks in advance! Jay
Why bother with vnc...? Why not set ssh up on a high port where no one should be able to find it and then ssh into your machine. Works well without more than a minutes worth of effort.
On Tuesday 12 July 2005 05:30 pm, Jay Paulson wrote:
Hi all!
I'm new to SuSE and I'm loving it! At work I want to be able to VNC into my machine at home. However, the only ports that are open to the outside world are 80 and 22. I would like to keep port 22 reserved for ssh and make port 80 reserved for VNC connections. My question is it possible to set up a secure connection to my machine at home via VNC on port 80? If so how would one set up VNC to connect via a secure connection on port 80?
Thanks in advance! Jay
Why bother with vnc...?
Why not set ssh up on a high port where no one should be able to find it and then ssh into your machine. Works well without more than a minutes worth of effort.
I can only get out from work via port 22 or port 80. So setting ssh up on a high port wouldn't work b/c I wouldn't be able to connect! doh! :)
On Tuesday 12 July 2005 04:17 pm, Jay Paulson wrote:
I can only get out from work via port 22 or port 80. So setting ssh up on a high port wouldn't work b/c I wouldn't be able to connect! doh! :)
Most firewalls will let outgoing ports be established. It is only the incoming that gets blocked. I'm in a very high security facility and I can connect outgoing to anything, just not incoming. B-)
On Tuesday 12 July 2005 04:17 pm, Jay Paulson wrote:
I can only get out from work via port 22 or port 80. So setting ssh up on a high port wouldn't work b/c I wouldn't be able to connect! doh! :)
Most firewalls will let outgoing ports be established. It is only the incoming that gets blocked. I'm in a very high security facility and I can connect outgoing to anything, just not incoming.
B-)
I guess I'm at a backwards company because the network admin has all the out bound ports blocked except for ports 80 and 22.. hence the headache I have trying to do my job sometimes. That's why I would love to be able to VNC via port 80 to my machine at home and pull up a browser and do whatever it is I need to do. The one thing I want is to make sure that my VNC session is encrypted over the net. =) jay
On July Tuesday 12 2005 6:33 pm, Jay Paulson wrote:
On Tuesday 12 July 2005 04:17 pm, Jay Paulson wrote: <snip>
I guess I'm at a backwards company because the network admin has all the out bound ports blocked except for ports 80 and 22.. hence the headache I have trying to do my job sometimes. That's why I would love to be able to VNC via port 80 to my machine at home and pull up a browser and do whatever it is I need to do. The one thing I want is to make sure that my VNC session is encrypted over the net.
If you are connecting for work related stuff, ask your netadmin to help you set this up. You will both be happier for it. Of course if it's personal, maybe you need to stick to the ports he has set ;-) -- j
On July Tuesday 12 2005 6:33 pm, Jay Paulson wrote:
On Tuesday 12 July 2005 04:17 pm, Jay Paulson wrote: <snip>
I guess I'm at a backwards company because the network admin has all the out bound ports blocked except for ports 80 and 22.. hence the headache I have trying to do my job sometimes. That's why I would love to be able to VNC via port 80 to my machine at home and pull up a browser and do whatever it is I need to do. The one thing I want is to make sure that my VNC session is encrypted over the net.
If you are connecting for work related stuff, ask your netadmin to help you set this up. You will both be happier for it. Of course if it's personal, maybe you need to stick to the ports he has set ;-)
I have multiple times. She won't do it. :(
On 7/12/05, Jay Paulson
On July Tuesday 12 2005 6:33 pm, Jay Paulson wrote:
On Tuesday 12 July 2005 04:17 pm, Jay Paulson wrote: <snip>
I guess I'm at a backwards company because the network admin has all the out bound ports blocked except for ports 80 and 22.. hence the headache I have trying to do my job sometimes. That's why I would love to be able to VNC via port 80 to my machine at home and pull up a browser and do whatever it is I need to do. The one thing I want is to make sure that my VNC session is encrypted over the net.
If you are connecting for work related stuff, ask your netadmin to help you set this up. You will both be happier for it. Of course if it's personal, maybe you need to stick to the ports he has set ;-)
I have multiple times. She won't do it. :(
So, I still can not understand your problem. There was at least 3 recommendations to use ssh tunnels. The port is open (as you said), so what exactly is the problem? Why this is not a solution? Sunny
I guess I'm at a backwards company because the network admin has all the out bound ports blocked except for ports 80 and 22.. hence the headache I have trying to do my job sometimes. That's why I would love to be able to VNC via port 80 to my machine at home and pull up a browser and do whatever it is I need to do. The one thing I want is to make sure that my VNC session is encrypted over the net.
If you are connecting for work related stuff, ask your netadmin to help you set this up. You will both be happier for it. Of course if it's personal, maybe you need to stick to the ports he has set ;-)
I have multiple times. She won't do it. :(
So, I still can not understand your problem. There was at least 3 recommendations to use ssh tunnels. The port is open (as you said), so what exactly is the problem? Why this is not a solution?
I'm currently trying to get FreeNX setup but I'm running into some problems setting that up. I'm not sure how ssh tunneling works so to even get that to work is a daunting task. Since I'm pretty new to linux and the lack of howto's on the topics that I need help with I'm at a loss for what I can do. If you have any links to articles that tell users who don't have a clue (aka me!) I would love to read them. Thanks!
On Wednesday 13 July 2005 04:10, Jay Paulson wrote: <snip>
I'm currently trying to get FreeNX setup but I'm running into some problems setting that up. I'm not sure how ssh tunneling works so to even get that to work is a daunting task.
Since I'm pretty new to linux and the lack of howto's on the topics that I need help with I'm at a loss for what I can do. If you have any links to articles that tell users who don't have a clue (aka me!) I would love to read them.
Thanks!
Okay, here comes help.... 1) Do you have your ssh server up and running on the linux? 2) Do you have an Internet addresable address for your home box? 3) have you setup vnc via xinetd in yast? 4) at work are you using windows? I assume yes to the first since SUSE sets up ssh by default. I assume you know how to get to your home box from the internet since you are only talking about getting out of the office. I also assume you've setup and tested vnc at home. If you got linux at work (which I doubt since you are so excited about SUSE at home), you can use the vncviewer -via <user>@<home> localhost:1 Most probably you problem consists of getting ssh tunneling going from a windows client. This has been discussed a million, zillion times on the vnc lists, but I'm sure that if you confirm the above some else will be kind enough to add a link to one of the many descriptions on how this done.... Jerry
<snip>
I'm currently trying to get FreeNX setup but I'm running into some problems setting that up. I'm not sure how ssh tunneling works so to even get that to work is a daunting task.
Since I'm pretty new to linux and the lack of howto's on the topics that I need help with I'm at a loss for what I can do. If you have any links to articles that tell users who don't have a clue (aka me!) I would love to read them.
Thanks!
Okay, here comes help....
Yay! Thanks so much!
1) Do you have your ssh server up and running on the linux?
Yes
2) Do you have an Internet addresable address for your home box?
Yes. I have port forwarding working through my home router to my SuSE box.
3) have you setup vnc via xinetd in yast?
Yep sure have. I can connect via 5901 and through the web at 5801 but at work on my Mac OSX box I don't have access to those ports as I have already stated. That's why FreeNX would be great if I can get it working through my Mac OSX machine at work.
4) at work are you using windows?
Nope Mac OSX 10.3.9.
I assume yes to the first since SUSE sets up ssh by default.
I assume you know how to get to your home box from the internet since you are only talking about getting out of the office.
I also assume you've setup and tested vnc at home.
Yes, Yes, Yes.
If you got linux at work (which I doubt since you are so excited about SUSE at home), you can use the vncviewer -via <user>@<home> localhost:1
Ah.. well unfortunately no linux at work. :(
Most probably you problem consists of getting ssh tunneling going from a windows client.
If I could only find a tutorial or howto about ssh tunneling that is written in English that I can understand.
This has been discussed a million, zillion times on the vnc lists, but I'm sure that if you confirm the above some else will be kind enough to add a link to one of the many descriptions on how this done....
A link to something would be great! :) Thanks so much!
On Tue, 2005-07-12 at 17:17 -0500, Jay Paulson wrote:
On Tuesday 12 July 2005 05:30 pm, Jay Paulson wrote:
Hi all!
I'm new to SuSE and I'm loving it! At work I want to be able to VNC into my machine at home. However, the only ports that are open to the outside world are 80 and 22. I would like to keep port 22 reserved for ssh and make port 80 reserved for VNC connections. My question is it possible to set up a secure connection to my machine at home via VNC on port 80? If so how would one set up VNC to connect via a secure connection on port 80?
Thanks in advance! Jay
Why bother with vnc...?
Why not set ssh up on a high port where no one should be able to find it and then ssh into your machine. Works well without more than a minutes worth of effort.
Once you know how. How an explanation for the new user. There is nothing worse than telling someone new how easy it is without showing them how. This link may help some: http://lists.suse.com/archive/suse-linux-e/2005-May/1511.html
I can only get out from work via port 22 or port 80. So setting ssh up on a high port wouldn't work b/c I wouldn't be able to connect! doh! :)
Chill out man. Usually only the inbound ports are restricted to 22 and 80 amongst others, not outbound. You never want to run vnc over the internet by it's self, it is -not- safe. Use ssh to create a tunnel first, It's similar to using VPN for a connection and it encrypts the connection. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
participants (8)
-
Brad Bourn -
Bruce Marshall -
Jay Paulson -
Jerry Westrick -
jfweber＠bellsouth.net -
Ken Schneider -
Richard Bos -
Sunny