Hi
I am having difficulties connecting with PowerCLI 10.0 through firewalls to a vCSA 6 with External PSC.
I have requested TCP 443 be allowed through to the vCSA and I can see in the FW logs the traffic is getting through.
However when I try
Connect-VIServer -Server vCSA.domain.com
I get back this error
Connect-VIServer : There was no endpoint listening at https://PSC.domain.com/lookupservice/sdk that could accept the message.
I have another server with firewall rules allowing access using PowerCLI 6.3 which can connect without error.
Should TCP 443 to the vCSA be sufficient for PowerCLI connections? Or do I need to be able to reach the PSC?
Has anything changed in PowerCLI that would be causing this?
Thanks
Mark
Yes, it's a bug that popped up with PowerCLI 10.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
This looks an awful lot like the bug described in vcsim: unable to connect when using PowerCLI 10 GA
Can you do the stack trace like Atanas asked in that thread?
Does it also happen with the latest PowerCLI 10.1.0 (which was released yesterday)?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
I don't have a firewall in place, but did some testing and can confirm that powerCLI is establishing a connection to an external PSC in addition to the VCS. Observed the behavior with 10 and 10.1.0 during authentication.
Assuming this is a bug, and not by design, may want to put the firewall rule in to allow https to the PSC as a fix.
Downgraded to PowerCLI 6.5.1 build 5377412 and it works!
Yes, it's a bug that popped up with PowerCLI 10.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Is there an ETA on when this bug will be fixed? I noticed that it's present on PowerCLI 10.2.0.9372002 as well.
Thanks.