connect-viserver not working and get prompted for credentials

This post was originally published on this site

On one machine, I use the connect-viserver ServerName command and that is enough. It connects. On another machine, I get prompted for credentials and then it fails with “The underlying connection was closed: An unexpected error occurred on a receive.”

Does anyone have any idea what I can do to make this work?


machines I’m connecting from that work: Windows Server 2008 R2, Server 2016. That don’t work: Windows Server 2012 R2.

PowerCLI versions: 5.1 and 5.8 – I’ve tried both versions on one of the machines that work and it continues to work and both on the machine that doesn’t work and there’s no difference.

vCenter Server 5.5 U3

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.