Vista can't join active domain

I'm getting this error when I try to connect vista / windows 2008 RC to my
domain on windows 2003.

"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 DNS server that can
resolve DNS names in the target domain"

I seachd and found some possible solutions but no of them resolve the issue.
This is my home network. I am barely familiar with AD, just setting it up
for development testing.

If anyone has any thoughts about how to fix it, a simple step by step would
be appreaciated.

Thanks.

Howdie!

D Browne schrieb:
> I'm getting this error when I try to connect vista / windows 2008 RC to
> my domain on windows 2003.

AD is setup well and working?

> "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 DNS server
> that can resolve DNS names in the target domain"

This pretty much indicates that DNS is broken. You might want to check
if you can reach the DNS server by using nslookup. Check if the right
DNS server is specified and that connectivity is given.

> I seachd and found some possible solutions but no of them resolve the
> issue. This is my home network. I am barely familiar with AD, just
> setting it up for development testing.

What checks did you run? If there's no solution you can find, please
post the output of ipconfig /all if you care to "expose" this ( - I know
this might expose your IP addressing scheme).

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.

Like I said before, I am only so-so familiar with administoring AD. It
appears that AD is working correctly. At least on the server itself. I can
ping the server and get back a response if I use ping serverIP. If I use
ping server\domain I return this:

"Ping request could not find host greencola.home"

nslookup domain returns:

Server: unknown
IP Address: <correct IP address for AD server>

name: greencola.home

This is the result of IPconfig /all on the client

Windows IP Configuration

Host Name . . . . . . . . . . . . : DennyVista
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit
Ether
net Controller
Physical Address. . . . . . . . . : 00-1A-92-4E-95-5E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, January 20, 2008 1:19:07 PM
Lease Expires . . . . . . . . . . : Tuesday, January 22, 2008 9:18:08 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.50
Primary WINS Server . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4137:9e50:286c:338d:3f57:fffd(Pref
erred)
Link-local IPv6 Address . . . . . :
fe80::286c:338d:3f57:fffd%10(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{1437D8C3-CBAF-4F4D-9A9F-1B31A9F8C
DC3}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.2%12(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.50
NetBIOS over Tcpip. . . . . . . . : Disabled

I've disabled IPv6 on the client as well as the network card with no
connection.

The ipaddress is obtained automatically. The preferred DNS server is set to
the ipaddress of the server 0.50
The default gateway is set to 0.1 which is the ipaddress to the router.

Ive disabled the firewall on both the client and the router. I am totally at
a lose

Thanks

"Florian Frommherz [MVP]" <florian@PLEASELEAVETHISOUT.frickelsoft.net> wrote
in message news:eUxJqVAXIHA.4740@TK2MSFTNGP02.phx.gbl...
> Howdie!
>
> D Browne schrieb:
>> I'm getting this error when I try to connect vista / windows 2008 RC to
>> my domain on windows 2003.
>
> AD is setup well and working?
>
>> "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 DNS server
>> that can resolve DNS names in the target domain"
>
> This pretty much indicates that DNS is broken. You might want to check if
> you can reach the DNS server by using nslookup. Check if the right DNS
> server is specified and that connectivity is given.
>
>> I seachd and found some possible solutions but no of them resolve the
>> issue. This is my home network. I am barely familiar with AD, just
>> setting it up for development testing.
>
> What checks did you run? If there's no solution you can find, please post
> the output of ipconfig /all if you care to "expose" this ( - I know this
> might expose your IP addressing scheme).
>
> cheers,
>
> Florian
> --
> Microsoft MVP - Windows Server - Group Policy.
> eMail: prename [at] frickelsoft [dot] net.
> blog: http://www.frickelsoft.net/blog.

Howdie!

D Browne schrieb:
> "Ping request could not find host greencola.home"
>
> nslookup domain returns:
>
> Server: unknown
> IP Address: <correct IP address for AD server>

That looks bad. The client needs to contact the DNS server in order to
make requests against it and "find" the domain controllers to join the
domain. Since the client's settings seem to be o.k., you might want to
check the DNS settings on the server - is DNS running on the server? Is
the server able to nslookup itself and the domain?

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.

On Jan 22, 1:44*am, "Florian Frommherz [MVP]"
<flor...@PLEASELEAVETHISOUT.frickelsoft.net> wrote:
> Howdie!
>
> D Browne schrieb:
>
> > "Ping request could not find host greencola.home"
>
> > nslookup domain returns:
>
> > Server: unknown
> > IP Address: <correct IP address for AD server>
>
> That looks bad. The client needs to contact the DNS server in order to
> make requests against it and "find" the domain controllers to join the
> domain. Since the client's settings seem to be o.k., you might want to
> check the DNS settings on the server - is DNS running on the server? Is
> the server able to nslookup itself and the domain?
>
> cheers,
>
> Florian
> --
> Microsoft MVP - Windows Server - Group Policy.
> eMail: prename [at] frickelsoft [dot] net.
> blog:http://www.frickelsoft.net/blog.

Hi,

Do not think this is the issue but maybe look at it to determine if
this can be fixed

Lease Obtained. . . . . . . . . . : Sunday, January 20, 2008 1:19:07
PM
Lease Expires . . . . . . . . . . : Tuesday, January 22, 2008
9:18:08 AM

What would happen if you manually add the DNS server's IP address as
the primary and only the primary?

Pinging a machine with IP removes DNS out of the picture and you have
pretty much hit the nail on the head with the following error.
"Ping request could not find host greencola.home

This could be one of a few things but first places to check are: DNS,
DNS, DNS

Good luck

Harj Singh
Power Your Active Directory Investment
www.specopssoft.com

I was able to get it to work by adding the computers to the active
directory... This is probably a basic instruction so thanks for the help.

"Harj" <cisqokid@gmail.com> wrote in message
news:913459c8-c8e4-49b2-b1cd-d39ef67e3a9a@e10g2000prf.googlegroups.com...
On Jan 22, 1:44 am, "Florian Frommherz [MVP]"
<flor...@PLEASELEAVETHISOUT.frickelsoft.net> wrote:
> Howdie!
>
> D Browne schrieb:
>
> > "Ping request could not find host greencola.home"
>
> > nslookup domain returns:
>
> > Server: unknown
> > IP Address: <correct IP address for AD server>
>
> That looks bad. The client needs to contact the DNS server in order to
> make requests against it and "find" the domain controllers to join the
> domain. Since the client's settings seem to be o.k., you might want to
> check the DNS settings on the server - is DNS running on the server? Is
> the server able to nslookup itself and the domain?
>
> cheers,
>
> Florian
> --
> Microsoft MVP - Windows Server - Group Policy.
> eMail: prename [at] frickelsoft [dot] net.
> blog:http://www.frickelsoft.net/blog.

Hi,

Do not think this is the issue but maybe look at it to determine if
this can be fixed

Lease Obtained. . . . . . . . . . : Sunday, January 20, 2008 1:19:07
PM
Lease Expires . . . . . . . . . . : Tuesday, January 22, 2008
9:18:08 AM

What would happen if you manually add the DNS server's IP address as
the primary and only the primary?

Pinging a machine with IP removes DNS out of the picture and you have
pretty much hit the nail on the head with the following error.
"Ping request could not find host greencola.home

This could be one of a few things but first places to check are: DNS,
DNS, DNS

Good luck

Harj Singh
Power Your Active Directory Investment
www.specopssoft.com