![]() can communicate over the management interface (eth0).If the WorkSpace has been running for some time and you still see this error, verify that the SkyLightWorkSpacesConfigService service: If you just reboot or start your WorkSpace, wait a few minutes, and then try again. This error usually indicates that the SkyLightWorkSpacesConfigService service isn’t responding to health checks. We were unable to connect you to your WorkSpace. Passing the network check often indicates a problem with network configuration on the WorkSpace. ![]() If this health check fails, check your local firewall settings. Note: The most common cause is a client-side firewall or proxy preventing access over port 4172 (TCP and UDP). Issues on the client side often cause the network check in the bottom-right corner of the client to fail.Ĭlick the icon (typically a red triangle with an exclamation point) to see which health checks are failing. This can happen when network prerequisites aren’t met. This error usually indicates that the Amazon WorkSpaces client can authenticate over port 443, but can’t establish a streaming connection over port 4172. After authenticating, the Amazon WorkSpaces client expands and displays a gray “Loading…” screen for a while before returning to the login screen. Today, let us see the common errors and solutions provided by our Support Techs. When the client fails to load the WorkSpace, that failure is usually because one of these prerequisites is incorrectly configured or unavailable. The Amazon WorkSpaces client depends on many special services and network settings. Unable to authenticate to WorkSpace using WorkSpaces client in Amazon? Today, let us see steps followed by our Support Techs to resolve it. Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services. Are you unable to authenticate to WorkSpace using WorkSpaces client in Amazon? We can help you.
0 Comments
Leave a Reply. |