|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[ More Info ]
If you go to My Computer on the remote system or use Windows Explorer, you should see the drives on the local system from which you connected listed among the drives visible on the remote system.
References:
I sometimes encounter a problem where I can't see the taskbar at the
bottom of the Windows display or the bottom of windows displayed on the
remote Windows system due to differences in the resolution for the
screen on the Linux/Unix system and the resolution of the Windows system.
The problem can be resolved by specifying the -f option when
starting rdesktop, so that you get a full screen display., e.g.
rdesktop -0 -f -u jsmith 192.168.0.44. But what do you do
when you wish to put the remote session in a window rather than have it
occupy the full screen without disconnecting? You can hit the
Ctrl-Alt-Enter keys simultaneously to switch to a windowed
view. You can also use Ctrl-Alt-Enter to switch to a full-screen
view, if you didn't start redesktop with the -f
option.
References:
To get Windows Defender to accept RealVNC, select "always allow" for the action and then click on "Apply Actions".
When you are configuring RealVNC during installation, under the Connections tab in RealVNC, you can set the ports or retain the default ports that will be used for listening for connections, if you are installing the server portion of the software so you can connect remotely to the system you are installing it on. The default values are shown below:
Accept connections on port: 5900
Disconnect idle clients after (seconds): 3600
Serve Java viewer via HTTP on port: 5800
Under Access Control in the Connections section, you can check "Only accept connections from the local machine", if you wnat to require access to be through an SSH connection.
If you install the server portion of the software to run as a service
on the Windows system, but don't want it to start automatically, click
on the Windows Start button, select Run and type
services.msc. Find "VNC Server Version 4" within the services
list, double-click on it and change the startup type from "automatic" to
"manual", then click on OK.
References:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
key in the registry of the remote system. By changing the
value of fDenyTSConnection from 1 to 0 and
then rebooting the system, you can enable Remote Desktop
support.
net start command. Issuing it without any
arguments given to it shows a list of available services on the system.
If you use the find with it, you can filter the list of
displayed services to see just the name for the pcAnywhere service.
C:\Documents and Settings\administrator>net start | find /i "pcanywhere"
pcAnywhere Host Service
Knowing that it is "pcAnywhere Host Service", you can then use net stop
"pcanywhere host service" to stop the service and net start
"pcanywhere host service" to restart it.
References:
[/os/windows/software/remote-control/pcanywhere] permanent link
Acme\jdoe. Or you can use the form jdoe@acme.com.Computer Management window.Or you can resolve the problem by logging into the computer for which the user needs access and then taking the following steps, if that system is a Windows XP Professional system.
Acme\jdoe. Or you can use the form jdoe@acme.com.Computer Management window.With rdesktop you get an X Window display on your Linux/Unix system that looks very similar to what you would see if you were sitting at the Windows system. It works much like Windows remote desktop software that allows you to control one Windows system with another.
If you are using a Linux system, rdesktop may already be present. You can check
by issuing the command rdesktop. If it isn't present,
installing rdesktop is easy. Download the file from
www.rdesktop.org,
SourceForge.net:rdesktop, or
here and then
issue the following commands on your Linux
or Unix system, subsituting the particular version number you have downloaded:
tar -xvzf rdesktop-1.4.1.tar.gz
cd rdesktop-1.4.1
./configure
make
make install
You can then run the software with the rdesktop command. E.g., if I wanted
to connect to a Windows system with IP address 192.168.0.3, I could issue the command
rdesktop 192.168.0.3. If the Windows system is behind a firewall, you
will need to open TCP port 3389.
I often boot a Windows system with a Knoppix Linux Live CD when I am working at a site, so that I can be sure that I am working on a secure system rather than a system that may have been compromised by viruses, trojans, spyware, etc. If I need to access a server at the site, such as a Windows Small Business Server (SBS) 2003 server, I can still access it from the system booted into Knoppix Linux with a Live CD by using rdesktop. Knoppix Linux comes with rdesktop, but you may have another Linux Live CD, which doesn't already provide rdesktop. Since you are booting from a Live CD and can't alter its contents, you need to specify a directory that is stored in memory rather than on the CD when you are installing rdesktop. You can do so by using "--prefix" to specify the directory into which you wish to install it. Otherwise, you will get the following error when you attempt to install it.
$ make install
mkdir -p /usr/local/bin
mkdir: cannot create directory `/usr/local/bin': Permission denied
make: *** [installbin] Error 1
To eliminate the problem, you can use the following commands after you have downloaded the software into a virtual disk Live CDs will typically set up in memory. Suppose you have /ramdisk/tmp as such an area and you have made that your working directory.
tar -xvzf rdesktop-1.4.1.tar.gz
cd rdesktop-1.4.1
./configure --prefix=/ramdisk/tmp
make
make install
./rdesktop 192.168.0.3
Unless you specify otherwise, a new logon session will be established to the system.
The current one won't be terminated. But, perhaps a user is already logged onto the
system and you wish to connect to the current console session on the system, to see
exactly what you would see if you were sitting at the system. Then you should use
the -0 option to attach to the console, e.g. rdesktop -0
192.168.0.3. You can specify the userid to use with the -u option,
e.g. rdesktop -0 -u administrator 192.168.0.3. You may also want to
change the color depth with the -a option. The default value is 8-bit
color, which gives you only 256 colors. If you use -a 16, you will
get 16-bit color, which is 2 raised to the power of 16 colors, i.e. 65,536 colors.
If you use rdesktop alone with no options, you will get a list of other
available options for the command.
References:
From a Unix workstation running Solaris, I entered the command
ssh -L 5901:localhost:5900 administrator@192.168.0.5 to
establish an SSH connection to
the system with port 5901 on the Unix workstation being forwarded to
port 5900 on the Windows SBS 2003 server. Port 5900 is the default port
for a VNC server and the one I used on the Windows system. However,
when I tried to connect to the Windows system with vncviewer by connecting
to port 5901 on the Unix system, which then should be forwarded over the
SSH connection to port 5900 on the Windows system, I saw the message
"Local loop-back connections are disabled."
bash-2.03$ vncviewer localhost:1
VNC viewer for X version 4.0 - built Jun 14 2004 12:04:05
Copyright (C) 2002-2004 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Tue Nov 22 16:08:49 2005
CConn: connected to host localhost port 5901
CConnection: Server supports RFB protocol version 3.3
CConnection: Using RFB protocol version 3.3
Tue Nov 22 16:08:50 2005
main: Local loop-back connections are disabled.
Doing a Google search on the
error, I learned I needed to have the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3 on the Windows system set
to a DWORD value of "1". Since I had a command line prompt on the
Windows system via the SSH connection, I used the reg query
command to check the current value of that registry key. Sure enough,
its current value was "0".
C:\Documents and Settings\Administrator>reg query HKEY_LOCAL_MACHINE\SOFTWARE\OR
L\WinVNC3
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3
ConnectPriority REG_DWORD 0x0
DebugMode REG_DWORD 0x0
DebugLevel REG_DWORD 0x2
LoopbackOnly REG_DWORD 0x0
EnableHTTPDaemon REG_DWORD 0x1
EnableURLParams REG_DWORD 0x0
AllowLoopback REG_DWORD 0x0
AuthRequired REG_DWORD 0x1
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default
Fortunately, the reg command can also be used to modify the
registry from the command line.
C:\Documents and Settings\Administrator>reg add HKEY_LOCAL_MACHINE\SOFTWARE\ORL\
WinVNC3 /v AllowLoopback /t REG_DWORD /d 1
Value AllowLoopback exists, overwrite(Yes/No)? yes
The operation completed successfully.
The REG ADD command uses the following syntax:
REG ADD KeyName [/v ValueName | /ve] [/t Type] [/s Separator] [/d Data] [/f]
In this case, the parameters used have the following meaning:
/v The value name, in this case "AllowLoopback", to
be added under the selected key.
/t Allows one to specify the data type, which can be
REG_SZ, REG_MULTI_SZ, REG_EXPAND_SZ, REG_DWORD, REG_BINARY, or REG_NONE.
If none is specified, REG_SZ is assumed. In this case REG_DWORD is needed.
/d The data to assign to the registry ValueName being
added, which is "1" in this case.
Another reg query HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3
shows the value was changed.
C:\Documents and Settings\Administrator>reg query HKEY_LOCAL_MACHINE\SOFTWARE\OR
L\WinVNC3
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3
ConnectPriority REG_DWORD 0x0
DebugMode REG_DWORD 0x0
DebugLevel REG_DWORD 0x2
LoopbackOnly REG_DWORD 0x0
EnableHTTPDaemon REG_DWORD 0x1
EnableURLParams REG_DWORD 0x0
AllowLoopback REG_DWORD 0x1
AuthRequired REG_DWORD 0x1
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default
After modifying the registry value, you then must stop and restart the VNC Server service.
C:\Documents and Settings\Administrator>net stop "VNC Server"
The VNC Server service is stopping..
The VNC Server service was stopped successfully.
C:\Documents and Settings\Administrator>net start "VNC Server"
The VNC Server service is starting.
The VNC Server service was started successfully.
You should then be able to use vncviewer localhost:1 to
access the remote system with VNC. After the message about the
protocol version, you should see a VNC Authentication window
open.
bash-2.03$ vncviewer localhost:1
VNC viewer for X version 4.0 - built Jun 14 2004 12:04:05
Copyright (C) 2002-2004 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Tue Nov 22 17:07:42 2005
CConn: connected to host localhost port 5901
CConnection: Server supports RFB protocol version 3.3
CConnection: Using RFB protocol version 3.3
In this case, I was then able to enter the VNC authorization password and then hit Ctrl-Alt-Del on the Solaris system to enter the user name and password for the Windows SBS 2003 server.
References:
LapLink has a mechanism for changing the port number used for establishing connections. It is a more cumbersome mechansm than that provided by some other Windows remote control programs, such as Symantec's pcAnywhere, but it is possible to change the port.
LapLink uses UDP and TCP ports 1547 by default. But,
if you edit the LLW.INI file, that will be in the directory
C:\Windows\TSI32\LLW, you can get it to use another port.
In LLW.INI, in the [TCPIP] section, add
ListenPort= followed by the port
number you wish to use as below:
[TCPIP]
Enabled=Yes
ListenPort=5549
What makes this approach more cumbersome is that if you need to connect to systems listening on different ports with LapLink, you need to edit the file, save your changes, and then restart LapLink to get it to use the port you want to use. If you want to go back to the default port, you can just put in "1547" for the ListenPort value.
