Using Remote Desktop connection
Hi, I have been trying to use Remote Desktop connection with my suse box 8.2, however, I haven't been able to connect neither to another suse box nor to a windows box. Could someone explain in detail how should I make that work. Thanks Jose
On Saturday 25 October 2003 14:07, Jose Sanchez wrote:
Hi,
I have been trying to use Remote Desktop connection with my suse box 8.2, however, I haven't been able to connect neither to another suse box nor to a windows box. Could someone explain in detail how should I make that work.
Thanks
Jose
I have Tightvnc running on the Windows box and use remote desktop to access it, it works fine. Connect to <ip of windows box>:0 for display 0. I have never tried to use the native XP remote desktop as the server if that is what you are asking.... The other Linux box needs to be running something like vncserver i think in order to listen for the connection. then you will connect to <ip of linux box>:1 for display 1. hope this helps ~j
On Saturday 25 October 2003 13:07, Jose Sanchez wrote:
Hi,
I have been trying to use Remote Desktop connection with my suse box 8.2, however, I haven't been able to connect neither to another suse box nor to a windows box. Could someone explain in detail how should I make that work.
Thanks
Jose
I have used Remote Desktop Connection with SuSE machine and VNC on Windows machines with great success. 1) make sure that you have remote desktop sharing (KDE) or VNC (Linux or Windows) configured on the remote host 2) connect to <ip addr of remote host>:0 Works well. I have attempted to connect to the remote desktop and terminal services part of XP/Server 2003 with no success. I have used rdesktop to make that connection so I know that it works, but I can't seem to get it to work properly through Remote Desktop Connection. To use rdesktop you simply type rdesktop <ip addr of remote host> and it should work. It seems that I had to recompile the rdesktop software for some reason to get it to work, but I don't remember why, you should check the archive for that probably. -- Kelly L. Fulks Home Account near Huntsville, AL
I have Tightvnc running on the Windows box and use remote desktop to access it, it works fine. Connect to <ip of windows box>:0 for display 0. I have never tried to use the native XP remote desktop as the server if that is what you are asking....
The other Linux box needs to be running something like vncserver i think in order to listen for the connection. then you will connect to <ip of linux box>:1 for display 1.
hope this helps ~j
1) make sure that you have remote desktop sharing (KDE) or VNC (Linux or Windows) configured on the remote host 2) connect to <ip addr of remote host>:0
Hi, thanks for the info. I downloaded a VNC server from the internet called realvnc (http://www.realvnc.com/download.html) and installed in my windows machine. I was able to connect from my linux PC to my windows PC, however, from my windows PC to my linux PC was not possible. Well I did it but I could only see the screen and couldn't do anything. I used the remote desktop sharing from suse, however it allows me only to connect for one hour and gives me a password. How do I activate a vncserver in linux? I entered the start internet services in yast and activated the vnc things, however how should I configure the vncserver in linux and start it because it seems not to be running. Thanks Jose
-----Original Message----- From: Jose Sanchez <joseos@okstate.edu> To: Cc: suse-linux-e@suse.com Date: Mon, 27 Oct 2003 17:45:34 -0600 Subject: Re: [SLE] Using Remote Desktop connection
I have Tightvnc running on the Windows box and use remote desktop to access it, it works fine. Connect to <ip of windows box>:0 for
display
0. I have never tried to use the native XP remote desktop as the server if that is what you are asking....
The other Linux box needs to be running something like vncserver i think in order to listen for the connection. then you will connect to <ip of linux box>:1 for display 1.
hope this helps ~j
1) make sure that you have remote desktop sharing (KDE) or VNC (Linux or Windows) configured on the remote host 2) connect to <ip addr of remote host>:0
Hi, thanks for the info. I downloaded a VNC server from the internet called realvnc (http://www.realvnc.com/download.html) and installed in my windows machine. I was able to connect from my linux PC to my windows PC, however, from my windows PC to my linux PC was not possible. Well I did it but I could only see the screen and couldn't do anything. I used the remote desktop sharing from suse, however it allows me only to connect for one hour and gives me a password.
Wrong. It gives you one hour in which to make the connection. Once you connect it will stay connected until you break the connection.
How do I activate a vncserver in linux? I entered the start internet services in yast and activated the vnc things, however how should I configure the vncserver in linux and start it because it seems not to be running.
Thanks
Jose
Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998
Jose Sanchez wrote:
1) make sure that you have remote desktop sharing (KDE) or VNC (Linux or Windows) configured on the remote host
I have been following this thread because I want to do remost assistance too but so far I am confused. Where is the KDE remote desktop sharing that you mentioned? So far I haven't been able to connect to or from a Linux PC. I installed the rdesktop package but I got the impression that it is for connecting to NT machines. I get the impression from this discussion that it will connect to Linux PCs also. Just what is rdesktop used for and what is required on the remote end (either Windows or Linux) in order for rdesktop to connect? I tried using VNC but on the Linux side it doesn't give me what I need. In order to be used as a remote assistance tool, I need to see remotely the same thing the local user sees, not the nearly blank window I see when connecting to a Linux (SuSE 8.0) PC that is running vncserver Damon Register
On Wed, 2003-10-29 at 16:04, Damon Register wrote:
Jose Sanchez wrote:
1) make sure that you have remote desktop sharing (KDE) or VNC (Linux or Windows) configured on the remote host
I have been following this thread because I want to do remost assistance too but so far I am confused. Where is the KDE remote desktop sharing that you mentioned?
So far I haven't been able to connect to or from a Linux PC. I installed the rdesktop package but I got the impression that it is for connecting to NT machines. I get the impression from this discussion that it will connect to Linux PCs also. Just what is rdesktop used for and what is required on the remote end (either Windows or Linux) in order for rdesktop to connect?
I tried using VNC but on the Linux side it doesn't give me what I need. In order to be used as a remote assistance tool, I need to see remotely the same thing the local user sees, not the nearly blank window I see when connecting to a Linux (SuSE 8.0) PC that is running vncserver
Damon Register
rsesktop is for connecting to windows servers. To share your desktop (using VNC) go to internet-->tools-->Desktop Sharing This will start a dialog for sharing your desktop :0 (using VNC) and will limit the amount of time you have to connect to 1 hour. This does not mean you only have an hour to be connected only that you must connect within the hour. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Ken Schneider wrote:
rsesktop is for connecting to windows servers.
so it isn't for connecting to other Linux PCs. Ok , thanks
To share your desktop (using VNC) go to
internet-->tools-->Desktop Sharing
I don't even see that option under internet-->tools Damon Register
On Wed, 2003-10-29 at 17:08, Damon Register wrote:
Ken Schneider wrote:
rsesktop is for connecting to windows servers.
so it isn't for connecting to other Linux PCs. Ok , thanks
To share your desktop (using VNC) go to
internet-->tools-->Desktop Sharing
I don't even see that option under internet-->tools
Damon Register
Then you don't have it installed. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Ken Schneider wrote:
I don't even see that option under internet-->tools
Damon Register
Then you don't have it installed.
Have what installed? I searched in the YaST packages list but did not find anything that contained sharing in name or description Damon Register
On Wed, 2003-10-29 at 18:00, Damon Register wrote:
Ken Schneider wrote:
I don't even see that option under internet-->tools
Damon Register
Then you don't have it installed.
Have what installed? I searched in the YaST packages list but did not find anything that contained sharing in name or description
Damon Register
You need to do a search for rdesktop. I usually select all of the search options when using the search function. But a search for the name only should show you the package to install. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Ken Schneider wrote:
rsesktop is for connecting to windows servers.
so it isn't for connecting to other Linux PCs. Ok , thanks
rdesktop isn't just for connecting to windows machines. I connect to a SuSE 8.2 machine through a ssh session and through a firewall regularly using rdesktop. vncserver runs on the remote machine and rdesktop fires up the the local one. The ssh command I use is "ssh -C -X -L 5905:192.168.1.5:5901 user@myserver.no-ip.com". The remote machine is protected by an IPCop firewall which allows requests coming in on port 22 from my local IP address. ssh then tunnels to the 192 address within the remote DMZ. Start up rdesktop locally and point it to localhost:5 and ssh tunnels the request to the remote vncserver. If your client and server are local you don't need the ssh stuff. I only included it in case others were curious. The issue you're seeing Damon is that windows only has one display so when you run vncserver on that display you effectively export that display through vnc. Any vncviewer client will then connect to it and will see what the remote user sees. On UNIX X can run multiple displays, as can vncserver. If X is using display :0 then vncserver will start up on the next free (virtual) display - in this case :1 so you don;t see what the remote user sees (:0). Damian
Damian O'Hara wrote:
Ken Schneider wrote:
rsesktop is for connecting to windows servers.
so it isn't for connecting to other Linux PCs. Ok , thanks
What I forgot to mention was ... Ken's right that you can export your KDE session (:0) thruogh the desktop tools. Also rdesktop will also connect to a Win2k or above (wash my mouth out) machine which has remote access configured (no vncserver required). On NT (IIRC) it only works with NT Server. This is not RAS but something else - I forget the windoze terminology. Damian
Damian O'Hara wrote:
Ken's right that you can export your KDE session (:0) thruogh the desktop tools. Also rdesktop will also connect to a Win2k or above (wash my mouth out) machine which has remote access configured (no vncserver required). On NT (IIRC) it only works with NT Server. This is not RAS but something else - I forget the windoze terminology.
While I really appreciate your help, I have to say that both you and Ken are leaving me very confused. You appear (at least to me) to be using server and client terms interchangeably. From what I see, rdesktop is only a client. I already have that installed. one of you mentioned Internet-->Tools-->remote desktop but from the discussion it seems to me that is for the server side? It appears to me that most of the answers are dealing with the client side but the question still remains: what must I do to the host or server computer so that a client computer with rdesktop or vncviewer may connect? I have downloaded the latest VNC for Linux from their website. It is installed and vncview will connect to windows computers with no trouble. Still I cannot connect from any client to a Linux host. I read Ken's earlier post about sharing the KDE desktop using vnc and I also read Richard's post that mentions package kdenetwork3-vnc. Is this package a must in order to share desktop :0 with vnc or is that just to allow access through internet-->tools>remote desktop? Stefan mentioned that I can use xf4vnc but that comes with almost zero instructions so I have no clue how to use it Damon Register
Damon Register wrote:
Damian O'Hara wrote:
Ken's right that you can export your KDE session (:0) thruogh the desktop tools. Also rdesktop will also connect to a Win2k or above (wash my mouth out) machine which has remote access configured (no vncserver required). On NT (IIRC) it only works with NT Server. This is not RAS but something else - I forget the windoze terminology.
While I really appreciate your help, I have to say that both you and Ken are leaving me very confused. You appear (at least to me) to be using server and client terms interchangeably. From what I see, rdesktop is only a client. I already have that installed. one of you mentioned Internet-->Tools-->remote desktop but from the discussion it seems to me that is for the server side?
It appears to me that most of the answers are dealing with the client side but the question still remains: what must I do to the host or server computer so that a client computer with rdesktop or vncviewer may connect? I have downloaded the latest VNC for Linux from their website. It is installed and vncview will connect to windows computers with no trouble. Still I cannot connect from any client to a Linux host.
I agree with you, as I told everyone before, I was able to see from my Windows PC my linux Desktop, however I was not able to interact with it. I mean, close windows, run programs, etc. I have no idea how to do that and how to configure it to allow clients to interact with the host. Jose
On Thursday 30 October 2003 01:10, Jose Sanchez wrote:
It appears to me that most of the answers are dealing with the client side but the question still remains: what must I do to the host or server computer so that a client computer with rdesktop or vncviewer may connect? I have downloaded the latest VNC for Linux from their website. It is installed and vncview will connect to windows computers with no trouble. Still I cannot connect from any client to a Linux host.
I agree with you, as I told everyone before, I was able to see from my Windows PC my linux Desktop, however I was not able to interact with it. I mean, close windows, run programs, etc. I have no idea how to do that and how to configure it to allow clients to interact with the host.
Jose
Gentlemen - This is how I do it maybe this will help you. On the linux box at a command prompt - $ /usr/X11R6/bin/vncpasswd This will set the vncserver password. Then - $ /usr/X11R6/bin/vncserver This starts Xvnc, and it should tell you which display it is on. Usually :1 Xvnc will start whatever is in $HOME/.vnc/xstartup, mine just has xrdb $HOME/.Xresources xsetroot -solid grey xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & fvwm & fvwm is a window manager which starts with a shell prompt open. It is not the desktop on display:0 like Windows has so this can cause some confusion. I run kmail or konqueror or whatever from the prompt. The writer is probably correct that sharing display 0 using VNC CAN be done. I have not tried that. I got an error about an X server already running on display:0 and left it at that. I just do the other thing above.... Hope this helps..... ~j
On Thursday 30 October 2003 10:32, J Lake wrote:
I got an error about an X server already running on display:0 and left it at that.
~ I believe one can run a 2nd X-Server, with the command :- startx -- :1 -- best wishes ____________ sent on Linux ____________
J Lake wrote:
The writer is probably correct that sharing display 0 using VNC CAN be done. I have not tried that. I got an error about an X server already running on
So far everyone is dancing around the subject. Sr. Sanchez, are you trying to connect to the host's main desktop :0 as I am? Connecting to any other desktop is of no value to me. According to http://www.realvnc.com/how.html, "For the individual user, one common scenario is using VNC to help troubleshoot the computer of a distant less-technically-savvy relative. In other words, sitting at your desk in Baltimore, you could use VNC to take control of your mother's PC in London and show her how to install and use some new software package by actually doing it yourself." Connecting to any other desktop besides :0 doesn't accomplish this. It seems at this point that serving :0 can't be done with VNC alone. I found that on the realvnc website. One person mentioned xf4vnc and that looks promising but also rather complicated so I will have to research that more Damon Register
On Thu, 2003-10-30 at 10:15, Damon Register wrote:
J Lake wrote:
The writer is probably correct that sharing display 0 using VNC CAN be done. I have not tried that. I got an error about an X server already running on
So far everyone is dancing around the subject. Sr. Sanchez, are you trying to connect to the host's main desktop :0 as I am? Connecting to any other desktop is of no value to me. According to http://www.realvnc.com/how.html, "For the individual user, one common scenario is using VNC to help troubleshoot the computer of a distant less-technically-savvy relative. In other words, sitting at your desk in Baltimore, you could use VNC to take control of your mother's PC in London and show her how to install and use some new software package by actually doing it yourself." Connecting to any other desktop besides :0 doesn't accomplish this.
It seems at this point that serving :0 can't be done with VNC alone. I found that on the realvnc website. One person mentioned xf4vnc and that looks promising but also rather complicated so I will have to research that more
Damon Register
The package to have installed in order to share your :0 display is kdenetwork-vnc. This will provide Internet-->Tools-->Desktop Sharing which will open a dialog to allow you to share your desktop. I have used this in the past and it works. When you launch the program it will display a window with a password that will be good for one hour. This means you have up to one hour to make the connection, it does NOT mean you can only connect for an hour. Once connected you can stay connected for as long as you like. The other program mentioned in this thread is Rdesktop which is used to connect to a MS NT (or above) OS running remote desktop services. It never hurts to do a little research on your own as well. How easy we have it today with search engines like Google. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Thursday 30 October 2003 09:15, Damon Register wrote:
J Lake wrote:
The writer is probably correct that sharing display 0 using VNC CAN be done. I have not tried that. I got an error about an X server already running on
So far everyone is dancing around the subject. Sr. Sanchez, are you trying to connect to the host's main desktop :0 as I am? Connecting to any other desktop is of no value to me. According to http://www.realvnc.com/how.html, "For the individual user, one common scenario is using VNC to help troubleshoot the computer of a distant less-technically-savvy relative. In other words, sitting at your desk in Baltimore, you could use VNC to take control of your mother's PC in London and show her how to install and use some new software package by actually doing it yourself." Connecting to any other desktop besides :0 doesn't accomplish this.
It seems at this point that serving :0 can't be done with VNC alone. I found that on the realvnc website. One person mentioned xf4vnc and that looks promising but also rather complicated so I will have to research that more
Damon Register
OK, the answer is (if you are running KDE) that you can do this. You can connect to desktop :0 and you can control it, if you set everything up properly. 1. Install kdenetwork3-vnc 2. KDE Menu -> Control Center 3. Internet & Network 4. Desktop Sharing 5. Check Allow uninvited connections (this allows you to connect at anytime) 6. Check Allow uninvited connections to control the desktop 7. Enter a password and make it a very good one as your desktop will potientially be exposed to the internet depending upon how your network is configured 8. Apply 9. File -> Quit 10. Connect from remote machine You may have to logout and login, it has been too long since I set this up to remember. But it does work. It is desktop :0. You can not serve :0 with VNC alone. VNC pretends to be an X Server to the X-Windows system and you can't have two :0 servers. I am not familiar with doing this with any other Desktop Environment/Window Manager, but it is possible with KDE. XF4Vnc does look promising in the area of other desktop environments, but I have no experience with it. I was not familiar with it, so thanks for the pointer. -- Kelly L. Fulks Home Account near Huntsville, AL
Kelly Fulks wrote:
OK, the answer is (if you are running KDE) that you can do this. You can connect to desktop :0 and you can control it, if you set everything up properly.
Thanks for that kick. I have always used WinVNC on the Windows machines, a simple enable and the linux machines are there as well. It is amazing just how much functionality is available 'out of the box'. It far outdoes WindowsXP ;) -- Lester Caine ----------------------------- L.S.Caine Electronic Services
Lester Caine wrote:
Windows machines, a simple enable and the linux machines are there as well.
It is amazing just how much functionality is available 'out of the box'. It far outdoes WindowsXP ;)
The problem is that this seems to be a very recent development. In trying to find that kdenetwork3-vnc that a few mentioned earlier it appears in a more recent kde than is with SuSE 8.0. I am not an expert here but I suspect that one cannot take a module from one version of kde and stick it into an older one. Therefore I would likely have to upgrade kde which seems like a difficult task. From all of the kde upgrade discussions I have seen here in the past, I don't think I want to tackle that. While it might very well outdo XP out of the box, I am still disappointed that it took so long to get to a point that has existed in Windows for years. Even though my SuSE 9.0 may arrive soon and this issue might be overcome by events, I can't accept being beaten so I will pursue this. It seems that xf4vnc is the only hope for older kde that doesn't have kdenetwork3-vnc. If anyone has had experience with xf4vnc with display :0 on SuSE, I would like to hear from you. Damon Register
Damon Register wrote:
Lester Caine wrote:
Windows machines, a simple enable and the linux machines are there as well.
It is amazing just how much functionality is available 'out of the box'. It far outdoes WindowsXP ;)
The problem is that this seems to be a very recent development. In trying to find that kdenetwork3-vnc that a few mentioned earlier it appears in a more recent kde than is with SuSE 8.0. I am not an expert here but I suspect that one cannot take a module from one version of kde and stick it into an older one. Therefore I would likely have to upgrade kde which seems like a difficult task. From all of the kde upgrade discussions I have seen here in the past, I don't think I want to tackle that. While it might very well outdo XP out of the box, I am still disappointed that it took so long to get to a point that has existed in Windows for years.
Even though my SuSE 9.0 may arrive soon and this issue might be overcome by events, I can't accept being beaten so I will pursue this. It seems that xf4vnc is the only hope for older kde that doesn't have kdenetwork3-vnc. If anyone has had experience with xf4vnc with display :0 on SuSE, I would like to hear from you.
Damon Register
Haven't tried it wit SuSE 9.0. This is what I had do to get it working on my laptop with SuSE 7.2 XFree4.2.0 kernel 2.4.18. Edit your "/etc/X11/XF86config" by adding the following lines: Add in the "Module" section the loading of the vnc module. --------------------------- Section "Module" .... Load "vnc" EndSection --------------------------- Now add the vnc keyboard and mouse as extra "Inputdevice". --------------------------- # Input devices for vnc session Section "InputDevice" Driver "rfbkeyb" Identifier "vncKeyboard" EndSection Section "InputDevice" Driver "rfbmouse" Identifier "vncMouse" EndSection --------------------------- Add the following lines in de "Device" section. These are the normal vnc options. --------------------------- Section "Device" ...... Option "rfbport" "5900" Option "dontdisconnect" Option "usevnc" EndSection --------------------------- Now add the vnc mouse and keyboard to the "serverLayout" section. --------------------------- Section "ServerLayout" ...... InputDevice "vncKeyboard" "ExtraKeyboard" InputDevice "vncMouse" "ExtraPointer" EndSection --------------------------- Your XF86config file is now setup. you still have to copy the vnc.o module into the "/usr/X11R6/lib/modules" dir for X to see it. With XFree4.2.0 you have to replace the X driver in the "/usr/X11R6/lib/modules/drivers" dir with the driver of XF4VNC. This will break the 3D capability of your VGA card. With Xfree4.3.0 this is no longer needed. If I remember correctly. XF4VNC can use the tight compression of tightvnc project. This a VNC client and server from low bandwidth setups. XF4VNC has one drawback. Namely when you connect to the host you can no longer get to the text consol. Somehow it locks the X server. You need to restart X then. Hope this helps, Stefan. Hope this
S. Bulterman wrote:
This is what I had do to get it working on my laptop with SuSE 7.2 XFree4.2.0 kernel 2.4.18. Edit your "/etc/X11/XF86config" by adding the following lines:
Yes! That's it. Thank you very much. While the other answers were of some value, they fell short. I just got my SuSE 9.0 last night and already installed it at home but that doesn't mean I can upgrade all PCs I have anything to do with or those of friends. If possible I am going to try this today Damon Register
S. Bulterman wrote:
Haven't tried it wit SuSE 9.0.
As others have said, it is easy for the latest SuSE. Remote desktop sharing is already built in so there is no need to install or tamper with anything.
This is what I had do to get it working on my laptop with SuSE 7.2 XFree4.2.0 kernel 2.4.18.
That was my problem. I couldn't get anything working with SuSE 8.0. xf4vnc from http://xf4vnc.sourceforge.net/ was the answer.
Edit your "/etc/X11/XF86config" by adding the following lines:
I found that this wasn't really necessary but interesting. I downloaded the project and unzipped in a temporary space. The README file just instructed to ./install.sh On restarting X, vnc still wasn't working. I found the /var/log/XFree86.0.log file with told me that the vnc.so module was for XFree 4.3 while I had XFree 4.2. On visiting http://xf4vnc.sourceforge.net/ again, I found something I had missed: for older XFree use -ignoreABI flag. That did it and the PC accepted a vnc connection request from another computer. So, lesson learned for XFree 4.2: 1. get xf4vnc from http://xf4vnc.sourceforge.net/ 2. expand project 3. ./install.sh 4. startx -- -ignoreABI Thanks for all your help Damon Register
I have had no problems with this since I first tried it in 8.1 (I think). I simply select "Desktop Sharing" from the SuSE KDE menu, it allows me to do an invitation to a host to connect to 192.168.10:0 and gives me a password to use on this machine, plus enable me to use keyboard and mouse. I came over to this machine (192.168.10.3) and selected "Remote Desktop connection", picked 192.168.10.1:0 and the password. So I'm sending this using the Mandrake box as keyboard and screen. Currently the two boxes are SuSE 9.0 and Mandrake 9.1, but I've done this on 8.2 also, right here in my shack. Everything needed was installed by default on both Mandrake and SuSE builds. Regards Sid. Damon Register wrote:
Lester Caine wrote:
Windows machines, a simple enable and the linux machines are there as well.
It is amazing just how much functionality is available 'out of the box'. It far outdoes WindowsXP ;)
The problem is that this seems to be a very recent development. In trying to find that kdenetwork3-vnc that a few mentioned earlier it appears in a more recent kde than is with SuSE 8.0. I am not an expert here but I suspect that one cannot take a module from one version of kde and stick it into an older one. Therefore I would likely have to upgrade kde which seems like a difficult task. From all of the kde upgrade discussions I have seen here in the past, I don't think I want to tackle that. While it might very well outdo XP out of the box, I am still disappointed that it took so long to get to a point that has existed in Windows for years.
Even though my SuSE 9.0 may arrive soon and this issue might be overcome by events, I can't accept being beaten so I will pursue this. It seems that xf4vnc is the only hope for older kde that doesn't have kdenetwork3-vnc. If anyone has had experience with xf4vnc with display :0 on SuSE, I would like to hear from you.
Damon Register
-- Sid Boyce .... Linux Only Shop.
On Thursday 30 October 2003 12:12, Damon Register wrote: [stuff deleted]
The problem is that this seems to be a very recent development. In trying to find that kdenetwork3-vnc that a few mentioned earlier it appears in a more recent kde than is with SuSE 8.0. I am not an expert here but I suspect that one cannot take a module from one version of kde and stick it into an older one. Therefore I would likely have to upgrade kde which seems like a difficult task. From all of the kde upgrade discussions I have seen here in the past, I don't think I want to tackle that.
While it might very well outdo XP out of the box, I am still disappointed that it took so long to get to a point that has existed in Windows for years.
Even though my SuSE 9.0 may arrive soon and this issue might be overcome by events, I can't accept being beaten so I will pursue this. It seems that xf4vnc is the only hope for older kde that doesn't have kdenetwork3-vnc. If anyone has had experience with xf4vnc with display :0 on SuSE, I would like to hear from you.
Damon Register
You are going to have to upgrade something somewhere to get access to :0 with VNC on a SuSE 8.0 box anyway. You are either going to have to upgrade KDE or XFree86 one. You can use VNC or XDMCP either one with what you currently have but not on :0. XF4VNC, while I haven't used it, has some special instructions for pre 4.3 versions of XFree86. You obviously won't be running a 4.3 version without an upgrade to XFree86 with SuSE 8.0. I can't remember what version was with 8.0, I do know that 8.1 had XFree86 4.2, so it isn't likely that 8.0 had XFree86 4.3. As to getting to a point that has existed in Windows for years, I was doing remote X sessions long before I could do remote Windows sessions. Remote X sessions go back to the beginning of X without any additional software required, while remote Windows sessions only arrived with WinXP (without any additional software required) on the desktop. There have been things like PC Anywhere, Citrix, Terminal Services, but they were additional or server machine functions, not desktop. The early remote desktop access in X was no to :0, but it was remote X none the less. I actually find much less need to be accessing the desktop than I do to just have access to the machine remotely at any rate. Accessing the desktop is only useful to show someone how to do something. There is much more that can be done on remote X sessions. -- Kelly L. Fulks Home Account near Huntsville, AL
On 10/31/2003 08:02 AM, Kelly Fulks wrote:
Accessing the desktop is only useful to show someone how to do something. There is much more that can be done on remote X sessions.
I have found there isn't even a need to remote the whole desktop. I have been helping someone remotely, and though i am not connecting to :0, I am able, via ssh -X (twice actually since I am helping on an internal to his LAN machine) to open an X application, i.e. xcdroast and konqueror, which open as just the app on my KDE desktop. I would assume it would take less bandwidth to just display an app vs the whole desktop. I'm sure there is more functionality available than I know, I keep learning all the time. ;-) -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Kelly Fulks wrote:
On Thursday 30 October 2003 09:15, Damon Register wrote:
J Lake wrote:
The writer is probably correct that sharing display 0 using VNC CAN be done. I have not tried that. I got an error about an X server already running on
So far everyone is dancing around the subject. Sr. Sanchez, are you trying to connect to the host's main desktop :0 as I am? Connecting to any other desktop is of no value to me. According to http://www.realvnc.com/how.html, "For the individual user, one common scenario is using VNC to help troubleshoot the computer of a distant less-technically-savvy relative. In other words, sitting at your desk in Baltimore, you could use VNC to take control of your mother's PC in London and show her how to install and use some new software package by actually doing it yourself." Connecting to any other desktop besides :0 doesn't accomplish this.
It seems at this point that serving :0 can't be done with VNC alone. I found that on the realvnc website. One person mentioned xf4vnc and that looks promising but also rather complicated so I will have to research that more
Damon Register
OK, the answer is (if you are running KDE) that you can do this. You can connect to desktop :0 and you can control it, if you set everything up properly.
1. Install kdenetwork3-vnc 2. KDE Menu -> Control Center 3. Internet & Network 4. Desktop Sharing 5. Check Allow uninvited connections (this allows you to connect at anytime) 6. Check Allow uninvited connections to control the desktop 7. Enter a password and make it a very good one as your desktop will potientially be exposed to the internet depending upon how your network is configured 8. Apply 9. File -> Quit 10. Connect from remote machine
You may have to logout and login, it has been too long since I set this up to remember. But it does work. It is desktop :0.
Thanks a lot it worked perfectly. Jose
Damon Register wrote:
Jose Sanchez wrote:
1) make sure that you have remote desktop sharing (KDE) or VNC (Linux or Windows) configured on the remote host
I have been following this thread because I want to do remost assistance too but so far I am confused. Where is the KDE remote desktop sharing that you mentioned?
So far I haven't been able to connect to or from a Linux PC. I installed the rdesktop package but I got the impression that it is for connecting to NT machines. I get the impression from this discussion that it will connect to Linux PCs also. Just what is rdesktop used for and what is required on the remote end (either Windows or Linux) in order for rdesktop to connect?
I tried using VNC but on the Linux side it doesn't give me what I need. In order to be used as a remote assistance tool, I need to see remotely the same thing the local user sees, not the nearly blank window I see when connecting to a Linux (SuSE 8.0) PC that is running vncserver
Damon Register
You could use XF4VNC plugin for X. This isn't tied to KDE only, but works for every windowmanager. You can find it on sourceforge. Hope this helps, Stefan.
S. Bulterman wrote:
You could use XF4VNC plugin for X. This isn't tied to KDE only, but works for every windowmanager. You can find it on sourceforge.
I found it and installed but there is very little info with it. What do I do with it? I still have not been able to find enough info to figure out how to get started Damon Register
participants (13)
-
Damian O'Hara -
Damon Register -
Damon Register -
J Lake -
Joe Morris (NTM) -
Jose Sanchez -
Kelly Fulks -
Ken Schneider -
Lester Caine -
pinto -
Richard Bos -
S. Bulterman -
Sid Boyce