Book
- Basic setup of a SOHO server
- SoHo - Software repositories
- SoHo - Alias of loopback interface
- SoHo - IPtables configuration example
- SoHo - Webmin
- SoHo - DNS
- SoHo - VMWare
- SoHo - Windows
- SoHo - OpenVPN
- SoHo - Remote Desktop
- Nameserver on Windows XP forwarding to public DNS with private zones
- SoHO - NTP
- SoHo - SSH
- SoHo - Ubuntu prerequisites
- How to strengthen SSH
- Fixing Nessus complaints
- Java installation on RHEL 4
- Installing vsFTPd on CentOS
- How to setup CA (certificate authority)
- Installation of VIM X11 and archivers on RHEL 4 x86_64
- SoHo - MS & Open-Office
- User management
- CommuniGate Pro
- Backup
- Issue tracking for small groups
- Jabber setup and configuration
- Monitoring & Statistics
- Printing in SOHO
- Faxes in SOHO
- T38 Modem
- PostScript fonts for faxes
- Installing Brother MFU drivers on Ubuntu
- Installing Hylafax client on RHEL4 and Fedora
- Installing Hylafax server on RHEL4
- Installing Hylafax server on Ubuntu
- Integrating Hylafax with CUPS
- Integrating Hylafax with CommuniGate
- Managing Hylafax from Ubuntu client
- Sending and receiving faxes over internet (links)
- How to test faxing
- Drivers for Brother MFUs
- Brand new idea about faxing
- External faxing resources
- Antivirus & Antispam
- External SOHO References
- Supplementary SOHO procedures
Remote Desktop Protocol (RDP) in SoHo
1. RDP information
Versions:
2. RDP and keyboard layout
The default keyboard layout changes when you use Remote Desktop (MS knowledge base article). I use rdesktop FC8 to connect to Windows 2003 English edition, FC8 is configured for russian locale, Windows has both russian and english layouts with english as default. When I connect, the default layout becomes russian, and some layout glitches appear, e.g. I cannot type slash. I helped this by changing keyboard map in tsclient rdesktop configuration to en.
3. RDP and sound
Current RDP 5.0 does not support audio streaming.It will be supported starting from RDP 5.1 which is planned for Windows XP server.However, Citrix supports sound streaming completely.
4. RDP and remote login
Problem: trying to login as a normal user, you see the message:
- Чтобы выполнить вход на этот удаленный компьютер, нужно иметь разрешение на вход в систему через службу терминалов. По умолчанию, слен группы пользователи удаленного рабочего стола имеют такое разрешение. Если Вы не являетесь членом группы пользователи удаленного рабочего стола или другой группы, имеющей такое разрешение, или если группа пользователей удаленного рабочего стола не имеет такое разрешение, нужно добавить это разрешение вручную.
Solution:
- Add users to the group Remote desktop users.
- Add the group Users of the remote desktop to the Computer Configuration - Windows Settings - Security Settings - Local Policies - User rights Assignment, policy "Allow log on through Terminal Services" (it is done by defaul already, but in the domain controller it is enabled only to administrators).
- Add the group Remote Desktop Users into the list of accepted groups for the connection rdp-tcp (by default it is done already)
Even simpler: add the group Domain Users in the accepted list of RDP-TCP
On the Windows server in the Windows Firewall settings enable the use of Remote desktop control for the network VPN Connection.
Related Links
- FAQ for RDP on Windows XP
- RDP :: forum.ru-board.com
- RDP :: microsoft technet: logon rights
- RDP :: support.microsoft.com
- RDP :: technet.microsoft: allow log on locally
- RDP :: terminal services: logon problems
- RDP :: user can rdc to a dc but admins
- ThinStuff - advanced RDP server
- Thinstuff RDP server for RHEL4
- XRDP

- Visit FAQ for RDP on Windows XP
- Visit RDP :: forum.ru-board.com
- Visit RDP :: microsoft technet: logon rights
- Visit RDP :: support.microsoft.com
- Visit RDP :: technet.microsoft: allow log on locally
- Visit RDP :: terminal services: logon problems
- Visit RDP :: user can rdc to a dc but admins
- Visit ThinStuff - advanced RDP server
- Visit Thinstuff RDP server for RHEL4
- Visit XRDP

Comments
Post new comment