Remote Desktop - Revision history

Tigersharke at 08:09, 26 April 2013

2013-04-26T08:09:17Z

Tigersharke at 20:30, 22 April 2013

2013-04-22T20:30:55Z

Drulavigne at 16:05, 16 April 2013

2013-04-16T16:05:59Z

Drulavigne: Marked this version for translation

2013-04-12T19:49:12Z

Marked this version for translation

Show changes

Drulavigne at 19:49, 12 April 2013

2013-04-12T19:49:05Z

Tigersharke: /* Connecting with KDE's KRDC */

2013-04-01T12:43:40Z

‎Connecting with KDE's KRDC

Tigersharke at 10:22, 5 March 2013

2013-03-05T10:22:31Z

Drulavigne at 19:20, 6 November 2012

2012-11-06T19:20:27Z

Drulavigne at 17:59, 6 November 2012

2012-11-06T17:59:53Z

Vater at 22:47, 7 September 2012

2012-09-07T22:47:14Z

@@ Line 1: / Line 1: @@
-<translate>
+<noinclude><translate>
 <!--T:1-->
-<noinclude>{{NavHeader|back=Windows Emulation|forward=Thin Client}}</noinclude>
+{{NavHeader|back=Windows Emulation|forward=Thin Client}}</noinclude>
 <!--T:2-->
@@ Line 120: / Line 120: @@
 <noinclude>
 {{refheading}}
 [[category:Remote Desktop]]
 <languages/>
 </translate>

@@ Line 123: / Line 123: @@
 [[category:Common Tasks]]
 [[category:Remote Desktop]]
 </noinclude>
 </translate>

← Older revision		Revision as of 16:05, 16 April 2013
Line 1:		Line 1:
−	<translate><!--T:1-->	+	<translate>
		+
		+	<!--T:1-->
	<noinclude>{{NavHeader\|back=Windows Emulation\|forward=Thin Client}}</noinclude>		<noinclude>{{NavHeader\|back=Windows Emulation\|forward=Thin Client}}</noinclude>

@@ Line 1: / Line 1: @@
-<noinclude>{{NavHeader|back=Windows Emulation|forward=Thin Client}}</noinclude>
+<translate><noinclude>{{NavHeader|back=Windows Emulation|forward=Thin Client}}</noinclude>
 [[File:Krdc.png|thumb|393px|'''Figure 9.7a: Creating a Connection Using KRDC''']]
@@ Line 86: / Line 86: @@
 [[category:Remote Desktop]]
 </noinclude>

@@ Line 56: / Line 56: @@
 Once you press OK, the connection should be initiated and you will receive pop-up messages asking for a username then a password; the details you provide must match a user account on the system you are connecting to. Once your authentication details are confirmed, you should see the desktop of the other system. If you move your mouse, it will move on the other desktop as well. Click the button ''View Only'' in the top toolbar whenever you wish to disable this mouse behaviour. When you are finished your session, you can click the button ''Disconnect'' in the top toolbar.
-{{note|width=48.5%|if the connection fails, check on the remote computer that either the RDP software is enabled or that the VNC server is listening for connections. Also double-check that a firewall is not preventing the connection.}}
+{{note|width=48.5%|icon64=if the connection fails, check on the remote computer that either the RDP software is enabled or that the VNC server is listening for connections. Also double-check that a firewall is not preventing the connection.}}
 ==== Connecting with VNC ====

@@ Line 1: / Line 1: @@
 <noinclude>{{NavHeader|back=Windows Emulation|forward=Thin Client}}</noinclude>
 Occasionally it is useful to allow connections between desktop sessions running on different computers. This can be handy when troubleshooting a problem since both users will be able to see the error on the problematic system and either user can take control of the mouse and keyboard in order to fix the problem. Typically this is a temporary situation as providing access to one's computer allows a remote user the ability to both view and modify its settings.
@@ Line 7: / Line 9: @@
 === Connecting to Another Computer With RDP ===
-The {{citelink|wp|url=Remote_Desktop_Protocol|txt=remote desktop protocol (RDP)}} can be used to make a connection to another computer. This section will demonstrate what is needed on the remote computer for an RDP connection, how to connect using KDE's KRDC, and how to connect using VNC.
+The {{citelink|wp|url=Remote_Desktop_Protocol|txt=remote desktop protocol (RDP)}} can be used to make a connection to another computer. This section will demonstrate what is needed on the remote computer for an RDP connection, how to connect using KDE's KRDC, and how to connect using VNC.[[File:Krdc1.png|left|thumb|'''Figure 9.7b: Settings for the RDP Connection''']]
 ==== Preparing the Remote System ====
@@ Line 31: / Line 33: @@
 Figure 9.7a shows the initial KRDC screen which allows you to specify which system you wish to connect to.
-'''Figure 9.7a: Creating a Connection Using KRDC'''
+Use the drop-down menu to indicate whether the remote system is using RDP or VNC for the connection. Then type in the IP address of the system you wish to connect to. If you are connecting to a VNC system, the IP address needs to be followed by a colon and a number indicating the number of the session. Typically, the number will be 1 unless the VNC server is hosting multiple simultaneous connections. Once you press enter, the connection will be initiated and, if it is an RDP connection, you will see the screen shown in Figure 9.7b.
-−
-[[Image:Krdc.png]]
-−
-Use the drop-down menu to indicate whether the remote system is using RDP or VNC for the connection. Then type in the IP address of the system you wish to connect to. If you are connecting to a VNC system, the IP address needs to be followed by a colon and a number indicating the number of the session. Typically, the number will be 1 unless the VNC server is hosting multiple simultaneous connections. Once you press enter, the connection will be initiated and, if it is an RDP connection, you will see the screen shown in Figure 9.7b:
-−
-'''Figure 9.7b: Settings for the RDP Connection'''
-−
-[[Image:Krdc1.png]]
 Here is a quick overview of the settings:
@@ Line 45: / Line 39: @@
 '''Desktop resolution:''' since the contents of the screen are sent over the network, select the lowest resolution that still allows you to see what is happening on the other system. If you have a very fast network connection, you can choose a higher resolution; if you find that the other system is very slow to refresh its screen, try choosing a lower resolution.
-'''Color depth:''' choose the lowest color depth that allows you to see the other system; you can choose a higher color depth if the network connection is fast.
+'''Color depth:''' choose the lowest color depth that allows you to see the other system; you can choose a higher color depth if the network connection is fast.[[File:Krfb1a.png|thumb|393px|'''Figure 9.7c: Initiating a Connection Request Using krfb''']]
 '''Keyboard layout:''' this drop-down menu allows you to select the desired keyboard layout.
 '''Sound:''' this drop-down menu allows you to choose whether any sounds heard during the connection are produced on this system, the remote system, or to disable sound during the connection.
@@ Line 59: / Line 52: @@
 '''Remember password:''' {{citelink|url=http://docs.kde.org/development/en/kdeutils/kwallet/|txt=KWallet}} is KDE's password storage system. If this box stays checked, you will only need to input the password the first time you make this connection as it will be saved for you. If this is the first time you have stored a password using KWallet, it will prompt you for some information to set up your wallet.
-If it is a VNC connection, you will be able to choose your connection type (speed), screen resolution, and have the option to remember the password.
+If it is a VNC connection, you will be able to choose your connection type (speed), screen resolution, and have the option to remember the password.[[File:Krfb1.png|thumb|393px|'''Figure 9.7d: Connection Invitation Created Using krfb''']]
 Once you press OK, the connection should be initiated and you will receive pop-up messages asking for a username then a password; the details you provide must match a user account on the system you are connecting to. Once your authentication details are confirmed, you should see the desktop of the other system. If you move your mouse, it will move on the other desktop as well. Click the button ''View Only'' in the top toolbar whenever you wish to disable this mouse behaviour. When you are finished your session, you can click the button ''Disconnect'' in the top toolbar.
-'''NOTE:''' if the connection fails, check on the remote computer that either the RDP software is enabled or that the VNC server is listening for connections. Also double-check that a firewall is not preventing the connection.
+{{note|width=48.5%|if the connection fails, check on the remote computer that either the RDP software is enabled or that the VNC server is listening for connections. Also double-check that a firewall is not preventing the connection.}}
 ==== Connecting with VNC ====
@@ Line 73: / Line 66: @@
 === Allowing Another Computer to Connect Using Desktop Sharing ===
-If you wish another user to connect to your computer and have the KDE desktop installed, you can use the KDE Desktop Sharing application to generate a connection invitation. To launch this application within KDE, go to ''Applications'' ➜ ''Internet'' ➜ ''Desktop Sharing'' or type '''krfb''' from the command prompt of any desktop. If you press F1 while in this application, it will open the Desktop Sharing Handbook where you can learn more about using this utility. Figure 9.7c shows the initial screen for this application:
+If you wish another user to connect to your computer and have the KDE desktop installed, you can use the KDE Desktop Sharing application to generate a connection invitation. To launch this application within KDE, go to ''Applications'' ➜ ''Internet'' ➜ ''Desktop Sharing'' or type '''krfb''' from the command prompt of any desktop. If you press F1 while in this application, it will open the Desktop Sharing Handbook where you can learn more about using this utility. Figure 9.7c shows the initial screen for this application.
-−
-'''Figure 9.7c: Initiating a Connection Request Using krfb'''
-−
-[[Image:Krfb1a.png]]
 There are two types of invitations that you can create:
-'''Personal Invitation:''' if you click this button it will display the hostname that the other person will use to connect, a temporary password to use for the connection, and a connection request expiration time of one hour. It will include a warning reminding you to only give this information to the person you wish to connect as anyone can connect using that information. The connection itself can be made from any VNC client. If the person is using PC-BSD®, they can use '''kdrc''' or '''vncviewer''' as described above. On other operating systems, they will need to check if VNC is installed and download a VNC client if it is not. Once you press the "Close" button, the invitation expiry date will be listed in the main screen.
+'''Personal Invitation:''' if you click this button it will display the hostname that the other person will use to connect, a temporary password to use for the connection, and a connection request expiration time of one hour. It will include a warning reminding you to only give this information to the person you wish to connect as anyone can connect using that information. The connection itself can be made from any VNC client. If the person is using PC-BSD®, they can use '''kdrc''' or '''vncviewer''' as described above. On other operating systems, they will need to check if VNC is installed and download a VNC client if it is not. Once you press the "Close" button, the invitation expiry date will be listed in the main screen. Figure 9.7d shows an example of a personal invitation.
-−
-'''Email Invitation:''' if you click this button it will display a warning that anyone who reads the email containing the invitation can connect. Once you click the "Continue" button, the default email program will open the invitation so that you can input the email address of the recipient and send the email.
-−
-It should be noted that the most secure way to convey the invitation information is through an alternate communications channel such as a phone call. Ideally, you are speaking to the other person as they connect so that you can walk them through the problem you are experiencing and they can let you know what they are doing to your system as you watch them do it.
-−
-Figure 9.7d shows an example of a personal invitation:
-−
-'''Figure 9.7d: Connection Invitation Created Using krfb'''
-−
-[[Image:Krfb1.png]]
-Once the other person has the invitation, they should input the information in the invitation into their VNC client in order to start the connection. You will know when they try to connect as a pop-up message will appear on your screen similar to Figure 9.7e:
+'''Email Invitation:''' if you click this button it will display a warning that anyone who reads the email containing the invitation can connect. Once you click the "Continue" button, the default email program will open the invitation so that you can input the email address of the recipient and send the email.[[File:Krfb2.png|thumb|393px|'''Figure 9.7e: The Other User is Trying to Connect Using the Invitation''']]
-'''Figure 9.7e: The Other User is Trying to Connect Using the Invitation'''
+It should be noted that the most secure way to convey the invitation information is through an alternate communications channel such as a phone call. Ideally, you are speaking to the other person as they connect so that you can walk them through the problem you are experiencing and they can let you know what they are doing to your system as you watch them do it.
-[[Image:Krfb2.png]]
+Once the other person has the invitation, they should input the information in the invitation into their VNC client in order to start the connection. You will know when they try to connect as a pop-up message will appear on your screen similar to Figure 9.7e.
 In this example, a computer with an IP address of 192.168.1.111 is trying to connect. Buttons are provided to either accept or refuse the connection. You can also check or uncheck the box to "allow remote user to control keyboard and mouse". If you accept the connection, the other user will be prompted to input the invitation password. Once the password is accepted, they will see your desktop.
 <noinclude>
 [[category:handbook]]
 [[category:Common Tasks]]
 [[category:Remote Desktop]]
 </noinclude>

@@ Line 1: / Line 1: @@
 <noinclude>{{NavHeader|back=Windows Emulation|forward=Thin Client}}</noinclude>
 Occasionally it is useful to allow connections between desktop sessions running on different computers. This can be handy when troubleshooting a problem since both users will be able to see the error on the problematic system and either user can take control of the mouse and keyboard in order to fix the problem. Typically this is a temporary situation as providing access to one's computer allows a remote user the ability to both view and modify its settings.
@@ Line 6: / Line 7: @@
 === Connecting to Another Computer With RDP ===
-The {{citelink|wp|url=Remote_Desktop_Protocol|remote desktop protocol (RDP)}} can be used to make a connection to another computer. This section will demonstrate what is needed on the remote computer for an RDP connection, how to connect using KDE's KRDC, and how to connect using VNC.
+The {{citelink|wp|url=Remote_Desktop_Protocol|txt=remote desktop protocol (RDP)}} can be used to make a connection to another computer. This section will demonstrate what is needed on the remote computer for an RDP connection, how to connect using KDE's KRDC, and how to connect using VNC.
 ==== Preparing the Remote System ====
@@ Line 12: / Line 13: @@
 Depending upon the operating system, you may have to first install or enable RDP software on the remote computer:
-* not every edition of Windows provides a fully functional version of RDP; for example, it may not be fully supported in a Home Edition of Windows. Even if the full version of RDP is included, remote access may or may not be enabled by default. If you have trouble connecting using RDP, do a web search for "remote desktop" and the name of the version of Windows you are using to find out how to configure its remote desktop settings. If you still cannot connect, you will need to download, install and configure {{citelink|wp|url=Virtual_Network_Computing|VNC}} server software on the system.
+* not every edition of Windows provides a fully functional version of RDP; for example, it may not be fully supported in a Home Edition of Windows. Even if the full version of RDP is included, remote access may or may not be enabled by default. If you have trouble connecting using RDP, do a web search for "remote desktop" and the name of the version of Windows you are using to find out how to configure its remote desktop settings. If you still cannot connect, you will need to download, install and configure {{citelink|wp|url=Virtual_Network_Computing|txt=VNC}} server software on the system.
-* if the other computer you are connecting to is a Mac, Linux, or BSD system, you will have to first install either {{citelink|url=http://www.xrdp.org/|xrdp}} or a VNC server on the other system. Depending upon the operating system, either software may or may not already be installed. If it is not, check the software repository for the operating system or use a web search to find out how to install and configure one of these applications on that operating system. If you are connecting to another PC-BSD® system, the '''krfb''' VNC server is automatically installed with KDE and additional VNC server software is available in AppCafe®.
+* if the other computer you are connecting to is a Mac, Linux, or BSD system, you will have to first install either {{citelink|url=http://www.xrdp.org/|txt=xrdp}} or a VNC server on the other system. Depending upon the operating system, either software may or may not already be installed. If it is not, check the software repository for the operating system or use a web search to find out how to install and configure one of these applications on that operating system. If you are connecting to another PC-BSD® system, the '''krfb''' VNC server is automatically installed with KDE and additional VNC server software is available in AppCafe®.
 If the remote system is protected by a firewall, you will need to check that it allows connections to the TCP port required by the type of connection that you will be using:
@@ Line 52: / Line 53: @@
 '''Console login:''' if you are connecting to a Unix-like system, you can check this box if you wish to have access to the other system's command line console.
-'''Extra options:''' allows you to specify {{citelink|url=http://linux.die.net/man/1/rdesktop|rdesktop switches}} that are not covered by the other options in this screen.
+'''Extra options:''' allows you to specify {{citelink|url=http://linux.die.net/man/1/rdesktop|txt=rdesktop switches}} that are not covered by the other options in this screen.
 '''Show this dialog again for this host:''' if you plan on using the same settings every time you connect to this computer, you can uncheck this box. If you need to change the settings at a later time, you can right-click the connection (which will appear in a list as a past connection) and choose Settings from the right-click menu.
-'''Remember password:''' {{citelink|url=http://docs.kde.org/development/en/kdeutils/kwallet/|KWallet}} is KDE's password storage system. If this box stays checked, you will only need to input the password the first time you make this connection as it will be saved for you. If this is the first time you have stored a password using KWallet, it will prompt you for some information to set up your wallet.
+'''Remember password:''' {{citelink|url=http://docs.kde.org/development/en/kdeutils/kwallet/|txt=KWallet}} is KDE's password storage system. If this box stays checked, you will only need to input the password the first time you make this connection as it will be saved for you. If this is the first time you have stored a password using KWallet, it will prompt you for some information to set up your wallet.
 If it is a VNC connection, you will be able to choose your connection type (speed), screen resolution, and have the option to remember the password.
-Once you press OK, the connection should be initiated and you will receive pop-up messages asking for a username then a password; the details you provide must match a user account on the system you are connecting to. Once your authentication details are confirmed, you should see the desktop of the other system. If you move your mouse, it will move on the other desktop as well. Click the "View Only" button in the top toolbar whenever you wish to disable this mouse behaviour. When you are finished your session, you can click the "Disconnect" button in the top toolbar.
+Once you press OK, the connection should be initiated and you will receive pop-up messages asking for a username then a password; the details you provide must match a user account on the system you are connecting to. Once your authentication details are confirmed, you should see the desktop of the other system. If you move your mouse, it will move on the other desktop as well. Click the button ''View Only'' in the top toolbar whenever you wish to disable this mouse behaviour. When you are finished your session, you can click the button ''Disconnect'' in the top toolbar.
 '''NOTE:''' if the connection fails, check on the remote computer that either the RDP software is enabled or that the VNC server is listening for connections. Also double-check that a firewall is not preventing the connection.