![]() Why does the view manager not put the computer in an Error state when it is not responding? Anyone else experience this and has a work around? This is a major product problem, as a failed computer in the pool will keep a user from being able to log into a pool that has several other free computer resources. Once the computer is deleted the user can login successfully, as the view manager will then assign them to one of the other computers. now my problem If I try to connect from the other subnet over the firewall I get a timeout/not respond. When I try to connect with the horizon client in the same subnet (192.168.0.0) it connect to anything perfectly. I recently installed two new monitors and since then I was able to log into my Horizon Client a few times but then after about a week I get disconnected immediately after it authenticates. Only way I have found to fix this is to delete the VDI computer from the view manager and let it be refreshed. the firewall between 192.168.178.0 and 192.168.0.0 is a Software UTM9 where I can monitor traffic etc anything. Horizon Client disconnects after authentication. If they attempt to log back in, they are taken directly back to their desktop. This is odd, because the user will be logged into their desktop working and all of the sudden they are back to the wyse terminal login screen. This is not a persistent pool but when a computer fails to respond on RDP it seems the user is tied to it. I have some users that are getting disconnected from their view session with a message saying their session has timed out. There are multiple other VDI computers available but the user will not be assigned to a different VDI computer upon successive login attempts. The user will get the same desktop EVERY login attempt and not successfully get a desktop. The desktop shows as ready in the View desktop pool list, but will not respond to RDP. (SESSION:06FCC636F79C265D4D1274F9BDA78DCF 98C908CC010DC3841BEFF9DD67F826D9) Failed to launch desktop CN=Stu_Desktop,OU=Applications,DC=vdi,DC=vmware,DC=int for user student1: Error raising port: Unable to connect to 10.4.35.108:3389, reason: Connection timed out: connect User logging into pool using the View client will not be able to successfully open a VDI session.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |