I have vnc working on my server when I am logged into that server. If I run vncviewer, I have a copy of the Desktop. Hwever, if I SSH into the server, I get an error. Due to my lack of experience, I am not sure what the log file means:
http://209.204.172.137/misc/vnc_error.txt
Could someone tell me what I am missing?
Todd
On Fri, 2007-02-02 at 16:05 -0800, Todd Cary wrote:
I have vnc working on my server when I am logged into that server. If I run vncviewer, I have a copy of the Desktop. Hwever, if I SSH into the server, I get an error. Due to my lack of experience, I am not sure what the log file means:
If you explain it with more details this should be easier to understand what you're trying to do ... It seems you're trying to have a vncserver working on your 'server' machine. How have you launched that vncserver ? through the standard /etc/rc.d/init.d/vncserver script ? What are the ports you're using ? Is a firewall running on that 'server' ? Did you mean you wanted to use ssh with port-forwarding to be able to connect on the remote vnc server through the ssh tunnel ? etc ...
He is what I would like to do:
Using Putty, log onto the server. Then type in
vncviewer server:1
and "see" the Desktop of the server *without* having the vnc ports open on the server; instead have the vnc data transferred via the SSH connection.
Todd
Fabian Arrotin wrote:
On Fri, 2007-02-02 at 16:05 -0800, Todd Cary wrote:
I have vnc working on my server when I am logged into that server. If I run vncviewer, I have a copy of the Desktop. Hwever, if I SSH into the server, I get an error. Due to my lack of experience, I am not sure what the log file means:
If you explain it with more details this should be easier to understand what you're trying to do ... It seems you're trying to have a vncserver working on your 'server' machine. How have you launched that vncserver ? through the standard /etc/rc.d/init.d/vncserver script ? What are the ports you're using ? Is a firewall running on that 'server' ? Did you mean you wanted to use ssh with port-forwarding to be able to connect on the remote vnc server through the ssh tunnel ? etc ...
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Todd Cary wrote:
He is what I would like to do:
Using Putty, log onto the server. Then type in
vncviewer server:1
and "see" the Desktop of the server *without* having the vnc ports open on the server; instead have the vnc data transferred via the SSH connection.
Todd
Start the vncserver and verify that it works locally by doing a vncviewer server:1 on the same machine (this should give a nice picture in picture in picture..). This is what already works, right? From a windows machine setup the a putty session by having a tunnel forwarding local port 5901 to server:5901. Then start a vncviewer on Windows (Realvnc/Tightvnc) and go to localhost:1 (so not to server:1) (You tried to start vncviewer in the putty shell? This will not work)
Theo
Theo -
That did it!! Many thanks.
By the way, after opening the VNC window and leaving, when I go to the server, the Network Alert icon is no longer there. It is probably due to my saying Yes when I came up in VNCviewer and it asked if wanted to delete an applet (I think it was an applet).
Would you know if any damage has been done and how I can restore the function that checks to see if I need to do an update?
Todd
Theo Band wrote:
Todd Cary wrote:
He is what I would like to do:
Using Putty, log onto the server. Then type in
vncviewer server:1
and "see" the Desktop of the server *without* having the vnc ports open on the server; instead have the vnc data transferred via the SSH connection.
Todd
Start the vncserver and verify that it works locally by doing a vncviewer server:1 on the same machine (this should give a nice picture in picture in picture..). This is what already works, right? From a windows machine setup the a putty session by having a tunnel forwarding local port 5901 to server:5901. Then start a vncviewer on Windows (Realvnc/Tightvnc) and go to localhost:1 (so not to server:1) (You tried to start vncviewer in the putty shell? This will not work)
Theo _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Todd Cary wrote:
Theo -
That did it!! Many thanks.
By the way, after opening the VNC window and leaving, when I go to the server, the Network Alert icon is no longer there. It is probably due to my saying Yes when I came up in VNCviewer and it asked if wanted to delete an applet (I think it was an applet).
Would you know if any damage has been done and how I can restore the function that checks to see if I need to do an update?
You need to keep your system up-to-date. I prefer to do that automatically with yum (chkconfig yum on;service yum start). The applet is not needed and even annoying if you do automatic updates. When manually updating, it might be handy for a single system.
To start it again: rhn-applet-gui
Theo
When I run rhn-applet-gui, I get the following error
http://209.204.172.137/misc/rhn-applet.txt
Any suggestions?
Todd
Theo Band wrote:
Todd Cary wrote:
Theo -
That did it!! Many thanks.
By the way, after opening the VNC window and leaving, when I go to the server, the Network Alert icon is no longer there. It is probably due to my saying Yes when I came up in VNCviewer and it asked if wanted to delete an applet (I think it was an applet).
Would you know if any damage has been done and how I can restore the function that checks to see if I need to do an update?
You need to keep your system up-to-date. I prefer to do that automatically with yum (chkconfig yum on;service yum start). The applet is not needed and even annoying if you do automatic updates. When manually updating, it might be handy for a single system.
To start it again: rhn-applet-gui
Theo _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 2/3/07, Todd Cary todd@aristesoftware.com wrote:
Theo -
That did it!! Many thanks.
By the way, after opening the VNC window and leaving, when I go to the server, the Network Alert icon is no longer there. It is probably due to my saying Yes when I came up in VNCviewer and it asked if wanted to delete an applet (I think it was an applet).
Would you know if any damage has been done and how I can restore the function that checks to see if I need to do an update?
Todd
I really like your aproach to this, so i wrote a small guide, to do it, you can read it here.
http://linux.go2linux.org/?q=node/15
On Mon, 2007-02-05 at 15:43 -0400, Guillermo Garron wrote:
On 2/3/07, Todd Cary todd@aristesoftware.com wrote:
Theo -
<snip>
Todd
I really like your aproach to this, so i wrote a small guide, to do it, you can read it here.
Excellent! However, if some newer users follow the guide, they may wonder why the lines subsequent to the "exec ..." have no effect. To forestall questions you might want to mention that.
-- Bill
On 2/5/07, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Mon, 2007-02-05 at 15:43 -0400, Guillermo Garron wrote:
On 2/3/07, Todd Cary todd@aristesoftware.com wrote:
Theo -
<snip>
Todd
I really like your aproach to this, so i wrote a small guide, to do it, you can read it here.
Excellent! However, if some newer users follow the guide, they may wonder why the lines subsequent to the "exec ..." have no effect. To forestall questions you might want to mention that.
Can you please help with that, 'cause I could be one of those users asking that :)
regards,
Guillermo Garron wrote:
On 2/5/07, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Mon, 2007-02-05 at 15:43 -0400, Guillermo Garron wrote:
On 2/3/07, Todd Cary todd@aristesoftware.com wrote:
Theo -
<snip>
Todd
I really like your aproach to this, so i wrote a small guide, to do it, you can read it here.
Excellent! However, if some newer users follow the guide, they may wonder why the lines subsequent to the "exec ..." have no effect. To forestall questions you might want to mention that.
Can you please help with that, 'cause I could be one of those users asking that :)
regards,
exec means replace the current shell by the command specified. Everything that follows is therefor not executed. If you remove the exec then it will work as well, and the commands after will get executed in sequence _after_ the vncserer dies. This might be handy is some occasions like starting and stopping ssh agents:
cat ~/.vnc/xstartup #!/bin/sh unset SESSION_MANAGER eval $(ssh-agent) /etc/X11/xinit/xinitrc kill $SSH_AGENT_PID exit
Theo
On 2/6/07, Theo Band theo.band@xanadu-wireless.com wrote:
Guillermo Garron wrote:
On 2/5/07, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Mon, 2007-02-05 at 15:43 -0400, Guillermo Garron wrote:
On 2/3/07, Todd Cary todd@aristesoftware.com wrote:
Theo -
<snip>
Todd
I really like your aproach to this, so i wrote a small guide, to do it, you can read it here.
Excellent! However, if some newer users follow the guide, they may wonder why the lines subsequent to the "exec ..." have no effect. To forestall questions you might want to mention that.
Can you please help with that, 'cause I could be one of those users asking that :)
regards,
exec means replace the current shell by the command specified. Everything that follows is therefor not executed. If you remove the exec then it will work as well, and the commands after will get executed in sequence _after_ the vncserer dies. This might be handy is some occasions like starting and stopping ssh agents:
cat ~/.vnc/xstartup #!/bin/sh unset SESSION_MANAGER eval $(ssh-agent) /etc/X11/xinit/xinitrc kill $SSH_AGENT_PID exit
Theo
thank you very much!
regards,
Theo Band wrote:
Todd Cary wrote:
He is what I would like to do:
Using Putty, log onto the server. Then type in
vncviewer server:1
and "see" the Desktop of the server *without* having the vnc ports open on the server; instead have the vnc data transferred via the SSH connection.
Todd
Start the vncserver and verify that it works locally by doing a vncviewer server:1 on the same machine (this should give a nice picture in picture in picture..). This is what already works, right? From a windows machine setup the a putty session by having a tunnel forwarding local port 5901 to server:5901. Then start a vncviewer on Windows (Realvnc/Tightvnc) and go to localhost:1 (so not to server:1) (You tried to start vncviewer in the putty shell? This will not work)
Theo _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On the server (Here with term 20): =================================== To start the server: vncserver :20 -depth 8 -geometry 1152x864 -name MyServerName:20
To stop the server: vncserver -kill :20
To change the VNC Password: vncpasswd
To get Gnome instead of default TWM: - vi ~/.vnc/xstartup - comment out TWM - add: gnome-session &
In PuTTY: - Create a session - Create a tunnel: L 5920 Destination: your.server.address:5920
Once connected: start VNC Viewer and enter "localhost:20" (without quotes) as the connect address. (Tested with TightVNC)
That should do the trick.
Guy Boisvert IngTegration inc.
On Sat, 2007-02-03 at 20:07 -0500, Guy Boisvert wrote:
Theo Band wrote:
Todd Cary wrote:
<snip>
On the server (Here with term 20):
To start the server: <snip>
To get Gnome instead of default TWM:
- vi ~/.vnc/xstartup
- comment out TWM
- add: gnome-session &
?? My ~/.vnc/xstartup originally had these three lines near the top
# Uncomment the following two lines for normal desktop: # unset SESSION_MANAGER # exec /etc/X11/xinit/xinitrc
I just deleted the "#" on the 2nd and 3rd lines and all subsequent lines in the file. My X default (KDE/Gnome or whatever) seems to be used then.
If I didn't want to use the system-wide default, I guess what I did would not be appropriate. Am I correct in guessing that it would be appropriate in a great many cases?
<snip>
Guy Boisvert IngTegration inc.
<snip CentOS sig stuff>
-- Bill
William L. Maltby wrote:
On Sat, 2007-02-03 at 20:07 -0500, Guy Boisvert wrote:
Theo Band wrote:
Todd Cary wrote:
<snip>
On the server (Here with term 20):
To start the server: <snip>
To get Gnome instead of default TWM:
- vi ~/.vnc/xstartup
- comment out TWM
- add: gnome-session &
?? My ~/.vnc/xstartup originally had these three lines near the top
# Uncomment the following two lines for normal desktop: # unset SESSION_MANAGER # exec /etc/X11/xinit/xinitrc
I just deleted the "#" on the 2nd and 3rd lines and all subsequent lines in the file. My X default (KDE/Gnome or whatever) seems to be used then.
If I didn't want to use the system-wide default, I guess what I did would not be appropriate. Am I correct in guessing that it would be appropriate in a great many cases?
-- Bill
Oh!
You're right Bill, i just checked the file too fast and didn't notice the note on top! I focused on the "TWM" line and just replaced it with Gnome-session!
Sorry again!
Guy Boisvert
I have found these "HowTo's", but I cannot get it working.
http://wheatstraw.is-a-geek.org/VNC%20through%20SSH%20Tunneling.html
http://www.science.smith.edu/~ejensen/vncssh.html
I use the Tectia SSH Client, though I do have putty.
Todd
Fabian Arrotin wrote:
On Fri, 2007-02-02 at 16:05 -0800, Todd Cary wrote:
I have vnc working on my server when I am logged into that server. If I run vncviewer, I have a copy of the Desktop. Hwever, if I SSH into the server, I get an error. Due to my lack of experience, I am not sure what the log file means:
If you explain it with more details this should be easier to understand what you're trying to do ... It seems you're trying to have a vncserver working on your 'server' machine. How have you launched that vncserver ? through the standard /etc/rc.d/init.d/vncserver script ? What are the ports you're using ? Is a firewall running on that 'server' ? Did you mean you wanted to use ssh with port-forwarding to be able to connect on the remote vnc server through the ssh tunnel ? etc ...
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Fabian Arrotin -
Guillermo Garron -
Guy Boisvert -
Theo Band -
Todd Cary -
William L. Maltby