avlieshout
VMware Employee
VMware Employee

Unable to connect to ESX server using PowerCLI 4.1.1

Jump to solution

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: (Smiley Happy , 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".

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".
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal

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

View solution in original post

0 Kudos
8 Replies
RvdNieuwendijk
Leadership
Leadership

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

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
avlieshout
VMware Employee
VMware Employee

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".

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".
0 Kudos
LucD
Leadership
Leadership

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

avlieshout
VMware Employee
VMware Employee

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".

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".
0 Kudos
admin
Immortal
Immortal

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

View solution in original post

0 Kudos
avlieshout
VMware Employee
VMware Employee

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".

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".
0 Kudos
allencrawford
Enthusiast
Enthusiast

Robert,

See http://communities.vmware.com/message/1657742#1657742 for the answer to your problem.

Allen

0 Kudos
Gabrie1
Commander
Commander

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 Smiley Sad

Turned out to be the proxy setting.






http://www.GabesVirtualWorld.com

http://www.GabesVirtualWorld.com
0 Kudos