https://wiki.archlinux.org/api.php?action=feedcontributions&user=Twighk&feedformat=atomArchWiki - User contributions [en]2024-03-29T15:23:48ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Tencent_QQ_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=217207Talk:Tencent QQ (简体中文)2012-08-09T10:54:34Z<p>Twighk: Suggestion for adding aur/libqq-pidgin to the page</p>
<hr />
<div><br />
== aur/pidgin-lwqq-git ==<br />
Currently aur/libqq-pidgin is not working for me as the protocol is being depreciated, however aur/pidgin-lwqq-git seems to work.</div>Twighkhttps://wiki.archlinux.org/index.php?title=Rdesktop&diff=215590Rdesktop2012-07-30T09:51:33Z<p>Twighk: Spelling for -> from</p>
<hr />
<div>[[Category:Remote Desktop Protocol]]<br />
[[http://www.rdesktop.org/ rdesktop]] is a free, open source client for Microsoft's proprietary RDP protocol released under the GNU General Public License. Use rdesktop to connect to Windows 2000/XP/Vista/Win7 RDP server to remotely administrate the Windows box.<br />
<br />
==Features==<br />
As of July 2008, rdesktop implements a large subset of the RDP 5 protocol, including:<br />
<br />
* Bitmap caching<br />
* File system, audio, serial port and printer port redirection<br />
* Mappings for most international keyboards<br />
* Stream compression and encryption<br />
* Automatic authentication<br />
* Smartcard support<br />
* RemoteApp like support called "seamless" mode via SeamlessRDP<br />
<br />
Still unimplemented are:<br />
<br />
* Remote Assistance requests<br />
* USB device redirection<br />
<br />
Support for the additional features available in RDP 5.1 and RDP 6 (including multi-head display spanning and window composition) also have not yet been implemented.<br />
==Installation==<br />
The packages for rdesktop are available in the extra repo; to install simply use pacman as you would any other package<br />
# pacman -S rdesktop<br />
==Usage==<br />
For a complete listing of options see the rdesktop man page. Here is a typical line<br />
$ rdesktop -g 1440x900 -P -z -x l -r sound:off -u windowsuser 98.180.102.33:3389<br />
<br />
Reading form left to right:<br />
<br />
{| border="1"<br />
| -g 1440x900 || Sets the resolution of the display to 1440x900<br />
|- <br />
| -P || Enables bitmap caching/speeds up xfers.<br />
|- <br />
| -z || Enables RDP datastream compression<br />
|-<br />
| -x l || Uses the "lan" quality experience level, see the man page for additional options<br />
|-<br />
| -r sound:off || Redirects sound generated on the server to null<br />
|-<br />
| -u windowsuser || This defines the username to use when logging into the Windows box<br />
|-<br />
| 98.180.102.33:3389 || This is the IP address and port number of the target machine<br />
|}<br />
==remote desktop using netbios names instead of using IP address==<br />
If you don't know the IP address of a windows computer in a network, you have to enable wins support. To do so, you have to install samba. Enabaling wins in samba is surprisingly easy: just edit the /etc/samba/smb.conf and add the following line to it, or uncomment the appropriate line:<br />
<br />
wins support = yes<br />
<br />
then you have to install winbind<br />
and edit the /etc/nsswitch.conf<br />
and add the "wins" to the list of hosts.<br />
<br />
restart smbd and nmbd services and test your success by pinging a windows netbios host.<br />
<br />
== See also ==<br />
*[[xrdp]] a daemon creating an RDP interface to the X server</div>Twighk