Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Can't log into vCenter with vSphere Client

Posted on 2013-06-10
6
Medium Priority
?
1,921 Views
Last Modified: 2013-06-15
Hi,

Up untill recently I have been able to use vSphere client to log into vCenter.
Meanwhile, i changed the ip class in my LAN, and therefore, i changed manually the ip for the esxi and the VCenter machine. After this change, i still can log successefully in esxi with VsphereWhen, but when I try to log in VCenter I get the following message:

vSphere Client could not connect to "<SERVERNAME>".
An unknown connection error occured. (The request failed because of
a connection failure. (Unable to connect to the remote server))


I tried troubleshooting the problem:
-restarting the services
-reinstalling the vcenter
-erase virtual machine (Win2k8R2) which hosts the Vcenter, and recreate it from zero; reinstall vcenter as well.

I still have the same error.
I would really apreciate your advices.

Thanks
0
Comment
Question by:braincap
6 Comments
 
LVL 35

Expert Comment

by:Joseph Daly
ID: 39235826
I would suggest taking a look at your ODBC SQL connection that you setup when installed vcenter. If you specified the connection strings using the old IP address this could cause you issues with logging in.
0
 
LVL 35

Expert Comment

by:Joseph Daly
ID: 39235836
Also have you checked your DNS server for older statically mapped addresses pointed to the older IP address.
0
 
LVL 124
ID: 39235868
can you telnet <ip address> 80

repeat for 443 and 902
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
LVL 6

Expert Comment

by:mmahaek
ID: 39236012
Do all your servers (ESXi, vCenter, SQL) have the same gateway and subnet mask?  If you changed IP config, if the settings are not matching, it could affect your ability to connect to the management services.
0
 

Accepted Solution

by:
braincap earned 0 total points
ID: 39236116
I managed to resolve my problem by editing the vpxa.cfg file.
The new IP add wasn't updated there.

Thanks everyone for answers.
0
 

Author Closing Comment

by:braincap
ID: 39249759
best solution
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
Suggested Courses

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question