To resolve the issue, check the status of the WorkSpace on the WorkSpaces console. However, sometimes rebooting the WorkSpace doesn't help. Usually, rebooting the WorkSpace from the WorkSpaces console or the WorkSpaces client resolves the issue. If either of these services aren't running, then the status of the WorkSpace on the WorkSpaces console typically displays Unhealthy.
#AWS WORKSPACES WINDOWS#
These errors typically indicate that the SkyLightWorkSpacesConfigService or the PCoIP Standard Agent for Windows services aren’t responding to health checks. If you need help, contact your administrator. Your WorkSpace is not reachable at the moment. After authentication, the WorkSpaces client displays a "Launching Session" screen, but after a few seconds, the client displays one of the following error messages. Connect to the WorkSpace using an RDP client to verify that the WorkSpace meets the same port requirements. For example, a Windows Firewall rule that's applied locally or through a group policy object (GPO), or an antivirus check might block UDP port 4172 on the management interface. If the network checks are passing on the client, then it indicates a problem with the network configuration on the WorkSpace. If this health check fails, check your local firewall settings. Note: A client-side firewall or proxy might cause a health check failure by preventing access over UDP port 4172. Choose the icon in the top-right corner to see which health checks are failing. Issues on the client side might cause the network check of the client to fail. This might happen when network prerequisites aren’t met.
This error typically indicates that the WorkSpaces client can authenticate over port 443, but can’t establish a streaming connection over UDP port 4172. The client window expands and displays a white screen before displaying a "Disconnected" message. After authentication, the WorkSpaces client displays a "Launching Session" screen. Connect to the WorkSpace using the Remote Desktop Protocol (RDP) client to verify that the WorkSpace meets the same port requirements. For example, a Windows Firewall rule that's applied locally or through a group policy object (GPO), or an antivirus check might block TCP port 4172 on the management interface. If the network checks are passing on the client, then it indicates a problem with the WorkSpace network configuration.
Note: A client-side firewall or proxy might cause a health check failure by preventing access over TCP port 4172. Issues on the client side might cause the network check for the client to fail.
This error typically indicates that the WorkSpaces client can authenticate over port 443, but can’t establish a connection over TCP port 4172. If you need help, contact your administrator." After a few seconds, the following error displays: "Unknown error Occurred. After authentication, the WorkSpaces client is stuck on a WorkSpaces launch screen. The following information describes common errors, the cause of these errors, and troubleshooting guidance to resolve the errors. When the client fails to load the WorkSpace, it's typically because a service or setting is incorrectly configured or unavailable.
The WorkSpaces client depends on special services and network settings.
0 kommentar(er)
