Quite often I'm in situation I need to start some xterm logging or other thing on my PC and later access it from some other or let someone else see the output. What I see people with XP/w2k around me doing is vnc. I know I can start vncserver on my 8.2 PC too, but what would be the safe way doing so and how can I just easy turn it on/off when needed. Thx, Martin __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
On Thursday 25 November 2004 15:20, Martin wrote:
Quite often I'm in situation I need to start some xterm logging or other thing on my PC and later access it from some other or let someone else see the output. What I see people with XP/w2k around me doing is vnc. I know I can start vncserver on my 8.2 PC too, but what would be the safe way doing so and how can I just easy turn it on/off when needed.
Thx, Martin
__________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
Using the firewall configuration, disable the external access to the port on which vncserver waits connection. Then use ssh tunneling to connect (putty is the ssh client I use under Win). That way, the connection will be encrypted, and you will have all the security provided by linux logon routine :) That way (using ssh tunnel) first thing you do one way or another is to establish ssh session with your machine. So if the vnc server is not running you can start it easily by issuing a simple command. And stop it when you want. I do not see a reason to stop it anyway, but if you wish - you can :) Cheers Sunny -- Try the best browser, get Firefox now: http://tinyurl.com/5a878
On Thursday 25 November 2004 1:20 pm, Martin wrote:
Quite often I'm in situation I need to start some xterm logging or other thing on my PC and later access it from some other or let someone else see the output. What I see people with XP/w2k around me doing is vnc. I know I can start vncserver on my 8.2 PC too, but what would be the safe way doing so and how can I just easy turn it on/off when needed.
Thx, Martin
Go to KDE Control Center -> Internet & Network -> Desktop Sharing. Then click on Help. And check out the link that says read the full manual here. KDE has a very nice Desktop Sharing mechanism. It essentially converts your running KDE desktop into a vncserver which someone else can connect to using a vncviewer. You can start and stop it without having to restart your KDE session. It automatically generates the passwords even and can email an invitation to someone else. It is pretty handy. Osho
__________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com
-- Osho
Osho GG wrote:
Go to KDE Control Center -> Internet & Network -> Desktop Sharing. Then click on Help. And check out the link that says read the full manual here.
KDE has a very nice Desktop Sharing mechanism. It essentially converts your running KDE desktop into a vncserver which someone else can connect to using a vncviewer. You can start and stop it without having to restart your KDE session. It automatically generates the passwords even and can email an invitation to someone else. It is pretty handy.
The problem with vnc, is that it requires someone at the remote system to allow access, which is not the greatest, if you don't have a keyboard & monitor attached.
James Knott wrote:
The problem with vnc, is that it requires someone at the remote system to allow access, which is not the greatest, if you don't have a keyboard & monitor attached.
That's my problem with it as well. And I don't want to have a short time-out on the connection lifetime. Is reasonable desktop access really too much to ask for? Jim
On Thu, 2004-11-25 at 22:08, Jim Sabatke wrote:
James Knott wrote:
The problem with vnc, is that it requires someone at the remote system to allow access, which is not the greatest, if you don't have a keyboard & monitor attached.
That's my problem with it as well. And I don't want to have a short time-out on the connection lifetime. Is reasonable desktop access really too much to ask for?
Jim
The Remote Desktop Connection and Desktop Sharing combination seems to have been designed with support in mind. This would mean that someone would be at the other end to support. If you want full access to the box remotely, go to Yast -> System -> "/etc/sysconfig Editor". Now go to Desktop -> "Display Manager" -> DISPLAY_MANAGER_REMOTE_ACCESS and set it to Yes. Now go to Yast -> "Network Services" -> "Network Services" and enable xinetd if it is not already enabled. Make sure vnc1 and vnchttpd1 are checked. Restart X Now you can remote to the logon screen of this machine at any time from anywhere. You can even set a web browser to http://yourmachine:5801 and get to the logon screen if the client is Windows or doesn't have the Remote Desktop client software installed. HTH Louis
Hi Louis, That works fine, but when i establish a connection, a see a black screen with a big X as mouse-pointer, and no my normal KDE-desktop. Also i cannot find any way to execute something. Greets, Franky. On Friday 26 November 2004 15:55, Louis Richards wrote:
On Thu, 2004-11-25 at 22:08, Jim Sabatke wrote:
James Knott wrote:
The problem with vnc, is that it requires someone at the remote system to allow access, which is not the greatest, if you don't have a keyboard & monitor attached.
That's my problem with it as well. And I don't want to have a short time-out on the connection lifetime. Is reasonable desktop access really too much to ask for?
Jim
The Remote Desktop Connection and Desktop Sharing combination seems to have been designed with support in mind. This would mean that someone would be at the other end to support.
If you want full access to the box remotely, go to Yast -> System -> "/etc/sysconfig Editor". Now go to Desktop -> "Display Manager" -> DISPLAY_MANAGER_REMOTE_ACCESS and set it to Yes.
Now go to Yast -> "Network Services" -> "Network Services" and enable xinetd if it is not already enabled. Make sure vnc1 and vnchttpd1 are checked.
Restart X
Now you can remote to the logon screen of this machine at any time from anywhere. You can even set a web browser to http://yourmachine:5801 and get to the logon screen if the client is Windows or doesn't have the Remote Desktop client software installed.
HTH Louis
-- _________________________________________________________ GOETHALS Franky Driegaaienstraat 104 B-9100 SINT-NIKLAAS B E L G I E Verantwoordelijke MVS Support voor Euroclear Bank Secretaris GSE Z/OS Systems Working Group Privaat doeleinden & GSE Workgroup : Tel. : 32 - (0)3 / 776.65.17 GSM : 32 - (0)473 / 98.90.24 Mail & MSN : franky.goethals@telenet.be http://gsezos.dyns.cx Professionele doeleinden : Tel. Werk : 32 - (0)2 / 224.15.92 Mail werk : goethals_franky@euroclear.com http://www.euroclear.com _________________________________________________________
On Fri, 2004-11-26 at 10:57, Franky Goethals wrote:
Hi Louis,
That works fine, but when i establish a connection, a see a black screen with a big X as mouse-pointer, and no my normal KDE-desktop. Also i cannot find any way to execute something.
Greets, Franky.
The fact that you are getting the screen with the X cursor indicates that the VNC Server program is working properly. The absence of a logon screen would indicate that KDM is not allowing XDMCP connections. Check at the bottom of the file "/etc/opt/kde3/share/config/kdm/kdmrc". You should see a section titled "[Xdmcp]" and just under that it should say "Enable=true". Make sure the above is OK and the go to a regular console screen, logon as root, and type "rckdm restart" and smash ENTER. I use this method to get at my systems. The desktop sharing app is for assisting users (getting on to their already running desktop). These are two different methods for two different needs. This is probably why the Desktop Sharing app defaults to requiring a user to authorize access. You would, after all, be getting on to their in use desktop. The xinetd vnc server is available without this requirement as you are presented with a logon screen. While not as good for assisting a user, this is better for remote administration and/or getting at a headless server. HTH Louis P.S. Of course, "ssh -X" works wonders too. ;-)
Hi Louis, Thanks for your help ! indeed, this was the problem. Greets, Franky. On Friday 26 November 2004 22:30, Louis Richards wrote:
On Fri, 2004-11-26 at 10:57, Franky Goethals wrote:
Hi Louis,
That works fine, but when i establish a connection, a see a black screen with a big X as mouse-pointer, and no my normal KDE-desktop. Also i cannot find any way to execute something.
Greets, Franky.
The fact that you are getting the screen with the X cursor indicates that the VNC Server program is working properly. The absence of a logon screen would indicate that KDM is not allowing XDMCP connections.
Check at the bottom of the file "/etc/opt/kde3/share/config/kdm/kdmrc". You should see a section titled "[Xdmcp]" and just under that it should say "Enable=true".
Make sure the above is OK and the go to a regular console screen, logon as root, and type "rckdm restart" and smash ENTER.
I use this method to get at my systems. The desktop sharing app is for assisting users (getting on to their already running desktop). These are two different methods for two different needs. This is probably why the Desktop Sharing app defaults to requiring a user to authorize access. You would, after all, be getting on to their in use desktop. The xinetd vnc server is available without this requirement as you are presented with a logon screen. While not as good for assisting a user, this is better for remote administration and/or getting at a headless server.
HTH Louis
P.S. Of course, "ssh -X" works wonders too. ;-)
-- _________________________________________________________ GOETHALS Franky Driegaaienstraat 104 B-9100 SINT-NIKLAAS B E L G I E Verantwoordelijke MVS Support voor Euroclear Bank Secretaris GSE Z/OS Systems Working Group Privaat doeleinden & GSE Workgroup : Tel. : 32 - (0)3 / 776.65.17 GSM : 32 - (0)473 / 98.90.24 Mail & MSN : franky.goethals@telenet.be http://gsezos.dyns.cx Professionele doeleinden : Tel. Werk : 32 - (0)2 / 224.15.92 Mail werk : goethals_franky@euroclear.com http://www.euroclear.com _________________________________________________________
Robert Rozman wrote:
and thanks,
I know exactly - the week after you get tired of waiting and install something else instead. ;-) -- "Congress shall make no law respecting an establishment of religion or prohibiting the free exercise thereof..." U.S. Constitution, Amendment 1 Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
On Friday 26 November 2004 04:10, James Knott wrote:
Osho GG wrote:
Go to KDE Control Center -> Internet & Network -> Desktop Sharing. Then click on Help. And check out the link that says read the full manual here.
KDE has a very nice Desktop Sharing mechanism. It essentially converts your running KDE desktop into a vncserver which someone else can connect to using a vncviewer. You can start and stop it without having to restart your KDE session. It automatically generates the passwords even and can email an invitation to someone else. It is pretty handy.
The problem with vnc, is that it requires someone at the remote system to allow access, which is not the greatest, if you don't have a keyboard & monitor attached.
Not at all, it is possible to set up both regular vnc and KDE remote desktop sharing to allow completely unattended sharing. Have a look at the settings available in KDE's desktop sharing setup, there is an option for allowing connections without manual verification
Anders Johansson wrote:
On Friday 26 November 2004 04:10, James Knott wrote:
Osho GG wrote:
Go to KDE Control Center -> Internet & Network -> Desktop Sharing. Then click on Help. And check out the link that says read the full manual here.
KDE has a very nice Desktop Sharing mechanism. It essentially converts your running KDE desktop into a vncserver which someone else can connect to using a vncviewer. You can start and stop it without having to restart your KDE session. It automatically generates the passwords even and can email an invitation to someone else. It is pretty handy.
The problem with vnc, is that it requires someone at the remote system to allow access, which is not the greatest, if you don't have a keyboard & monitor attached.
Not at all, it is possible to set up both regular vnc and KDE remote desktop sharing to allow completely unattended sharing. Have a look at the settings available in KDE's desktop sharing setup, there is an option for allowing connections without manual verification
I'll have to recheck that. I didn't see that option when I looked before. Thanks, Jim
Anders Johansson wrote:
On Friday 26 November 2004 04:10, James Knott wrote:
Osho GG wrote:
Go to KDE Control Center -> Internet & Network -> Desktop Sharing. Then click on Help. And check out the link that says read the full manual here.
KDE has a very nice Desktop Sharing mechanism. It essentially converts your running KDE desktop into a vncserver which someone else can connect to using a vncviewer. You can start and stop it without having to restart your KDE session. It automatically generates the passwords even and can email an invitation to someone else. It is pretty handy.
The problem with vnc, is that it requires someone at the remote system to allow access, which is not the greatest, if you don't have a keyboard & monitor attached.
Not at all, it is possible to set up both regular vnc and KDE remote desktop sharing to allow completely unattended sharing. Have a look at the settings available in KDE's desktop sharing setup, there is an option for allowing connections without manual verification
And those settings would be??? I've tried all the settings I can find, including turning off "Confirm uninvited connections before accepting".
On Friday 26 November 2004 20:14, James Knott wrote:
Anders Johansson wrote:
On Friday 26 November 2004 04:10, James Knott wrote:
Osho GG wrote:
Go to KDE Control Center -> Internet & Network -> Desktop Sharing. Then click on Help. And check out the link that says read the full manual here.
KDE has a very nice Desktop Sharing mechanism. It essentially converts your running KDE desktop into a vncserver which someone else can connect to using a vncviewer. You can start and stop it without having to restart your KDE session. It automatically generates the passwords even and can email an invitation to someone else. It is pretty handy.
The problem with vnc, is that it requires someone at the remote system to allow access, which is not the greatest, if you don't have a keyboard & monitor attached.
Not at all, it is possible to set up both regular vnc and KDE remote desktop sharing to allow completely unattended sharing. Have a look at the settings available in KDE's desktop sharing setup, there is an option for allowing connections without manual verification
And those settings would be??? I've tried all the settings I can find, including turning off "Confirm uninvited connections before accepting".
I can connect to Mine with vncviewer ip-address:0 I use these options: Start->System->Remote Access->Desktop Sharing click [configure] Access Tab: x Allow uninvited connections x Announce service on network o COnfirm uninvited connections x Allow uninvited connections to control desktop Pasword: ********** Session tab: o Always disable background image Network tab: x Assign Port automatically Jerry
On Friday 26 November 2004 20:14, James Knott wrote:
And those settings would be??? I've tried all the settings I can find, including turning off "Confirm uninvited connections before accepting".
That's what I've done, and together with checking the "Allow uninvited connections" and "Allow uninvited connections to control the desktop", it's worked for me for several versions of kde (and from Jerry's mail, I don't think I'm the only one). Only do it on trusted networks of course, it's not something you want to have open to the internet
On Fri, 2004-11-26 at 20:58, Anders Johansson wrote:
On Friday 26 November 2004 20:14, James Knott wrote:
And those settings would be??? I've tried all the settings I can find, including turning off "Confirm uninvited connections before accepting".
That's what I've done, and together with checking the "Allow uninvited connections" and "Allow uninvited connections to control the desktop", it's worked for me for several versions of kde (and from Jerry's mail, I don't think I'm the only one).
Only do it on trusted networks of course, it's not something you want to have open to the internet
You could use an ssh tunnel to connect through the Internet with a bit of security. I use the following where InsideIP equals a machine inside my network running VNC Server. Use localhost if you have just the one PC or want to connect to your firewall. OutsideIP is the Internet address of the system. ssh -C -c blowfish -L 5901:InsideIP:5901 OutsideIP Then connect the client to localhost:1 . It seems to run at a usable speed over a medium speed DSL. If you throw in another -L parameter on the command line for port 139, you can even mount a Samba share and transfer files. That last one is pretty slow though. It's usually faster to use scp. HTH Louis
participants (11)
-
Anders Johansson -
Felix Miata -
Franky Goethals -
James Knott -
Jerry Westrick -
Jim Sabatke -
Louis Richards -
Martin -
Osho GG -
Robert Rozman -
Sunny