How to: start only vnc server without local X instance - Suse 9.0 ?
Hi, I'd like to have only vnc server to server X windows to remote vnc viewers without starting local X (to have only console). How to do this ? Thanks in advance, Robert.
Robert, On Friday 27 August 2004 14:35, Robert Rozman wrote:
Hi,
I'd like to have only vnc server to server X windows to remote vnc viewers without starting local X (to have only console).
How to do this ?
Does that make any sense? VNC is about so-called "desktop sharing" and is implicitly about GUIs. If all you need in the way of remote access is a CLI, then SSH is what you want. Conversely, if you want to run programs on your Linux box and interact with them from the keyboard, display and mouse of a remote site, then you want to invoke those programs on your box with the DISPLAY environment variable set to refer to the host where that keyboard, display and mouse exist and, of course, the necessary security setup in place on that X server. Don't ask me about setting up non-local X service, however. I've never done it.
Thanks in advance,
Robert.
Randall Schulz
On Sat, 2004-08-28 at 02:17, Randall R Schulz wrote:
Robert,
On Friday 27 August 2004 14:35, Robert Rozman wrote:
Hi,
I'd like to have only vnc server to server X windows to remote vnc viewers without starting local X (to have only console).
How to do this ?
Does that make any sense? VNC is about so-called "desktop sharing" and is implicitly about GUIs. If all you need in the way of remote access is a CLI, then SSH is what you want.
It makes a lot of sense. If you only use the machine remote there is no need to run a FULL blown KDE on a screen that is turned of... What he wants is the Linux version of terminal server, and VNC is a great way to do it...
Conversely, if you want to run programs on your Linux box and interact with them from the keyboard, display and mouse of a remote site, then you want to invoke those programs on your box with the DISPLAY environment variable set to refer to the host where that keyboard, display and mouse exist and, of course, the necessary security setup in place on that X server.
That depends on the the effects the latenca has on the program. Some programs work great this way, some don't! Additionally, with remote vnc you can use KDE over small throughput lines.
Don't ask me about setting up non-local X service, however. I've never done it.
SuSE is prepared for this option... In Yast->system->/etc/sysconfig editor Search for DisplayManager section Set the option there to the following values: DISPLAYMANAGER_REMOTE_ACCESS="yes" DISPLAYMANAGER_ROOT_LOGIN_REMOTE="yes" (If allow root) DISPLAYMANAGER_STARTS_XSERVER="no" (don't start local x-win) KDM_SHUTDOWN="auto" "Who is allowed to shutdown) DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no" Then you need to setup VNC to work off Xinet.d, which SuSE has also prepared for you.... Open a Unix shell and edit the file: /etc/xinetd.d/vnc in the section “service vnc11” change the “server_args” to the following: server_args = :42 -inetd -once -query local host -desktop Westrick_GmbH -geometry 1280x1024 -depth 16 On the disable line change “yes” to “no”, execute the following line in a root shell: /etc/init.d/xinetd reload. Note: Westrick_GmbH cannot contian Spaces..., and is the name of your host... Good Luck Jerry
Thanks in advance,
Robert.
Randall Schulz
Jerome, On Saturday 28 August 2004 09:46, Jerome R. Westrick wrote:
On Sat, 2004-08-28 at 02:17, Randall R Schulz wrote:
Robert,
On Friday 27 August 2004 14:35, Robert Rozman wrote:
Hi,
I'd like to have only vnc server to server X windows to remote vnc viewers without starting local X (to have only console).
How to do this ?
Does that make any sense? VNC is about so-called "desktop sharing" and is implicitly about GUIs. If all you need in the way of remote access is a CLI, then SSH is what you want.
It makes a lot of sense. If you only use the machine remote there is no need to run a FULL blown KDE on a screen that is turned of...
What he wants is the Linux version of terminal server, and VNC is a great way to do it...
One thing from Microsoft that really impressed me (and there aren't many such things) is the the protocol used in their Terminal Server. Even over a 56K modem, it's pretty responsive. In fact, it compares quite favorably with VNC between two systems with 6Mb / 600 Kb ADSL lines. The VNC experience I'm referring to was recent. Did I fail to configure VNC optimally? Because it was really too slow to be very useful. It was pretty clear from watching it run that the protocol was strictly a remote bitblt whereas it seemed that Terminal Server had an elaborate protocol for various special operations (buttons, text, other widgets, etc. -- it really seemed that the protocol was a remote version of the GUI portion of the win32 API, which of course can drastically cut the amount of data that must be transmitted to effect a given result on the display).
Conversely, if you want to run programs on your Linux box and interact with them from the keyboard, display and mouse of a remote site, then you want to invoke those programs on your box with the DISPLAY environment variable set to refer to the host where that keyboard, display and mouse exist and, of course, the necessary security setup in place on that X server.
That depends on the the effects the latenca has on the program. Some programs work great this way, some don't! Additionally, with remote vnc you can use KDE over small throughput lines.
Don't ask me about setting up non-local X service, however. I've never done it.
SuSE is prepared for this option...
...
Thanks for that information. I don't know when I'll need it, but at least I'll know where to go to handle this situation should it arise.
Good Luck Jerry
Randall Schulz
For Widnows VNC server try the Ultra-Vnc variant it has advanced devices to improve this problem... But why don't you just use the Linux Rdesktop client? The MS protocol and more importantly the deeply linked code, will always be faster than vnc. So use it! Use Yast to install RDesktop, I use all day everyday! Jerry On Sat, 2004-08-28 at 19:02, Randall R Schulz wrote:
Jerome,
On Saturday 28 August 2004 09:46, Jerome R. Westrick wrote:
On Sat, 2004-08-28 at 02:17, Randall R Schulz wrote:
Robert,
On Friday 27 August 2004 14:35, Robert Rozman wrote:
Hi,
I'd like to have only vnc server to server X windows to remote vnc viewers without starting local X (to have only console).
How to do this ?
Does that make any sense? VNC is about so-called "desktop sharing" and is implicitly about GUIs. If all you need in the way of remote access is a CLI, then SSH is what you want.
It makes a lot of sense. If you only use the machine remote there is no need to run a FULL blown KDE on a screen that is turned of...
What he wants is the Linux version of terminal server, and VNC is a great way to do it...
One thing from Microsoft that really impressed me (and there aren't many such things) is the the protocol used in their Terminal Server. Even over a 56K modem, it's pretty responsive. In fact, it compares quite favorably with VNC between two systems with 6Mb / 600 Kb ADSL lines.
The VNC experience I'm referring to was recent. Did I fail to configure VNC optimally? Because it was really too slow to be very useful. It was pretty clear from watching it run that the protocol was strictly a remote bitblt whereas it seemed that Terminal Server had an elaborate protocol for various special operations (buttons, text, other widgets, etc. -- it really seemed that the protocol was a remote version of the GUI portion of the win32 API, which of course can drastically cut the amount of data that must be transmitted to effect a given result on the display).
Conversely, if you want to run programs on your Linux box and interact with them from the keyboard, display and mouse of a remote site, then you want to invoke those programs on your box with the DISPLAY environment variable set to refer to the host where that keyboard, display and mouse exist and, of course, the necessary security setup in place on that X server.
That depends on the the effects the latenca has on the program. Some programs work great this way, some don't! Additionally, with remote vnc you can use KDE over small throughput lines.
Don't ask me about setting up non-local X service, however. I've never done it.
SuSE is prepared for this option...
...
Thanks for that information. I don't know when I'll need it, but at least I'll know where to go to handle this situation should it arise.
Good Luck Jerry
Randall Schulz
Jerome, On Saturday 28 August 2004 10:21, Jerome R. Westrick wrote:
For Widnows VNC server try the Ultra-Vnc variant it has advanced devices to improve this problem...
But why don't you just use the Linux Rdesktop client? The MS protocol and more importantly the deeply linked code, will always be faster than vnc. So use it!
Wow. I was unaware that there was a real alternative to VNC on the Linux side, let alone an implementation of the Terminal Services protocols. I always assumed the Windows protocol was proprietary (unpublished) and also kind of assumed it would be non-trivial to reverse engineer it.
Use Yast to install RDesktop, I use all day everyday!
Jerry
Thanks again for the information. Randall Schulz
Hi,
thanks for responses.
I'm just curious about Rdesktop thing - can I have server on Linux and
client on windows ? Which apps ?
Regards,
Robert.
----- Original Message -----
From: "Jerome R. Westrick"
For Widnows VNC server try the Ultra-Vnc variant it has advanced devices to improve this problem...
But why don't you just use the Linux Rdesktop client? The MS protocol and more importantly the deeply linked code, will always be faster than vnc. So use it!
Use Yast to install RDesktop, I use all day everyday!
Jerry
On Sat, 2004-08-28 at 19:02, Randall R Schulz wrote:
Jerome,
On Saturday 28 August 2004 09:46, Jerome R. Westrick wrote:
On Sat, 2004-08-28 at 02:17, Randall R Schulz wrote:
Robert,
On Friday 27 August 2004 14:35, Robert Rozman wrote:
Hi,
I'd like to have only vnc server to server X windows to remote vnc viewers without starting local X (to have only console).
How to do this ?
Does that make any sense? VNC is about so-called "desktop sharing" and is implicitly about GUIs. If all you need in the way of remote access is a CLI, then SSH is what you want.
It makes a lot of sense. If you only use the machine remote there is no need to run a FULL blown KDE on a screen that is turned of...
What he wants is the Linux version of terminal server, and VNC is a great way to do it...
One thing from Microsoft that really impressed me (and there aren't many such things) is the the protocol used in their Terminal Server. Even over a 56K modem, it's pretty responsive. In fact, it compares quite favorably with VNC between two systems with 6Mb / 600 Kb ADSL lines.
The VNC experience I'm referring to was recent. Did I fail to configure VNC optimally? Because it was really too slow to be very useful. It was pretty clear from watching it run that the protocol was strictly a remote bitblt whereas it seemed that Terminal Server had an elaborate protocol for various special operations (buttons, text, other widgets, etc. -- it really seemed that the protocol was a remote version of the GUI portion of the win32 API, which of course can drastically cut the amount of data that must be transmitted to effect a given result on the display).
Conversely, if you want to run programs on your Linux box and interact with them from the keyboard, display and mouse of a remote site, then you want to invoke those programs on your box with the DISPLAY environment variable set to refer to the host where that keyboard, display and mouse exist and, of course, the necessary security setup in place on that X server.
That depends on the the effects the latenca has on the program. Some programs work great this way, some don't! Additionally, with remote vnc you can use KDE over small throughput lines.
Don't ask me about setting up non-local X service, however. I've never done it.
SuSE is prepared for this option...
...
Thanks for that information. I don't know when I'll need it, but at least I'll know where to go to handle this situation should it arise.
Good Luck Jerry
Randall Schulz
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sun, 2004-08-29 at 17:50, Robert Rozman wrote:
Hi,
thanks for responses.
I'm just curious about Rdesktop thing - can I have server on Linux and client on windows ? Which apps ?
Nope Server is on Windows, and to the best of my knowledge not open source. Client on linux, so you can RDP to windows... Jerry
Regards,
Robert.
----- Original Message ----- From: "Jerome R. Westrick"
To: "Suse Users" Sent: Saturday, August 28, 2004 7:21 PM Subject: Re: [SLE] How to: start only vnc server without local X instance -Suse 9.0 ? For Widnows VNC server try the Ultra-Vnc variant it has advanced devices to improve this problem...
But why don't you just use the Linux Rdesktop client? The MS protocol and more importantly the deeply linked code, will always be faster than vnc. So use it!
Use Yast to install RDesktop, I use all day everyday!
Jerry
On Sat, 2004-08-28 at 19:02, Randall R Schulz wrote:
Jerome,
On Saturday 28 August 2004 09:46, Jerome R. Westrick wrote:
On Sat, 2004-08-28 at 02:17, Randall R Schulz wrote:
Robert,
On Friday 27 August 2004 14:35, Robert Rozman wrote:
Hi,
I'd like to have only vnc server to server X windows to remote vnc viewers without starting local X (to have only console).
How to do this ?
Does that make any sense? VNC is about so-called "desktop sharing" and is implicitly about GUIs. If all you need in the way of remote access is a CLI, then SSH is what you want.
It makes a lot of sense. If you only use the machine remote there is no need to run a FULL blown KDE on a screen that is turned of...
What he wants is the Linux version of terminal server, and VNC is a great way to do it...
One thing from Microsoft that really impressed me (and there aren't many such things) is the the protocol used in their Terminal Server. Even over a 56K modem, it's pretty responsive. In fact, it compares quite favorably with VNC between two systems with 6Mb / 600 Kb ADSL lines.
The VNC experience I'm referring to was recent. Did I fail to configure VNC optimally? Because it was really too slow to be very useful. It was pretty clear from watching it run that the protocol was strictly a remote bitblt whereas it seemed that Terminal Server had an elaborate protocol for various special operations (buttons, text, other widgets, etc. -- it really seemed that the protocol was a remote version of the GUI portion of the win32 API, which of course can drastically cut the amount of data that must be transmitted to effect a given result on the display).
Conversely, if you want to run programs on your Linux box and interact with them from the keyboard, display and mouse of a remote site, then you want to invoke those programs on your box with the DISPLAY environment variable set to refer to the host where that keyboard, display and mouse exist and, of course, the necessary security setup in place on that X server.
That depends on the the effects the latenca has on the program. Some programs work great this way, some don't! Additionally, with remote vnc you can use KDE over small throughput lines.
Don't ask me about setting up non-local X service, however. I've never done it.
SuSE is prepared for this option...
...
Thanks for that information. I don't know when I'll need it, but at least I'll know where to go to handle this situation should it arise.
Good Luck Jerry
Randall Schulz
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Jerome, On Sunday 29 August 2004 16:32, Jerome R. Westrick wrote:
On Sun, 2004-08-29 at 17:50, Robert Rozman wrote:
Hi,
...
I'm just curious about Rdesktop thing - can I have server on Linux and client on windows ? Which apps ?
Nope Server is on Windows, and to the best of my knowledge not open source.
So it does not help those who need "peer-to-peer" desktop sharing. The Linux user can only connect to a Windows Terminal Server, which I believe runs only on the Server variants of Windows 2000 and XP, right? So in my case, the need to share a desktop with a remote coworker who has a basic Windows XP (Pro, I think) installation, VNC is still the only option open to us, right? That's too bad.
Client on linux, so you can RDP to windows...
Jerry
Randall Schulz
On Mon, 2004-08-30 at 01:46, Randall R Schulz wrote:
Jerome,
On Sunday 29 August 2004 16:32, Jerome R. Westrick wrote:
On Sun, 2004-08-29 at 17:50, Robert Rozman wrote:
Hi,
...
I'm just curious about Rdesktop thing - can I have server on Linux and client on windows ? Which apps ?
Nope Server is on Windows, and to the best of my knowledge not open source.
So it does not help those who need "peer-to-peer" desktop sharing. The Linux user can only connect to a Windows Terminal Server, which I believe runs only on the Server variants of Windows 2000 and XP, right?
So in my case, the need to share a desktop with a remote coworker who has a basic Windows XP (Pro, I think) installation, VNC is still the only option open to us, right?
Xp Pro has Remote Desktop. XP Pro and Home have a remote assistence function to allow someone share thier desktop. I use RDP on to take controll of windows machines (where available), I use VNC to "share" desktop. But I guess that's my personal preference. To share or controll a linux remote then vnc and remote X-Windows are your only choice. Here I use both. For example: I usually watch the log files of my server via remote-X, while I do my emailing via vnc with evolution. (Evolution don't do to well with remote-X and the huge folders I got.) I find that the people I help out with (sharing), have it easier if I place an Icon on thier destop called "Send Screen To Jerry", which they can double click. This is much easier than going through the Remote Assistance dialog! Jerry
That's too bad.
Client on linux, so you can RDP to windows...
Jerry
Randall Schulz
Jerome R. Westrick wrote:
<SNIP>
Open a Unix shell and edit the file: /etc/xinetd.d/vnc in the section “service vnc11” change the “server_args” to the following:
server_args = :42 -inetd -once -query local host -desktop Westrick_GmbH -geometry 1280x1024 -depth 16
On the disable line change “yes” to “no”, execute the following line in a root shell:
/etc/init.d/xinetd reload.
Note: Westrick_GmbH cannot contian Spaces..., and is the name of your host...
Good Luck Jerry
You can also turn on these services in Yast-->Network Services-->Network Services (inetd). This way you won't have to edit the file. Without the desktop setting in the file, your window will say "nobody's desktop" but will function the same. If you do decide to edit the file, notice that "local host" above should be "localhost". Also try putting the desktop value in quotes if you want to use two or more words. HTH, Louis
This might help, http://www.fedoraforum.org/forum/archive/index.php/t-1606.html On Fri, 2004-08-27 at 15:35, Robert Rozman wrote:
Hi,
I'd like to have only vnc server to server X windows to remote vnc viewers without starting local X (to have only console).
How to do this ?
Thanks in advance,
Robert. -- Thank you,
Matt Duval Sr. Network Engineer HealthTrans www.healthtrans.com "Transforming Healthcare, One Transaction At A Time" (720) 493-8252 6061 South Willow Drive Suite 125 Greenwood Village, CO 80111
participants (6)
-
Jerome R. Westrick
-
Jerome R. Westrick
-
Louis Richards
-
Matt T. Duval
-
Randall R Schulz
-
Robert Rozman