Prev: MSDTC starts even set to manaul
Next: moving and Enterprise CA from one DC to another
From: Ace Fekay [MVP - Directory Services, MCT] on 24 Apr 2010 14:33
On Sat, 24 Apr 2010 10:44:07 -0400, "JohnB" <jbrigan(a)yahoo.com> wrote:

>Maybe it's just me... but when I've joined an XP client to the domain I've
>never had to do anything to TCP/IP properties, I just leave it set to
>dynamic. With Windows 7 clients, I've had to specify the IP address of a
>DNS server for it to be able to find a DC. If I don't, I get the message
>"no domain controller found", or something to that effect. So the first
>time that happened I googled that, and found that yes, you have to *help*
>the Windows 7 Pro client find the DC by specifying a DNS server manually in
>TCP/IP properties.
>
>Are we talking about the same thing? I can't imagine you are... that you
>manually enter the IP address on 2000 & XP clients for the DNS server?

If you keep it set to automatic, then it is *assumed* the DHCP server
Option 06 is configured so ONLY the domain controller's IP address is
given for the DNS settings. Otherwise, expect issues.

If you had to specify the DC's DNS server IP manually, then it's
clearly indicating Option 006 is not set properly, or you are using
your router as a DHCP server, which the DNS address it is giving out
is incorrect.

There's really not much to DHCP. Just set it properly, and it gives
the clients the correct config, and all works.



Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
From: Ace Fekay [MVP - Directory Services, MCT] on 24 Apr 2010 14:39
As Kerry indicated, it appears the DNS server settings on the domain
controller are incorred. It shows the following:
DNS Servers . . . . . . . . . . . : ::1
211.29.132.12
8.8.8.8


To further explain:
The ::1 is the IPv6 address loopback. No problem with that one, but
the other two concerns me because they are external addresses.
Therefore, the DC cant't even "find" itself. Active Directory works
with DNS, therefore it queries DNS to "find" the domain, and that
includes a domain controller when itneeds to find itself.

I suggest to change the DNS address to 192.168.1.3.

If Internet access is what you're worried about, DNS will use the Root
hints. You can also configure a Forwarder for more efficiency. DNS
properties, Forwarders tab, then type in those two other DNS addresses
you have.

My blog offers a more detailed explanation:

Active Directory and Its Reliance on DNS, and using an ISP's DNS
address
http://msmvps.com/blogs/acefekay/archive/2009/08/17/ad-and-its-reliance-on-dns.aspx

I hope you find it helpful.

Ace




On Fri, 23 Apr 2010 01:46:22 -0500, clement <guest(a)unknown-email.com>
wrote:

>
>I'm having the same problem with a Windows 7 machine not being able to
>connect to the domain. All the Windows XP machines can join, it's only 2
>Windows 7 machines.
>
>The ipconfig/all logs are as follows:
>
>ipconfig /all from Windows 7 Machines:
>
>
>Windows IP Configuration
>Host Name . . . . . . . . . . . . : PERRY3
>Primary Dns Suffix . . . . . . . :
>Node Type . . . . . . . . . . . . : Hybrid
>IP Routing Enabled. . . . . . . . : No
>WINS Proxy Enabled. . . . . . . . : No
>Ethernet adapter Local Area Connection:
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
>Connection
>Physical Address. . . . . . . . . : 00-16-76-40-D1-7B
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
>Link-local IPv6 Address . . . . . :
>fe80::60eb:9a80:d217:5053%11(Preferred)
>IPv4 Address. . . . . . . . . . . : 192.168.1.7(Preferred)
>Subnet Mask . . . . . . . . . . . : 255.255.255.0
>Default Gateway . . . . . . . . . : 192.168.1.1
>DHCPv6 IAID . . . . . . . . . . . : 234886774
>DHCPv6 Client DUID. . . . . . . . :
>00-01-00-01-13-62-AD-CD-00-16-76-40-D1-7B
>DNS Servers . . . . . . . . . . . : 192.168.1.3
>NetBIOS over Tcpip. . . . . . . . : Enabled
>Tunnel adapter isatap.{75E881DF-81AC-491C-8A2A-FA40EAE89A87}:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : Microsoft ISATAP Adapter
>Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
>Tunnel adapter Local Area Connection* 9:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
>Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
>
>====================================================
>
>ipconfig /all from Windows 2008 Server:
>
>
>Windows IP Configuration
>Host Name . . . . . . . . . . . . : PERRY-SVR
>Primary Dns Suffix . . . . . . . : perry.local
>Node Type . . . . . . . . . . . . : Hybrid
>IP Routing Enabled. . . . . . . . : Yes
>WINS Proxy Enabled. . . . . . . . : No
>DNS Suffix Search List. . . . . . : perry.local
>Ethernet adapter Local Area Connection 4:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : HP NC382i DP Multifunction
>Gigabit Server Adapter #4
>Physical Address. . . . . . . . . : 18-A9-05-61-13-E4
>DHCP Enabled. . . . . . . . . . . : Yes
>Autoconfiguration Enabled . . . . : Yes
>Ethernet adapter Local Area Connection 3:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : HP NC382i DP Multifunction
>Gigabit Server Adapter #3
>Physical Address. . . . . . . . . : 18-A9-05-61-13-E2
>DHCP Enabled. . . . . . . . . . . : Yes
>Autoconfiguration Enabled . . . . : Yes
>Ethernet adapter Local Area Connection 2:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : HP NC382i DP Multifunction
>Gigabit Server Adapter #2
>Physical Address. . . . . . . . . : 18-A9-05-61-13-E0
>DHCP Enabled. . . . . . . . . . . : Yes
>Autoconfiguration Enabled . . . . : Yes
>Ethernet adapter Local Area Connection:
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : HP NC382i DP Multifunction
>Gigabit Server Adapter
>Physical Address. . . . . . . . . : 18-A9-05-61-13-DE
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
>Link-local IPv6 Address . . . . . :
>fe80::97dc:80c1:7488:b953%10(Preferred)
>Link-local IPv6 Address . . . . . :
>fe80::b82e:b192:bdaa:2cc6%10(Preferred)
>IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
>Subnet Mask . . . . . . . . . . . : 255.255.255.0
>Default Gateway . . . . . . . . . : 192.168.1.1
>DHCPv6 IAID . . . . . . . . . . . : 219719941
>DHCPv6 Client DUID. . . . . . . . :
>00-01-00-01-13-47-2C-CD-18-A9-05-61-13-DE
>DNS Servers . . . . . . . . . . . : ::1
>211.29.132.12
>8.8.8.8
>NetBIOS over Tcpip. . . . . . . . : Enabled
>Tunnel adapter Local Area Connection* 8:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . :
>isatap.{8A6E7293-7892-4ED4-A22C-BB152ECE43B1}
>Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
>Tunnel adapter Local Area Connection* 9:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . :
>isatap.{5801F605-9961-434B-A1C8-A06FC9CCDFCA}
>Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
>Tunnel adapter Local Area Connection* 11:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . :
>isatap.{B89F28EE-32D8-4201-B41D-A9CBAB2CF22C}
>Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
>Tunnel adapter Local Area Connection* 12:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . :
>isatap.{AD607B6F-E535-4818-A04B-075C1749F7B8}
>Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
>Tunnel adapter Local Area Connection* 13:
>Media State . . . . . . . . . . . : Media disconnected
>Connection-specific DNS Suffix . :
>Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
>Physical Address. . . . . . . . . : 02-00-54-55-4E-01
>DHCP Enabled. . . . . . . . . . . : No
>Autoconfiguration Enabled . . . . : Yes
From: Hank Arnold on 25 Apr 2010 07:41
I've not had to do anything special w.r.t. DNS to get W7 to join a
domain. I've set up 4 different computers so far and in each case, the
IP and DNS information was set to default.

The one thing I've noticed is that if the user name being logged onto
the computer is identical to a local one, you have to sometimes specify
the domain as part of the logon (e.g., domain\username)....


Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://it.toolbox.com/blogs/personal-pc-assistant/

On 4/24/2010 10:44 AM, JohnB wrote:
> Maybe it's just me... but when I've joined an XP client to the domain I've
> never had to do anything to TCP/IP properties, I just leave it set to
> dynamic. With Windows 7 clients, I've had to specify the IP address of a
> DNS server for it to be able to find a DC. If I don't, I get the message
> "no domain controller found", or something to that effect. So the first
> time that happened I googled that, and found that yes, you have to *help*
> the Windows 7 Pro client find the DC by specifying a DNS server manually in
> TCP/IP properties.
>
> Are we talking about the same thing? I can't imagine you are... that you
> manually enter the IP address on 2000& XP clients for the DNS server?
>
>
>
>
> "Bill Grant"<not.available(a)online> wrote in message
> news:%23E$ADT04KHA.4888(a)TK2MSFTNGP06.phx.gbl...
>> That "feature" came with Win 2000! Active Directory uses DNS to find a
>> DC. You have to go back to NT to find a DC using Netbios names rather than
>> DNS.
>>
>>
>> "JohnB"<jbrigan(a)yahoo.com> wrote in message
>> news:um0mg5t4KHA.620(a)TK2MSFTNGP02.phx.gbl...
>>> There's a *feature* in Windows 7, when joining a domain (assuming you
>>> have the Pro version) you have to specify your DNS server in TCP/IP
>>> properties. Otherwise it is unable to find your DC.
>>>
>>> Don't you just love these improvments to Windows!
>>>
>>>
>>>
>>> "clement"<guest(a)unknown-email.com> wrote in message
>>> news:6c7b2a298a1ad25fa221e511970d8fd6(a)nntp-gateway.com...
>>>>
>>>> I'm having the same problem with a Windows 7 machine not being able to
>>>> connect to the domain. All the Windows XP machines can join, it's only 2
>>>> Windows 7 machines.
>>>>
>>>> The ipconfig/all logs are as follows:
>>>>
>>>> ipconfig /all from Windows 7 Machines:
>>>>
>>>>
>>>> Windows IP Configuration
>>>> Host Name . . . . . . . . . . . . : PERRY3
>>>> Primary Dns Suffix . . . . . . . :
>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>> IP Routing Enabled. . . . . . . . : No
>>>> WINS Proxy Enabled. . . . . . . . : No
>>>> Ethernet adapter Local Area Connection:
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
>>>> Connection
>>>> Physical Address. . . . . . . . . : 00-16-76-40-D1-7B
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Link-local IPv6 Address . . . . . :
>>>> fe80::60eb:9a80:d217:5053%11(Preferred)
>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.7(Preferred)
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>> DHCPv6 IAID . . . . . . . . . . . : 234886774
>>>> DHCPv6 Client DUID. . . . . . . . :
>>>> 00-01-00-01-13-62-AD-CD-00-16-76-40-D1-7B
>>>> DNS Servers . . . . . . . . . . . : 192.168.1.3
>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>> Tunnel adapter isatap.{75E881DF-81AC-491C-8A2A-FA40EAE89A87}:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : Microsoft ISATAP Adapter
>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Tunnel adapter Local Area Connection* 9:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>>
>>>> ====================================================
>>>>
>>>> ipconfig /all from Windows 2008 Server:
>>>>
>>>>
>>>> Windows IP Configuration
>>>> Host Name . . . . . . . . . . . . : PERRY-SVR
>>>> Primary Dns Suffix . . . . . . . : perry.local
>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>> IP Routing Enabled. . . . . . . . : Yes
>>>> WINS Proxy Enabled. . . . . . . . : No
>>>> DNS Suffix Search List. . . . . . : perry.local
>>>> Ethernet adapter Local Area Connection 4:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : HP NC382i DP Multifunction
>>>> Gigabit Server Adapter #4
>>>> Physical Address. . . . . . . . . : 18-A9-05-61-13-E4
>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Ethernet adapter Local Area Connection 3:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : HP NC382i DP Multifunction
>>>> Gigabit Server Adapter #3
>>>> Physical Address. . . . . . . . . : 18-A9-05-61-13-E2
>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Ethernet adapter Local Area Connection 2:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : HP NC382i DP Multifunction
>>>> Gigabit Server Adapter #2
>>>> Physical Address. . . . . . . . . : 18-A9-05-61-13-E0
>>>> DHCP Enabled. . . . . . . . . . . : Yes
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Ethernet adapter Local Area Connection:
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : HP NC382i DP Multifunction
>>>> Gigabit Server Adapter
>>>> Physical Address. . . . . . . . . : 18-A9-05-61-13-DE
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Link-local IPv6 Address . . . . . :
>>>> fe80::97dc:80c1:7488:b953%10(Preferred)
>>>> Link-local IPv6 Address . . . . . :
>>>> fe80::b82e:b192:bdaa:2cc6%10(Preferred)
>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>> DHCPv6 IAID . . . . . . . . . . . : 219719941
>>>> DHCPv6 Client DUID. . . . . . . . :
>>>> 00-01-00-01-13-47-2C-CD-18-A9-05-61-13-DE
>>>> DNS Servers . . . . . . . . . . . : ::1
>>>> 211.29.132.12
>>>> 8.8.8.8
>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>> Tunnel adapter Local Area Connection* 8:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . :
>>>> isatap.{8A6E7293-7892-4ED4-A22C-BB152ECE43B1}
>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Tunnel adapter Local Area Connection* 9:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . :
>>>> isatap.{5801F605-9961-434B-A1C8-A06FC9CCDFCA}
>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Tunnel adapter Local Area Connection* 11:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . :
>>>> isatap.{B89F28EE-32D8-4201-B41D-A9CBAB2CF22C}
>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Tunnel adapter Local Area Connection* 12:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . :
>>>> isatap.{AD607B6F-E535-4818-A04B-075C1749F7B8}
>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Tunnel adapter Local Area Connection* 13:
>>>> Media State . . . . . . . . . . . : Media disconnected
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
>>>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>>
>>>>
>>>> --
>>>> clement
>>>
>>>
>
>
From: clement on 28 Apr 2010 00:09

Hi guys, thanks for your help. I have configured the DNS address of the
DC to 192.168.1.3 only, and all the clients have static DNS servers set
to 192.168.1.3 only. That solved the problem, thanks again!


--
clement
From: Kerry Brown on 28 Apr 2010 01:01
Glad to hear you got it working.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/


"clement" <guest(a)unknown-email.com> wrote in message
news:bcf53dbc531640ffb4a647eed5dd786c(a)nntp-gateway.com...
>
> Hi guys, thanks for your help. I have configured the DNS address of the
> DC to 192.168.1.3 only, and all the clients have static DNS servers set
> to 192.168.1.3 only. That solved the problem, thanks again!
>
>
> --
> clement

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: MSDTC starts even set to manaul
Next: moving and Enterprise CA from one DC to another