Skip to content

Commit 960701f

Browse files
author
modularity
committed
acrolinx edits
1 parent 2e6421c commit 960701f

File tree

1 file changed

+32
-32
lines changed

1 file changed

+32
-32
lines changed

articles/lab-services/troubleshoot-connect-lab-vm.md

Lines changed: 32 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -35,27 +35,27 @@ This article provides guidance on how to troubleshoot common connectivity issues
3535

3636
- Quantify the RDP connection speed
3737

38-
The utility PsPing can be used to measure the response time to the machine. Steps are included in the blog [How to ensure the best RDP experience for lab users](https://techcommunity.microsoft.com/t5/azure-lab-services-blog/how-to-ensure-the-best-rdp-experience-for-lab-users/ba-p/2813369).
38+
The utility PsPing can be used to measure the response time to the machine. Steps are included in the blog [How to ensure the best RDP experience for lab users](https://techcommunity.microsoft.com/t5/azure-lab-services-blog/how-to-ensure-the-best-rdp-experience-for-lab-users/ba-p/2813369)
3939

4040
- Determine the scope of the problem:
4141

42-
- Is it a specific machine?
43-
- Is there a VPN being used?
44-
- Is it slow on a specific network?
45-
- Is there a firewall on the network?
46-
- Is it slow with a specific ISP?
42+
- Is it a specific machine
43+
- Is there a VPN being used
44+
- Is it slow on a specific network
45+
- Is there a firewall on the network
46+
- Is it slow with a specific ISP
4747

4848
##### Specific machine
4949
Adjust the [settings in the client experience](/windows-server/administration/performance-tuning/role/remote-desktop/session-hosts#client-experience-settings) to reduce the volume of data being transmitted.
5050

5151
##### Use of VPN
52-
A good troubleshooting step is to turn off the VPN to see if that improves the connection speed. If it's the VPN and it's required, then review the VPN settings and configuration to possibly allow RDP or SSH connections to be passed through connections aren’t routed to distant regions or routed incorrectly.
52+
A good troubleshooting step is to turn off the VPN to see if that improves the connection speed. If it's the VPN and it's required, then review the VPN settings and configuration to possibly allow RDP or SSH connections to be 'passed through' connections aren’t routed to distant regions or routed incorrectly.
5353

5454
##### Specific network or firewall
5555
A network can affect the connectivity to Azure Lab Services, from an enterprise level network to a student's home router/Wi-Fi combination. For example, a students’ home router might have built-in firewalls that block or limit the RDP/SSH connections. Check if there's a firewall enabled on the network and if it's configured to limit the RDP/SSH connections.
5656

5757
##### Specific internet service provider (ISP)
58-
It isn't common to have multiple ISPs to connect to. If the slowdown is on a specific network and other options were explored, then you may want to contact your ISP to see if they have any limiters on RDP/SSH connections.
58+
It isn't common to have multiple ISPs to connect to. If the slowdown is on a specific network and other options were explored, then you might want to contact your ISP to see if they have any limiters on RDP/SSH connections.
5959

6060
## Virtual Machine not running
6161

@@ -68,30 +68,30 @@ It isn't common to have multiple ISPs to connect to. If the slowdown is on a spe
6868
#### Causes
6969

7070
- The virtual machine that the students are trying to connect to isn't running
71-
- The lab VM may still be starting
72-
- Idle settings can impact lab VM connections
71+
- The lab VM might still be starting
72+
- Idle settings can affect lab VM connections
7373

7474
#### Resolution
7575

7676
Open the [Lab portal](https://labs.azure.com) and check that the virtual machine shows as running. If it's not running, the student can start the virtual machine from their lab portal. It might take between 2 to 5 minutes to get the machine fully running.
7777

78-
Adjusting the [lab automatic shutdown settings](/azure/lab-services/how-to-enable-shutdown-disconnect) may improve the student connection experience. Since turning on and off the virtual machine takes time, adjusting the settings may decrease the chances of the student trying to connect while the machine is changing state. The automatic shutdown settings are part of a cost savings strategy, though they may need to be adjusted to improve the student experience.
78+
Adjusting the [lab automatic shutdown settings](/azure/lab-services/how-to-enable-shutdown-disconnect) might improve the student connection experience. Since turning on and off the virtual machine takes time, adjusting the settings can decrease the chances of the student trying to connect while the machine is changing state. The automatic shutdown settings are part of a cost savings strategy, though they might need to be adjusted to improve the student experience.
7979

80-
- Shut down idle virtual machines: If the duration is too short, there may not be enough time from when the student starts the machine and then connects, or if the student is not active (in-classroom learning for example), the virtual machine may be shutdown.
80+
- Shut down idle virtual machines: If the duration is too short, there might not be enough time from when the student starts the machine and then connects, or if the student isn't active (in-classroom learning for example), the virtual machine might be shut down.
8181
- Shut down virtual machines when users disconnect: If there's too small a time delay, you can run into issues where an accidental disconnect starts a shutdown. Students would need to start the virtual machine again to connect.
82-
- Shut down virtual machines when users don't connect: If students don't connect to the virtual machine after some time and if the duration is too short, the virtual machine will be shutdown. The timing can affect students starting the virtual machine themselves, or if schedules are used in the lab. Changing the idle setting to a longer duration is an option but has potential cost implications. If schedules are being used, the virtual machines can be started closer to when the class time starts.
82+
- Shutdown virtual machines when users don't connect: If students don't connect to the virtual machine after some time and if the duration is too short, the virtual machine will be shutdown. The timing can affect students starting the virtual machine themselves, or if schedules are used in the lab. Changing the idle setting to a longer duration is an option but has potential cost implications. If schedules are being used, the virtual machines can be started closer to when the class time starts.
8383

8484

8585
## Outbound network restriction
8686

8787
#### Symptoms
8888

89-
- The network can be a point of interference when firewall(s), switches, routers or other network appliances block or limit RDP/SSH (3389/22) ports
89+
- The network can be a point of interference when firewalls, switches, routers, or other network appliances block or limit RDP/SSH (3389/22) ports
9090

9191
#### Causes
9292

9393
- Local firewall from a school, university, enterprise, or home network restricting outbound RDP/SSH connections
94-
- Modern routers, especially WIFI 6, have default behavior to block or restrict the RDP/SSH connections
94+
- Modern routers, especially WiFi 6, have default behavior to block or restrict the RDP/SSH connections
9595
- Operating system restricting outbound RDP/SSH connectivity
9696

9797
#### Resolution
@@ -113,7 +113,7 @@ Consider removing the RDP/SSH restriction or add an exemption for the [lab publi
113113

114114
#### Resolution
115115

116-
A lab template can be set up with a [script to autoreset the networking](https://techcommunity.microsoft.com/t5/azure-lab-services-blog/running-a-powershell-shutdown-script-on-windows-lab-services/ba-p/3273163) on machine shutdown. Otherwise, students or teachers would need to [reimage the lab VM](/azure/lab-services/how-to-reset-and-redeploy-vm#reimage-a-lab-vm), which will get them back to a good state.
116+
A lab template can be set up with a [script to autoreset the networking](https://techcommunity.microsoft.com/t5/azure-lab-services-blog/running-a-powershell-shutdown-script-on-windows-lab-services/ba-p/3273163) on machine shutdown. Otherwise, students or teachers would need to [reimage the lab VM](/azure/lab-services/how-to-reset-and-redeploy-vm#reimage-a-lab-vm), which get them back to a good state.
117117

118118
If custom DNS is needed, use [Advanced Networking](/azure/lab-services/how-to-connect-vnet-injection) and specify custom DNS servers on the virtual network.
119119

@@ -135,22 +135,22 @@ If custom DNS is needed, use [Advanced Networking](/azure/lab-services/how-to-co
135135

136136
#### Symptoms
137137

138-
- If the lab has a failure the machine connections may not work properly
138+
- If the lab has a failure the machine connections might not work properly
139139

140140
#### Causes
141141

142142
- The Azure activity log is the most comprehensive list of events and results
143143

144144
#### Resolution
145145

146-
The [activity log](/azure/azure-monitor/essentials/activity-log?tabs=powershell) can be filtered on the resource group that the lab is located in. The events may take a few minutes to be available in the log. These event logs contain more detailed information that can be used for troubleshooting and should be included if a support ticket needs to be created.
146+
The [activity log](/azure/azure-monitor/essentials/activity-log?tabs=powershell) can be filtered on the resource group that the lab is located in. The events can take a few minutes to be available in the log. These event logs contain more detailed information that can be used for troubleshooting and should be included if a support ticket needs to be created.
147147

148148
## Login with username and password
149149

150150
#### Symptoms
151151

152152
- Unable to connect to lab VM with username and password
153-
- Recieve error message 'Your credentials did not work"
153+
- Receive error message 'Your credentials did not work"
154154

155155
#### Causes
156156

@@ -164,34 +164,34 @@ The [activity log](/azure/azure-monitor/essentials/activity-log?tabs=powershell)
164164
##### Student using wrong credentials
165165
Confirm the student is using the correct username and password for their lab VM. If the lab was created with "Use same password for all virtual machines" enabled, then the username and password should be the same for each student.
166166
##### Student forgot their password
167-
If they have a custom password and have forgotten it, then the student can [reset the password on the machine from the lab](/azure/lab-services/how-to-set-virtual-machine-passwords). Additionally, the student can [reimage the machine](/azure/lab-services/how-to-reset-and-redeploy-vm#reimage-a-lab-vm), but any user data are deleted and not be retrievable.
167+
If they have a custom password and forgot it, then the student can [reset the password on the machine from the lab](/azure/lab-services/how-to-set-virtual-machine-passwords). Additionally, the student can [reimage the machine](/azure/lab-services/how-to-reset-and-redeploy-vm#reimage-a-lab-vm), but any user data are deleted and not be retrievable.
168168
##### Password associated with Azure Compute Gallery image
169-
If other students can’t login using the common lab username and password and the lab was created using an existing custom image this may be caused by a known [limitation](/azure/lab-services/troubleshoot-access-lab-vm#unable-to-login-with-the-credentials-you-used-for-creating-the-lab). The workaround is to use the username and password when the image was created or reset the password.
169+
If other students can’t login using the common lab username and password and the lab was created using an existing custom image this can be caused by a known [limitation](/azure/lab-services/troubleshoot-access-lab-vm#unable-to-login-with-the-credentials-you-used-for-creating-the-lab). The workaround is to use the username and password when the image was created or reset the password.
170170
##### Machine was compromised
171-
There are situations where a student password could be fraudulently changed by a bad actor. The student can reset their password to regain access to the machine, but here are some suggestions to reduce the likelihood of this happening:
172-
- Do not use common passwords, uncheck the use same password option when creating the lab. Having individual specific passwords reduces the scope if the password is compromised.
171+
There are situations where a student password is fraudulently changed by a bad actor. The student can reset their password to regain access to the machine, but here are some suggestions to reduce the likelihood of this happening:
172+
- Don't use common passwords and uncheck the use same password option when creating the lab. Having individual specific passwords reduces the scope if the password is compromised
173173
- [Use strong passwords](https://support.microsoft.com/windows/create-and-use-strong-passwords-c5cebb49-8c53-4f5e-2bc4-fe357ca048eb) and secure them
174-
- [Restrict access to the lab](/azure/lab-services/how-to-manage-lab-users?tabs=manual), so that only those students that are in the class can access the machines. By default, the lab is restricted.
175-
##### Remote Desktop Gateway configured
176-
While uncommon, the remote desktop client the students are using may have a Remote Desktop Gateway configured. If so, they would need to enter their gateway credentials first (to authenticate to the gateway) before connecting to their student VM.
174+
- [Restrict access to the lab](/azure/lab-services/how-to-manage-lab-users?tabs=manual), so that only those students that are in the class can access the machines. By default, the lab is restricted
175+
##### Remote Desktop Gateway
176+
While uncommon, the remote desktop client the students are using can have a Remote Desktop Gateway configured. If so, they would need to enter their gateway credentials first (to authenticate to the gateway) before connecting to their student VM.
177177

178178
## Advanced Networking Troubleshooting Items
179-
The list below contains troubleshooting items that only apply to [advanced networking scenarios](/azure/lab-services/concept-lab-services-supported-networking-scenarios).
179+
Some troubleshooting items only apply to [advanced networking scenarios](/azure/lab-services/concept-lab-services-supported-networking-scenarios).
180180

181181
#### Missing a Network Security Group
182-
When troubleshooting a lab plan that has advanced networking configured, one of the first checks is to confirm that the lab services network subnet has a network security group connected to it. This will let the RDP/SSH connections to be allowed through. Without a network security group, all connections are blocked to the virtual machines (template VM and student VMs).
182+
For a lab plan configured with advanced networking, one of the first checks is to confirm that the lab services network subnet has a network security group connected to it. This lets the RDP/SSH connections be allowed through. Without a network security group, all connections are blocked to the virtual machines (template VM and student VMs).
183183

184184
#### Using Azure Virtual Machine RDP Troubleshooting
185-
There are unique troubleshooting techniques with labs that are configured with advanced networking. Advanced networking enables additional troubleshooting by creating an Azure Virtual Machine connected directly to the virtual network that the lab plan is connected to. Using this Azure VM (outside of Azure Lab Services), you can use the Azure Virtual Machine RDP Troubleshooting guide, including the in-Azure connection troubleshooter, to determine if the network is configured correctly.
185+
There are unique troubleshooting techniques with labs that are configured with advanced networking. Advanced networking enables more troubleshooting by creating an Azure Virtual Machine connected directly to the virtual network that the lab plan is connected to. Using this Azure VM (outside of Azure Lab Services), you can use the Azure Virtual Machine RDP Troubleshooting guide, including the in-Azure connection troubleshooter, to determine if the network is configured correctly.
186186

187187
#### NSG Rules are blocking RDP/SSH connections
188-
Using the Azure VM that is connected directly to the virtual network (from the previous section), you can diagnose virtual machine network connectivity directly in the Azure Portal. The blocking or limiting of the RDP/SSH connections via security rules can be done at the subnet with a Network Security Group or by using Azure Virtual Network Manager, the easiest way to see the full list of rules is via the Azure Virtual Machine network effective security rules.
188+
Using the Azure VM that is connected directly to the virtual network (from the previous section), you can diagnose virtual machine network connectivity directly in the Azure portal. The blocking or limiting of the RDP/SSH connections via security rules can be done at the subnet with a Network Security Group or by using Azure Virtual Network Manager. The easiest way to see the full list of rules is via the Azure Virtual Machine network effective security rules.
189189

190190
#### Default User Defined Route (Route table problem)
191-
Advanced networking allows the network to be customized as needed, including modifying the route table. A user-defined route table directs traffic to the appropriate destinations. There is a special route, the “internet route” (0.0.0.0/0) which directs traffic not bound for another local address to the Internet. Azure Lab Services advanced networking does not support updating the ‘next hop’ for the 0.0.0.0/0 route to anything except the internet. Changing this to a specific IP address (for example, directing outbound internet traffic to a firewall or other network appliance) will break connectivity to the lab by introducing an asymmetric routing issue. When debugging issues, check for a custom route table and make sure that the default route is set to have 0.0.0.0/0 to the Internet.
191+
Advanced networking allows the network to be customized as needed, including modifying the route table. A user-defined route table directs traffic to the appropriate destinations. There's a special route, the “internet route” (0.0.0.0/0) which directs traffic not bound for another local address to the Internet. Azure Lab Services advanced networking doesn't support updating the ‘next hop’ for the 0.0.0.0/0 route to anything except the internet. Changing this to a specific IP address (for example, directing outbound internet traffic to a firewall or other network appliance) breaks connectivity to the lab by introducing an asymmetric routing issue. When debugging issues, check for a custom route table and make sure that the default route is set to have 0.0.0.0/0 to the Internet.
192192

193193
## Further troubleshooting
194194

195-
If you're still experiencing issues after following the above steps, you may need to collect more data for further troubleshooting. This could include logs from your virtual machine, network trace data, or other relevant information.
195+
If you're still experiencing issues after following the above steps, you might need to collect more data for further troubleshooting. This could include logs from your virtual machine, network trace data, or other relevant information.
196196

197197
[!INCLUDE [contact Azure support](includes/lab-services-contact-azure-support.md)]

0 commit comments

Comments
 (0)