• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Virtual vCenter

R

RezQme

n00b
Joined
Apr 17, 2012
Messages
29
I have a vCenter server set up on ws 2008 R2 on my domain. My domain controller and DNS server is also ws 2008 R2.
When I log into vCenter server from vSphere Client on my W7 desktop (which is not a member of my domain, but is set to use the DC as its DNS server) I cannot access the consoles of any of the VMs. I get the following error message (displayed across the top of the console):

"Unable to connect to the MKS: Host address lookup for server xxxxxx.local failed: No such host is known"

I have no issues when I access the consoles on the same PC when logged directly into the Host in vSphere Client.

I believe my DNS records are set up correctly, I have a forward, reverse, and PTR record for my host, vcenter server, and DC.

What might my problem be?
 
How is the vCenter server DNS configured?

Make sure it can resolve the ESXi hostname(s). I got hung up on this before and correcting the DNS servers solved it for me.
 
From what I understand your workstation connects directly to the ESXi hosts when you use the console. The vCenter server does NOT act as a proxy. Make sure you can resolve from your workstation the ESXi hostnames.
 
Thank you guys for all the responses.
I will try these as soon as I get home today.
 
So, as it turns out I can't ping the host by DNS name from my workstation.
I can't ping my vCenter server by DNS name OR IP address from my workstation, but I can log into vCenter from my workstation.
I can ping my host by IP address, but not DNS name. I have tried removing and redoing the forward lookups, reverse lookups, and PTR. No changes so far...
 
disable the firewall domain profile on the 2008 r2 DC/DNS.
 
RezQme said:
Just tried disabling it on the DC and the workstation...no change :-\
Click to expand...

is your workstation using the DNS on the DC as its primary? Just from glossing over this thread it seems that the workstation isnt resolving through the DC system, which would indicate something blocking that communication, whether its a FW issue or gateway, etc issue.
 
The workstation is set to use the DC as primary DNS. quick ipconfig confirms this. I can ping everything by DNS name from the workstation except for the esxi host.
However, the workstation is not part of the domain. Should that matter?
 
RezQme said:
The workstation is set to use the DC as primary DNS. quick ipconfig confirms this. I can ping everything by DNS name from the workstation except for the esxi host.
However, the workstation is not part of the domain. Should that matter?
Click to expand...

No, i connect to my vcenter from a workstation not in my domain with no issue using domain creds.

I do however have all FW profiles disabled on my 2008 r2 domain system hosting vcenter. And using a Virtual 2008 R2 DC/DNS for resolution with no issue.

can you verify your ESXi host itself has proper network configuration>? Netmask/gateway/etc. Perhaps an IP conflict even?
 
It looks like everything on the host is acceptable. I can ping the host by DNS name from the DC and he vcenter server, just not my workstation. The only thing I saw is that some of my machines have a netmask of 255.255.248.0 and some are 255.255.255.0, but they are all 192.168.0.x, so ...that shouldn't matter either?
 
definitely a broadcasting issue I think. They should all be 255.255.255.0 if everything is on 192.168.0.x. if its a /24
 
That was it! I thought that it would be okay because the 255.255.248.0 netmask included the 255.255.255.0 subnet... but apparently I don't understand subnetting very well

I appreciate the help very much
 
Actually I still can't ping the esxi host by name from my workstation, but logging into vCenter from my workstation I now seem to have full functionality (opening consoles). I'll try to figure that out tomorrow...
 
RezQme said:
That was it! I thought that it would be okay because the 255.255.248.0 netmask included the 255.255.255.0 subnet... but apparently I don't understand subnetting very well

I appreciate the help very much
Click to expand...

having a too-wide subnet on one or more hosts could cause loss of connectivity (since said host(s) would be trying to connect directly rather than go through routing), but if as you say, they are all 192.168.0.x IP addresses, this should not matter.
 
That's what I thought... and they are all 192.168.0.x addresses.
So why might have changing the subnet mask from 255.255.248.0 to 255.255.255.0 fixed the issue?
 
You must log in or register to reply here.
Back
Top