Share via

fix connectivity issue in Microsoft lab environment

williamson sayia 0 Reputation points
2026-03-11T07:34:53.9633333+00:00

i am trying to do one of the applied skills and im having connectivity issues when i access the lab, how do i fix this error?

Community Center | Not monitored
0 comments No comments

2 answers

Sort by: Most helpful
  1. Julian Sharp 21,366 Reputation points
    2026-03-11T11:18:21.5666667+00:00
    0 comments No comments

  2. Q&A Assist
    2026-03-11T07:35:16.4566667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Use the following checks and fixes in order, based on the symptoms seen in the lab.

    1. Confirm the lab VM is actually running
    • Open the Lab portal at https://labs.azure.com.
    • Check that the assigned virtual machine shows as Running.
    • If it is Stopped or Starting, start it from the portal and wait 2–5 minutes before reconnecting.
    1. If the error is “Remote Desktop can’t connect to the remote computer…”
    • This usually means the VM is off or still starting.
    • After confirming the VM is running, try reconnecting from the lab again.
    • If this happens often, the instructor or admin should review the lab’s automatic shutdown/idle settings so VMs are not shutting down too quickly:
      • Increase “shut down idle virtual machines” duration.
      • Increase delay for “shut down when users disconnect.”
      • Increase “shut down when users don’t connect” duration or adjust lab schedules so VMs start closer to class time.
    1. If the issue looks like slow, laggy, or black/blank screen
    • This is often a connectivity/latency problem between the device and the lab host.
    • Check latency and readiness using the Lab Orientation & Connectivity Check: https://labondemand.com/Launch/122B02AA.
    • Typical latency guidance:
      • 100–250 ms = Good
      • 250–500 ms = OK
      • 500 ms = Poor and may feel sluggish or non‑responsive.
    • If using a work-issued device or managed network, try:
      • Using a personal device instead.
      • Using a different network (e.g., home vs. corporate/school Wi‑Fi).
      • Having IT review the lab connectivity requirements and firewall rules.
    1. If the connection fails immediately (RDP/SSH blocked)
    • Some school, enterprise, or home networks and modern Wi‑Fi 6 routers block outbound RDP/SSH (TCP 3389/22).
    • Ask the network admin (or configure the home router/firewall) to:
      • Remove outbound RDP/SSH restrictions, or
      • Add an allow rule for the lab’s public IP address (see how to find the lab public IP in the firewall configuration guidance).
    1. If the lab VM cannot reach external resources via VPN
    • If a VPN is started inside the lab VM and it fails to connect, this can be due to Azure Lab Services network configuration.
    • In that case, open an Azure support request and include:
      • Lab plan ID (from the lab plan Properties in Azure portal).
      • Lab ID (from the lab Properties or the lab URL in labs.azure.com).
      • Approximate time of the issue.
      • Relevant entries from the lab’s Activity log.
    1. If login fails with “Your credentials did not work”
    • Verify the correct username and password for the lab VM.
    • If the lab uses “Use same password for all virtual machines,” ensure those shared credentials are used.
    • If a custom password was forgotten:
      • Use the lab portal option to reset the VM password.
      • As a last resort, reimage the VM (this deletes all user data on that VM).
    • If the lab was created from a custom Azure Compute Gallery image and no student can log in with the common credentials, use either:
      • The username/password used when the image was created, or
      • Reset the password on the VM.
    1. If the issue started after changes inside the VM (admin changes)
    • If network settings were modified in the VM (static IP, DHCP disabled, custom DNS, local group changes), connectivity can break.
    • Fix options:
      • Use a template script that auto-resets networking on shutdown (for future labs), or
      • Reimage the affected lab VM to return it to a known good state.
    1. If none of the above resolves the issue
    • Collect more data (screenshots, error text, approximate time of failure).
    • Ask the lab owner/admin to:
      • Check the lab’s Activity log in Azure Monitor for errors.
      • Create an Azure support request and include:
        • Lab plan ID
        • Lab ID
        • Time of issue
        • Relevant Activity log entries
    • Community help is also available via Azure community support for Azure Lab Services.

    References:


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.