Skip to content

Commit 7394742

Browse files
committed
spacing
1 parent 7c06695 commit 7394742

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

windows-365/enterprise/connection-errors.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,7 @@ The following errors can occur when connecting to a Cloud PC.
3737
### We couldn't connect because there are currently no available resources
3838

3939
**Potential cause**: The Cloud PC hasn’t completed provisioning.
40+
4041
**Possible solution**: Wait for provisioning to complete. Provisioning time can be variable and may exceed 45 minutes or more.
4142

4243
### We couldn't connect to the gateway because of an error. If this keeps happening, ask your admin or tech support for help.
@@ -45,15 +46,16 @@ The following errors can occur when connecting to a Cloud PC.
4546

4647
- Custom DNS Settings
4748
- Network Virtual Appliance blocking
48-
- Network Security group configuration
49+
- Network Security group configuration
4950
- Resource Locks
5051
- Blocks on required endpoints
5152

5253
**Possible solution**: Review the settings and confirm that they aren’t interfering with connections.
5354

5455
### The remote PC ended your session. If this keeps happening, contact your network administrator for assistance. Error code: 0x3
5556

56-
**Potential cause**: This error can occur when the Cloud PC’s processor is overutilized.
57+
**Potential cause**: This error can occur when the Cloud PC’s processor is over-utilized.
58+
5759
**Possible solution**: If the issue persists, try restarting the Cloud PC from the admin portal.
5860

5961
## Other connection error causes

0 commit comments

Comments
 (0)