'Bad Domain Name' when configuring QuickPrep

[MarkLomas]

Hi there!

I have a bit of a double-whammy issue. Our vCenter server is NOT joined to our domain, and the domain itself is a single label domain! When attempting to specify the deails for our domain in QuickPrep, I keep getting a 'Bad Domain Name' error.

I've added our domain name and the IP address of a DC into the hosts file on the vCenter server, along with the IP address and hostname of the DC - but it still doesn't work (and I am restarting the view composer service after making changes).

Are there any other workaround tips that might help here, or is it really just much better an idea to have vCenter on the domain.

--

Mark Lomas

[admin]

please try also adding it to the broker host file.

Regards,

Christoph

Don't forget to award the points if this answer was helpful for you.

Blog:

http://communities.vmware.com/blogs/dommermuth |

[MarkLomas]

The View Connection server itself /is/ on the domain - it's on the VCenter server that is not.

--

Mark Lomas

[admin]

Yes, but you should give it a try.

[jrVMguy]

Mark,

Are you using View 3.0 ?

If so, then upgrade to 3.1, that made it possible for us to use our "single label" domain name.

i was able to install 3.1 right over the top of our 3.0 installation.

[MarkLomas]

We're already at 3.1. I think I'll just have to recommend that we get the VI server joined to the domain, as nothing is working!

[jgiardina1]

Mark, have you found a solution to this without adding your VCenter server to the domain?

In a lab, we have followed many threads regarding hosts files, dns entries, etc. with no avai. We also have a ticket in with VMware support that had been idle for days. Even though the VCS server has the hosts file entry, the VCenter server has the hosts file entry, both hosts can see each other, and the VCS server can connect to tcp port 389 on the domain controller, we are still get the "Bad Domain" error.

Let me know if you find anything, VMware is not helping much and adding the VCenter server to the domain is not an option.

[BonezOz]

Crazy question, but why not add the vCenter server to the domain?

[jgiardina1]

Not an option. If you are in a multi-client environment, like an ISP, this will not solve anything.

[BonezOz]

Well, that makes a heap more sense.

[ayazaslam]

Hi!

I had similar problem and got it solved.....

ESX server (X.X.X.150)

VirtualCentre(X.X.X.153) (In workgroup)

ViewManager(X.X.X.152) (Joined to domain)

Windows 2003 AD, DNS, DHCP

Make sure vCentre and ViewManager system have same DNS IP in preferred DNS. From both the server you should be able to ping your dc uisng fqdn. If you get this working you won't get the error "bad domain name"

In my case I didn't configured DNS ip on VirtualCentre machine.

[johnwilk]

Your VirtualCenter server does not have to be part of the domain but your View Manager does. I have this working perfectly with a standalone VC server.

[admin]

That's correct. All you need is a proper working DNS.

Sent with my BlackBerry