User logging into pool using the View client will not be able to successfully open a VDI session. Related event logs on the view server:
(98C908CC010DC3841BEFF9DD67F826D9) onJMSMessage (RaisePort) Unable to connect to 10.4.35.108:3389, reason: Connection timed out: connect
(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
The desktop shows as ready in the View desktop pool list, but will not respond to RDP. The user will get the same desktop EVERY login attempt and not successfully get a desktop. There are multiple other VDI computers available but the user will not be assigned to a different VDI computer upon successive login attempts. This is not a persistent pool but when a computer fails to respond on RDP it seems the user is tied to it.
Only way I have found to fix this is to delete the VDI computer from the view manager and let it be refreshed. Once the computer is deleted the user can login successfully, as the view manager will then assign them to one of the other computers.
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.
We are facing the same problems. Lots of user can not logged while there are other that still logged.I don't thik it's a network problem because the time response are ok and we have also pc that work with no problems.
If you have find the answer to the problem, I wil be very grateful
thank you very much