You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/dev-box/how-to-resolve-dev-box-connectivity-issues.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,26 +24,26 @@ Before you begin troubleshooting, ensure you have:
24
24
25
25
## Steps for troubleshooting
26
26
27
-
Remote Desktop connections are essential for accessing your Dev Box. However, connectivity issues cansometimes arise due to various factors. This guide provides a comprehensive step-by-step approach to troubleshooting common Remote Desktop connection problems, ensuring that your workflow remains uninterrupted.
27
+
Remote Desktop connections are essential for accessing your Dev Box. However, connectivity issues can sometimes arise due to various factors. This guide provides a comprehensive step-by-step approach to troubleshooting common Remote Desktop connection problems, ensuring that your workflow remains uninterrupted.
28
28
29
-
Before proceeding with troubleshooting, ensure that your Remote Desktop app is updated and both your client computer and Dev Box have the latest updates installed.
29
+
Before proceeding with troubleshooting, ensure that your Remote Desktop app is updated and both your client computer, and Dev Box have the latest updates installed.
30
30
31
-
Be aware that any improper network configurations on your Dev Box can disrupt Remote Desktop connections.
31
+
Any improper network configurations on your Dev Box can disrupt Remote Desktop connections.
32
32
33
-
Additionally, if you haven't accessed your Dev Box in the past three months, check if you might have been removed from Azure Active Directory (AAD) due to inactivity. In such cases, contact the Cloud PC Service support team for assistance in regaining access.
33
+
Additionally, if you haven't accessed your Dev Box in the past three months, check if you might have been removed from Microsoft Entra ID due to inactivity. In such cases, contact the Cloud PC Service support team for assistance in regaining access.
34
34
35
35
### Step 0: Preliminary Checks
36
36
-**Internet Connection:** Verify that your local machine has an active internet connection.
37
37
-**Dev Box Status:** Confirm that your Dev Box is running through the Dev Box portal.
38
-
-**Proxy Settings:** Incorrect internet proxy settings can interfere with the Remote Desktop experience, so ensure these are correctly configured.
38
+
-**Proxy Settings:** Incorrect internet proxy settings can interfere with the Remote Desktop experience, so ensure these settings are correctly configured.
39
39
40
40
### Step 1: Windows Update and App Restart
41
-
-**Pending Updates:** If a Windows update is in progress, it may take up to 30 minutes, during which your Dev Box won't connect.
41
+
-**Pending Updates:** If a Windows update is in progress, it might take up to 30 minutes, during which your Dev Box won't connect.
42
42
-**Restart Remote Desktop:** Close all instances of the Remote Desktop app, terminate any 'msrdc.exe' and 'msrdcw.exe' processes via Task Manager, and then reopen the app to attempt reconnection.
43
43
44
-
### Step 2: Addressing App Hang and Authentication Issues
44
+
### Step 2: Address App Hang and Authentication Issues
45
45
-**App Hang:** If the Remote Desktop app hangs, capture a process dump of MSRDC.exe and create a support request. Restart your computer and try connecting again.
46
-
-**Authentication Errors:** If denied sign-in despite correct credentials, check the AAD join status using dsregcmd.exe /status. Resolve any errors with the helpdesk and restart your computer. If authentication errors persist, unsubscribe and resubscribe to your Dev Box pool in the app. Ensure that your client machine connects to the MSFT VPN if using PIN authentication with a Hybrid-AD joined Dev Box.
46
+
-**Authentication Errors:** If denied sign-in despite correct credentials, check the join status using `dsregcmd.exe /status`. Resolve any errors with the helpdesk and restart your computer. If authentication errors persist, unsubscribe and resubscribe to your Dev Box pool in the app. Ensure that your client machine connects to the MSFT VPN if using PIN authentication with a Hybrid-AD joined Dev Box.
47
47
48
48
### Step 3: Browser Client Connection
49
49
-**Browser Access:** Attempt to connect via the browser client by visiting https://DevBox.microsoft.com and selecting "Open in browser".
@@ -70,7 +70,7 @@ If you experience frequent connection drops with the Remote Desktop app despite
70
70
71
71
You can configure this setting through a registry edit, or through Group Policy.
72
72
73
-
**Use TCP instead of UDP - Registry edit:**
73
+
#### Use TCP instead of UDP - Registry edit:
74
74
Close the Remote Desktop app, apply the following registry setting on your client computer, and try reconnecting.
75
75
76
76
```
@@ -85,7 +85,7 @@ You can set the above using this command in an elevated shell:
Alternatively, use Group Policy Editor on your Dev Box to set RDP transport protocols to "Use only TCP".
90
90
91
91
1. Open the Group Policy Editor on your Dev Box.
@@ -94,7 +94,7 @@ Alternatively, use Group Policy Editor on your Dev Box to set RDP transport prot
94
94
4. Set it to **Enabled**.
95
95
5. For **Select Transport Type**, select **Use only TCP**.
96
96
97
-
If the preceeding steps don't resolve your issue, please contact the Dev Box team support by creating an incident [here]. For urgent or widespread issues, raise the priority of the incident or email the Dev Box team directly at [email protected].
97
+
If the preceding steps don't resolve your issue, contact the Dev Box team support by creating an incident [here]. For urgent or widespread issues, raise the priority of the incident or email the Dev Box team directly at [email protected].
98
98
99
99
Include the following details in your incident report:
100
100
@@ -109,7 +109,7 @@ Include the following details in your incident report:
0 commit comments