Cannot add Windows Vista PC to Windows 2008 domain

When trying to add a new Windows Vista (hqseven) machine to a Windows 2008
network I get the following error message... "An attempt to resolve the DNS
name of a DC in the domain being joined has failed. Please verify this client
is configured to reach a DNS server that can resolve DNS names in the target
domain." In the past year, I have added two XP, one Windows 7, and another
Vista box to the domain. I am not sure why I can't add my new Windows Vista
machine.

I am able to get on the internet with the Vista PC. I can RDP to the DC
(hqserver64) or any client. (using host name or static ip) I am also able to
ping the domain controller (DC) or any other computer on my network using
host name.

After initial info search I did find the following error message when doing
an nslookup from my new vista box.

mydomainname is a pseudonym.

nslookup mydomainname
Server: hqserver64.mydomainname.net
Address: 192.168.0.99
*** hqserver64.mydomainname.net can't find mydomainname: Server failed.

I do not understand why I am suddenly getting these error messages when I
have been able to join this domain in the past.

--
Stan Smith

Howdie!

Am 01.06.2010 19:28, schrieb Stan:
> After initial info search I did find the following error message when doing
> an nslookup from my new vista box.
>
> mydomainname is a pseudonym.
>
> nslookup mydomainname
> Server: hqserver64.mydomainname.net
> Address: 192.168.0.99
> *** hqserver64.mydomainname.net can't find mydomainname: Server failed.
>
> I do not understand why I am suddenly getting these error messages when I
> have been able to join this domain in the past.

That is a DNS issue. With that error message, it is 98% of the time. So
make sure you get those DNS errors clear, re-configure TCP/IP on the
NIC(s) of the machine, check whether a hosts file is bogus, false DHCP
settings, ...

Cheers,
Florian

Thanks that was helpful.

As it turned out the problem was associated with the integrated NIC on the
ASUS Crossfire Mother Board (Asus Crossfire IV--the new MOBO.)

The chipset is Marvell Yukon 88E8059 Family PCI-E Gigabit Ethernet
Controller. I had to check the box under the 'Use this connections DNS suffix
in the DNS registration'. Then I had to manually enter the full domain name
in Full Computer Name field prior to joining the domain.

My conclusion is that the NIC driver still needs a little debugging for this
new integrated NIC/MOBO to work together.

Thanks for pointing me in the right direction.

--
Stan Smith


"Florian Frommherz [MVP]" wrote:

> Howdie!
>
> Am 01.06.2010 19:28, schrieb Stan:
> > After initial info search I did find the following error message when doing
> > an nslookup from my new vista box.
> >
> > mydomainname is a pseudonym.
> >
> > nslookup mydomainname
> > Server: hqserver64.mydomainname.net
> > Address: 192.168.0.99
> > *** hqserver64.mydomainname.net can't find mydomainname: Server failed.
> >
> > I do not understand why I am suddenly getting these error messages when I
> > have been able to join this domain in the past.
>
> That is a DNS issue. With that error message, it is 98% of the time. So
> make sure you get those DNS errors clear, re-configure TCP/IP on the
> NIC(s) of the machine, check whether a hosts file is bogus, false DHCP
> settings, ...
>
> Cheers,
> Florian
>
>
>
> .
>

Hey Stan,

On 02.06.2010 00:34, Stan wrote:
> Thanks that was helpful.
>
> As it turned out the problem was associated with the integrated NIC on the
> ASUS Crossfire Mother Board (Asus Crossfire IV--the new MOBO.)
>
> The chipset is Marvell Yukon 88E8059 Family PCI-E Gigabit Ethernet
> Controller. I had to check the box under the 'Use this connections DNS suffix
> in the DNS registration'. Then I had to manually enter the full domain name
> in Full Computer Name field prior to joining the domain.
>
> My conclusion is that the NIC driver still needs a little debugging for this
> new integrated NIC/MOBO to work together.

Thanks for the feedback. Good to know what the error was. This'll
probably help others out here reading this.

Thanks again!
Florian