This is just an attempt to work out why the client behaved differently for different people.
We have just had a problem with our esx4i infrastructure. One effect of this was that anybody who was connected to the infrastructure by their vsphere client was able to maintain the connection / reconnect after the problem was solved. Those who tried to connect during the problem got the error "unable to read data from transport connection: the connection was closed". Those who tried to connect only after the problem was solved were able to connect. However, those that opened their client during the problem period, and kept their client open, were not able to connect even after things were fixed and still got the same error mesage as above.
But, if they closed the client and re-opened it, they were able to connect.
So, my question is, is this the way that the client works? Does it use the same connection for repeated attempts, hence it didn't work for those that opened it during the problem period? And is it fully understandable that things worked after the client was re-started?
A small issue, but that's the way that you get to know how these work.
Many thanks
Ian.