![]() The possible solution: Change the SNAT setting on the virtual server. Recommended Actions Make sure the BIG-IP can create the TCP connection to the VMWare server. T12:09:46.735+05:30 INFO (01) : CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetClient: desktop PID is INFO (01) : CdkViewUsb_Log: ViewUsblib log: ViewUsb_GetClient: client handle is 0F2827A0 VMWare Horizon client Cause Network enviroment issue, BIG-IP create the TCP connection from 172.30.100.100.12345 to 172.31.100.100.443, failed. T12:09:46.735+05:30 INFO (01) : Session::OnDisconnected:2019: Remote session (C6CD0AC) disconnected: The connection to the remote computer ended. T12:09:46.733+05:30 WARN (01) : RMKSWindow::OnConnectionStateChanged:2202: (C6CB368) disconnected with error 'The connection to the remote computer ended.'. The server providing the 504 Gateway Timeout Error is acting as a gateway. ![]() T12:09:46.603+05:30 EROR (01) : RMKSWindow::OnMKSPresentChanged:2050: Failed to mount to remote session. Lets take a moment to discuss what a gateway (or proxy) is. (Posting here in case someone is able to identify what is going on here) Search for jobs related to Vmware horizon client http error 504 or hire on the world's largest freelancing marketplace with 22m+ jobs. On the affected machines I tried checking the client logs but couldn't find any references on the error below: I would strongly recommend you to collect the client and connection server logs and upload it to the VMware GSS team with the user name and timestamp. I changed the agent to 2106 and client to 2203 and it started working fine again. When designing APIs, choosing HTTP status codes is not always that obvious and prone. ![]() I have observed similar issues with agent 2111 2203 2206 and client 22. When I try to connect using the Remote Desktop client, it hangs at. ![]()
0 Comments
Leave a Reply. |