I am getting no errors at all in vCenter via either client. The user/password combo works fine. Bypassing the netscaler is not trivial. I'd have to reconfigure the vCenter server to point to a new PSC. More a political issue than technical. The netscaler is configured for passthrough and it was working fine up until i updated to the latest powercli version.
I understand (on the Netscaler).
Perhaps a network trace on the station where you launch the Connect-VIServer cmdlet might shed some light?
Connect from a HTML5 Client and do a Connect-VIServer.
Any obvious differences in what the VCSA returns?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
Sorry, I don't understand what you mean by "Connect from a HTML5 Client and do a Connect-VIServer". Can you explain? I am connecting from the PowerShell ISE. I am unaware of how to run the commandlet through HTML 5. Thank you.
I just mean connect to the vCenter with the Web Client or the HTML5 Client (the web interfaces).
You also need to authenticate for those, just as with Connect-VIServer.Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
I had my networking team take a look at the trace, this is what they see:
I opened the trace in a different software we have that sometimes gives a little more insight and I just saw the same thing. The client is sending the RST flag to tear down the connection. I looked into that packets and do not see anything that indicates why it would terminate the session.
He's referring to the PowerCLI trace.
Have a look at this thread PowerCLI 6.5.1 connect-viserver returns nothing
There the problem turned out to be a TLS issue.Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
Unfortunately not working for me. I tried forcing ssl3 through tls 1.2. with the following:
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
All protocols are enabled on my machine. I'll head down the protocol/security stack path and see what I find.