Unable to login to Vcenter

[Ngas]

I'm experiencing a weird issue with my Vmware. When I attempt to login to my vcenter cluster via vsphere client, I get incorrect username or password for the local admin and my AD admin account.

I can access single hosts and VM's running off these host (includes the vcenter VM)  using the exact credentials used to access my vcenter server. But everything is managed through my Vcenter cluster - which I can't access.

I also have this problem when trying to access it through web client.

Has anyone come across this issue before

[rcporto]

Which version of vCenter you're running ? Since you told that tried login using the vSpher Web Client I assume that you're using a version 5.1 or later, then have you tried using the administrator@vsphere.local (or admin@system-domain) ?

[ThompsG]

Hi and welcome to the community,

Can you confirm for us the following:

• vCenter build number?
• Windows or vCenter Server appliance?

Kind regards.

[Ngas]

Running 5.1.0.

I've tried using root account and admin AD. They usually work for me.

[Ngas]

build details:

vsphere client ver 5.1.0 Build 2306356

VMware ESXi ver 5.1.0 Build 2323236

[Ngas]

I've also just found that all my backup jobs have failed too because it can't access vcenter cluster due to incorrect username/password.

[Ngas]

here's the msg I get with the web client version

[rcporto]

Try using admin@system-domain user.

[ThompsG]

Hi there,

Can you confirm the vCenter Single Sign-On service on your vCenter server is running - if this is stopped then you will not be able to login.

Kind regards.

[Ngas]

Hi ThompsG

Single sign on service is running.

[Ngas]

Hi Richardson porto

Ok so I can login now using administrator@system domain which is great. For me to login using the original credentials, do I need to re-apply them?

[lathef]

I had a similar case and when I typed the full domain name before the user name I got it through.

abc.co.in\username

all the best.

a.latheef

[hussainbte]

Hi Ngas,

Login with administrator@vsphere.local and verify your identity sources.

Make sure you have a valid domain mentioned as the Identity source and remove the local OS users if any.

Check the below KB.

http://kb.vmware.com/kb/2043070