Skip to content

Commit 3abfb45

Browse files
committed
Learn Editor: Update use-remote-desktop.md
1 parent c878bef commit 3abfb45

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/virtual-machines/linux/use-remote-desktop.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,12 @@ The article was written and tested using an Ubuntu 18.04 VM.
2424
This article requires an existing Ubuntu 18.04 LTS or Ubuntu 20.04 LTS VM in Azure. If you need to create a VM, use one of the following methods:
2525

2626
- The [Azure CLI](quick-create-cli.md)
27-
- The [Azure portal](quick-create-portal.md)
27+
- - The [Azure portal](quick-create-portal.md)
2828

2929

3030
## Install a desktop environment on your Linux VM
3131

32-
Most Linux VMs in Azure do not have a desktop environment installed by default. Linux VMs are commonly managed using SSH connections rather than a desktop environment, however there are several desktop environments that you can choose to install. Depending on your choice of desktop environment, it will consume up to 2 GB of disk space and take up to ten minutes to both install and configure all the required packages.
32+
Most Linux VMs in Azure don't have a desktop environment installed by default. Linux VMs are commonly managed using SSH connections rather than a desktop environment, however there are several desktop environments that you can choose to install. Depending on your choice of desktop environment, it consumes up to 2 GB of disk space and take up to ten minutes to both install and configure all the required packages.
3333

3434
The following example installs the lightweight [xfce4](https://www.xfce.org/) desktop environment on an Ubuntu VM. Commands for other distributions vary slightly (use `yum` to install on Red Hat Enterprise Linux and configure appropriate `selinux` rules, or use `zypper` to install on SUSE, for example).
3535

@@ -40,7 +40,7 @@ First, SSH to your VM. The following example connects to the VM named *myvm.west
4040
4141
```
4242

43-
If you are using Windows and need more information on using SSH, see [How to use SSH keys with Windows](ssh-from-windows.md).
43+
If you're using Windows and need more information on using SSH, see [How to use SSH keys with Windows](ssh-from-windows.md).
4444

4545
Next, install xfce using `apt` :
4646

@@ -59,7 +59,8 @@ sudo apt-get -y install xrdp
5959
sudo systemctl enable xrdp
6060
```
6161

62-
On Ubuntu 20, you'll need to give certificate access to an xrdp user:
62+
On Ubuntu 20, you need to give certificate access to an xrdp user:
63+
6364
```bash
6465
sudo adduser xrdp ssl-cert
6566
```
@@ -77,7 +78,7 @@ sudo service xrdp restart
7778
```
7879

7980
## Set a local user account password
80-
If you created a password for your user account when you created your VM, skip this step. If you only use SSH key authentication and do not have a local account password set, specify a password before you use xrdp to log in to your VM. xrdp cannot accept SSH keys for authentication. The following example specifies a password for the user account *azureuser*:
81+
If you created a password for your user account when you created your VM, skip this step. If you only use SSH key authentication and don't have a local account password set, specify a password before you use xrdp to log in to your VM. xrdp can't accept SSH keys for authentication. The following example specifies a password for the user account *azureuser*:
8182

8283
```bash
8384
sudo passwd azureuser
@@ -148,7 +149,7 @@ If your local RDP client uses network level authentication (NLA), you may need t
148149

149150

150151
## Troubleshoot
151-
If you cannot connect to your Linux VM using a Remote Desktop client, use `netstat` on your Linux VM to verify that your VM is listening for RDP connections as follows:
152+
If you can't connect to your Linux VM using a Remote Desktop client, use `netstat` on your Linux VM to verify that your VM is listening for RDP connections as follows:
152153

153154
```bash
154155
sudo netstat -plnt | grep rdp
@@ -161,7 +162,7 @@ tcp 0 0 127.0.0.1:3350 0.0.0.0:* LISTEN 53192/xrdp-sesm
161162
tcp 0 0 0.0.0.0:3389 0.0.0.0:* LISTEN 53188/xrdp
162163
```
163164

164-
If the *xrdp-sesman* service is not listening, on an Ubuntu VM restart the service as follows:
165+
If the *xrdp-sesman* service isn't listening, on an Ubuntu VM restart the service as follows:
165166

166167
```bash
167168
sudo service xrdp restart
@@ -175,8 +176,7 @@ tail -f /var/log/syslog
175176

176177
Other Linux distributions such as Red Hat Enterprise Linux and SUSE may have different ways to restart services and alternate log file locations to review.
177178

178-
If you do not receive any response in your remote desktop client and do not see any events in the system log, this behavior indicates that remote desktop traffic cannot reach the VM. Review your network security group rules to ensure that you have a rule to permit TCP on port 3389. For more information, see [Troubleshoot application connectivity issues](/troubleshoot/azure/virtual-machines/troubleshoot-app-connection).
179-
179+
If you don't receive any response in your remote desktop client and don't see any events in the system log, this behavior indicates that remote desktop traffic can't reach the VM. Review your network security group rules to ensure that you have a rule to permit TCP on port 3389. For more information, see [Troubleshoot application connectivity issues](/troubleshoot/azure/virtual-machines/troubleshoot-app-connection).
180180

181181

182182
## Next steps

0 commit comments

Comments
 (0)