![]() (Click any image in this story to enlarge it.) You can give your computer any name you want, so long as you'll recognize it. Then, go back to your original tab, and you'll find a prompt waiting for you to name your computer and move forward. Click the blue "Add to Chrome" button on the page that appears and confirm that you want to proceed. You'll then be prompted to download the Chrome Remote Desktop extension. Within Chrome, navigate to Google's Chrome Remote Desktop web app and click the circular blue arrow icon inside the box labeled "Set up remote access." (If you see a blue button labeled "Turn On" instead of a blue arrow, congratulations: You're one step ahead! Skip the next paragraph, and you'll be back on track.) If you want to be able to access your own computer from another desktop or mobile device, start by opening up Chrome on the host computer (or downloading and installing Chrome, if you're using a Windows, Mac, or Linux system that somehow doesn't already have it). In that scenario, it's up to the IT department to decide.) Using Chrome Remote Desktop to access your own computer Step 1: Prepare the computer for connections (Note that Chrome Remote Desktop might not work with company-managed, enterprise-level Google accounts. In fact, all you need to do is decide what type of connection you want and then complete a couple quick steps, and you'll be remotely connecting like nobody's business. address [0.0.And best of all? Getting the service up and running is easy as can be. Socket 12: AF_INET6 connection received from ::ffff:59.78.0.91 port 11867 Socket 12: AF_INET6 connection received from ::ffff:59.78.0.91 port 11866 TLS connection established from ::ffff: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 Socket 12: AF_INET6 connection received from ::ffff:59.78.0.91 port 7586 Socket 12: AF_INET6 connection received from ::ffff:59.78.0.91 port 7585 xrdp_mm_connect_chansrv: chansrv connect successful xrdp_wm_log_msg: login successful for display 10 xrdp_wm_log_msg: login failed for display 0 xrdp_wm_log_msg: sending login info to session manager, please wait. xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350 local keymap file for 0x00000804 found and doesn't match built in keymap, using local keymap file Loading keymap file /etc/xrdp/km-00000409.ini ![]() Cannot find keymap file /etc/xrdp/km-00000804.ini TLS connection established from ::ffff:: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 adding channel item name drdynvc chan_id 1007 flags 0xc0800000 ![]() adding channel item name cliprdr chan_id 1006 flags 0xc0a00000 adding channel item name rdpsnd chan_id 1005 flags 0xc0000000 ![]() adding channel item name rdpdr chan_id 1004 flags 0x80800000 connected client computer name: HUSKY-K610C Security layer: requested 11, selected 1 Using default X.509 key file: /etc/xrdp/key.pem Using default X.509 certificate: /etc/xrdp/cert.pem Closed socket 11 (AF_INET6 :: port 3389) The Ubuntu system is installed on a laptop, and the keyboard and mouse are normal. ![]() I was trying to control Ubuntu 20.04 remotely via windows 10.Īfter logging in on windows, the screen was refreshing but the mouse and keyboard did not respond. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |