VMware Cloud Community
markmcgilly
Enthusiast
Enthusiast
Jump to solution

Connect-VIServer through firewall to vCSA 6.0 with External PSC

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

1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

Yes, it's a bug that popped up with PowerCLI 10.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

0 Kudos
6 Replies
LucD
Leadership
Leadership
Jump to solution

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

kwhornlcs
Enthusiast
Enthusiast
Jump to solution

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.

2018-04-27 09_10_02-TCPView.png

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.

markmcgilly
Enthusiast
Enthusiast
Jump to solution

I've updated to 10.1 and get the same error about the lookupservice

Full output including stack trace is in the attached.

0 Kudos
markmcgilly
Enthusiast
Enthusiast
Jump to solution

Downgraded to PowerCLI 6.5.1 build 5377412 and it works!

0 Kudos
LucD
Leadership
Leadership
Jump to solution

Yes, it's a bug that popped up with PowerCLI 10.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
andrew_perfectm
Contributor
Contributor
Jump to solution

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.

0 Kudos