I can't connect directly to an ESX host using PowerCLI 4.1.1
C:\Program Files\VMware\Infrastructure\vSphere PowerCLI> Connect-VIServer esx001
Connect-VIServer : 12/2/2010 12:04:38 PM Connect-VIServer Could not connect using the requested protocol.
At line:1 char:17
+ Connect-VIServer <<<< esx001
+ CategoryInfo : ObjectNotFound: ( , ViServerConnectionException
+ FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_ProtocolError,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServer
Connecting to vCenter works without problems.
I also tried specifying the -protocol and -port parameters, but without success.
I am using .net 3.5 SP1 and PowerShell 2.0
Anyone else experiencing the same problems?
-
Arnim van Lieshout
Blogging: http://www.van-lieshout.com
Twitter: http://www.twitter.com/avlieshout
If you find this information useful, please award points for "correct" or "helpful".
Hi Arnim,
Could you please check your ProxyPolicy settings (Get-PowerCLIConfiguration)? You can set the proxy policy to "NoProxy" and try connecting again. I guess this might be the cause of the problem.
Regards,
Dimitar
-
PowerCLI development team
Hi Arnim,
I have no problem connecting a ESX 3.5 server from PowerCLI 4.1 U1. At the moment I do not have a vSphere ESX server to test with.
I must say however that I get a warning message when I connect the ESX server. The warning states in Dutch:
WARNING: De index ligt buiten de matrixgrenzen.
Which translates to English in:
WARNING: The index is outside the array bounds.
I don't know why I get that warning and how to prevent it.
Regards, Robert
Thank you Robert,
I also tried ESX3.5 without success.
I'm installing powershell and powercli on another test server right now.
When I connect to vCenter server I also get the index error.
Maybe has something to do with updating the $global:DefaultVIServers array. Looks like a bug to me.
Arnim
-
Arnim van Lieshout
Blogging: http://www.van-lieshout.com
Twitter: http://www.twitter.com/avlieshout
If you find this information useful, please award points for "correct" or "helpful".
No problem connecting to ESX 4.1 and ESXi 4.1.
____________
Blog: LucD notes
Twitter: lucd22
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Upgraded to PowerCLI 4.1.1 on another testserver.
Same problem!
I'm flabbergasted right now.
-
Arnim van Lieshout
Blogging: http://www.van-lieshout.com
Twitter: http://www.twitter.com/avlieshout
If you find this information useful, please award points for "correct" or "helpful".
Hi Arnim,
Could you please check your ProxyPolicy settings (Get-PowerCLIConfiguration)? You can set the proxy policy to "NoProxy" and try connecting again. I guess this might be the cause of the problem.
Regards,
Dimitar
-
PowerCLI development team
YES!
Thank You!
-
Arnim van Lieshout
Blogging: http://www.van-lieshout.com
Twitter: http://www.twitter.com/avlieshout
If you find this information useful, please award points for "correct" or "helpful".
Robert,
See http://communities.vmware.com/message/1657742#1657742 for the answer to your problem.
Allen
Cool,
This just solved my problem with a customer where I "quickly" wanted to export all folders and vms placements in those folders and nothing worked
Turned out to be the proxy setting.
http://www.GabesVirtualWorld.com