I have seen the same issue myself. It's a timing issue related to the
'reserved' state. During this state, the vcld process loops until it
detects a value in reservation.remoteIP which gets set when the user
clicks 'Connect'. There is a 5 second wait in between attempts. This
could be reduced but the downside would be a little more processing on
the management node.
Once it detects the remote IP has been set, it can take 3-9 seconds for
the firewall-opening commands to be executed.
Quickly looking at the code, I think some improvements can be made to
reduce the lag time. I created an issue for this:
On 4/1/2011 2:58 PM, Hartl, Gerhard L. wrote:
(disregard previous, forgot to retitle)
Since upgrading to 2.2, when a user browses to the 'connect' page, I've noticed that the
clients ip is captured and the management node then ssh's to the vm and opens up the port
for the clients ip on 3389. While I understand this is best practice, I have noticed
that if they user is to quick clicking through the page that they sometimes have to click
the "Get RDP File" twice since the first time tries to connect prior to the
port being opened up. Is there any way around this?
- Gerhard Hartl
Old Dominion University