![]() ![]() 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. 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 TCP 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 for 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 connection over TCP port 4172. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |