Any Go To Assist alternatives for Linux
in [General Linux]
|
From: Marcel Bruinsma on 30 Sep 2009 21:25 Am Donnerstag, 1. Oktober 2009 00:48, Keith Keller a écrit : > On 2009-09-30, despen(a)verizon.net <despen(a)verizon.net> wrote: >> >> I believe that is ONE of the ways that it runs, but from the >> TightVNC main page: >> >> TightVNC is a free remote control software package. >> With TightVNC, you can see the desktop of a remote >> machine and control it with your local mouse and >> keyboard, just like you would do it sitting in the >> front of that computer. > > TightVNC runs exactly this way on Windows. If you read > the vncserver man page, however, it implies that it does > not run this way on unix/linux. > > http://www.tightvnc.com/vncserver.1.php > > "vncserver is a wrapper script for Xvnc, the free X server > for VNC (Virtual Network Computing). It provides all > capabilities of a standard X server, but does not connect > to a display for itself. Instead, Xvnc creates a virtual > desktop you can view or control remotely using a > VNC viewer." > > The man page for Xvnc is similar. But neither explicitly > state outright that it can not control the display and > keyboard on the console. Snippet from the Xvnc manual: « -QueryConnect » Prompts the user of the desktop to explicitly accept or » reject incoming connections. This is most useful when » using the vnc.so module or x0vncserver(1) program to » access an existing X desktop via VNC. » How does this work? Does x0vncserver start an Xvnc instance, that connects to a (locally?) running X server, and subsequently waits for incoming vncviewer clients? -- printf -v email $(echo \ 155 141 162 143 145 154 142 162 165 151 \ 156 163 155 141 100 171 141 150 157 157 056 143 157 155|tr \ \\\\) # Live every life as if it were your last! #
From: Keith Keller on 1 Oct 2009 00:52 On 2009-10-01, Marcel Bruinsma <mb(a)nomail.afraid.org> wrote: > > Snippet from the Xvnc manual: > > � -QueryConnect > � Prompts the user of the desktop to explicitly accept or > � reject incoming connections. This is most useful when > � using the vnc.so module or x0vncserver(1) program to > � access an existing X desktop via VNC. � This man page is likely for RealVNC, not TightVNC. > How does this work? Does x0vncserver start an Xvnc > instance, that connects to a (locally?) running X server, > and subsequently waits for incoming vncviewer clients? I don't recall if I posted this, but here's the x0vncserver man page: http://www.realvnc.com/products/free/4.1/man/x0vncserver.html So it seems like that's what x0vncserver does, but there is probably a huge devil in the details. :) --keith -- kkeller-usenet(a)wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information
From: André Gillibert on 1 Oct 2009 05:02 Robert Riches <spamtrap42(a)verizon.net> wrote: > > At my previous consulting assignment, the IT was exclusively > Windhose. The computer in my assigned cubicle was running > Windhose XP. On one occasion, I needed to have a sysadmin do > something with a license registration. She took over the mouse > and keyboard to do the operation while I watched. > > I asked her very directly whether Windhose it would be possible > for her to log in remotely to do the operation without having to > take over the mouse, keyboard, and screen. She said it is not > possible with XP. She said it would be possible with a newer > (high-priced) special server version of Windhose, but not with a > "desktop" version. > With Windows XP Pro, it's possible to log remotely with RDP and not locally show the remote screen contents. But, due to a software feature lock, whenever somebody logs in remotely, any local user is switched to the fast user switching login screen without being unlogged, but, unable to continue their work. If the local user tries to login or switch to his session, the remote user is disconnected. On Windows Server 2003, more than one user may be connected at once. There's a hack (which may be legal or illegal, depending on user's country laws, but Microsoft would certainly hate you if you did it) to enable the Windows Server 2003 behavior on Windows XP. This misfeature of Windows XP is designed by Microsoft to make people buy the expensive Microsoft Windows Huge Enterprise Server 2008 for Large Networks with More Than One Computer 64-bit Edition for x86 extended systems. That's similar to the 2 disk drives and 1 NIC limitation of Windows Storage Server 2003 Express Edition. -- André Gillibert
From: Stan Bischof on 1 Oct 2009 09:05 Robert Riches <spamtrap42(a)verizon.net> wrote: > > At my previous consulting assignment, the IT was exclusively > Windhose. The computer in my assigned cubicle was running > Windhose XP. On one occasion, I needed to have a sysadmin do > something with a license registration. She took over the mouse > and keyboard to do the operation while I watched. > > I asked her very directly whether Windhose it would be possible > for her to log in remotely to do the operation without having to > take over the mouse, keyboard, and screen. She said it is not > possible with XP. She said it would be possible with a newer > (high-priced) special server version of Windhose, but not with a > "desktop" version. > You should have hired a more knowledgable IT person. This is simply not correct. But back to Linux. The Windows folks can take care of themselves somewhere else. Stan
From: John Hasler on 1 Oct 2009 09:21
Stan writes: > You should have hired a more knowledgable IT person. Consultants don't usually hire IT people. > This is simply not correct. I suspect that by "desktop" version he means "Windows XP Home". According to Microsoft that does not include "Remote Desktop". I don't know why he'd be using Home at a business, though. -- John Hasler jhasler(a)newsguy.com Dancing Horse Hill Elmwood, WI USA |