Hello Everyone,
I am working on an issue that I was interested in getting some feedback on.
We have a new installation of vCenter 5.1 that we are working with. However, we are having issues logging in with the vSphere client with domain credentials. Our vCenter server is running as a VM, joined to the domain, and configured on a different subnet. However, when we log into vCenter it says that it has timed out. This is when we are already signed into windows on the vCenter server and are opening the vSphere client from the vCenter Server. So, there seems to be some communication problem between the vCenter server and our domain controlllers.
We found that if we put the vCenter server in the same subnet as our domain, we can then sign into the client without a problem.
We've tried many things including:
- hostname vs fqdn vs ip address vs local host
- using the "use windows credentials" checkbox vs manually typinig the username and password.
- we can ping back and forth between the domain controllers and the vCenter server with less than 1ms of delay and zero dropped packets.
So, our theory is that there is some kind of broadcast dependancy between vCenter and the domain controllers, but we can't seem to pin it down.
Has anyone dealt with this kind of issue before?
Do you know if any kind of broadcast dependancy between vSphere and the domain? I've ran 4.1 with vCenter on another subnet without a problem, but this is new to me. If there is a dependancy, how can we fix it?
Thanks everyone.