Windows 7 can't join existing domain, DNS issue!

Are you using DHCP, if so then make sure that DHCP is giving out the correct address for the DNS server.
(run ipconfig /all on the Win7 machine.

If not then set the DNS server address on the Win7 Machine manualy to point to the DC

Have you tried using the FQDN instead of the NetBIOS name, such as domain.local instead of DOMAIN?

This is from the W7 Machine :

Pv4-adresse . . . . . . . . . . . . . . . . : 192.168.1.33
   Undernetmaske. . . . . . . . . . . . . . . . : 255.255.255.0
   Rettigheden opnået . . . . . . . . . . . . . : 23. februar 2010 14:29:32
   Rettigheden udløber. . . . . . . . . . . . . : 3. marts 2010 15:23:59
   Standardgateway. . . . . . . . . . . . . . . : 192.168.1.1
   DHCP-server. . . . . . . . . . . . . . . . . : 192.168.1.5

   DNS-servere. . . . . . . . . . . . . . . . . : 192.168.1.5
   NetBIOS over Tcpip . . . . . . . . . . . . . : Aktiveret


This is from the Windows 2003 server :

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.5
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.5

The domain is called 'HHF'

When i press HHF i get prompted for username and password
When i press HHF.local i do not get prompted.

Is it HHF.local, or .int or something else?

You should try assigining the machine a static IP & DN and then try joining the domain. Once joined you can then reset the PC to use DHCP.

I just tried to give the machine

192.168.1.33
255.255.255.0
GW 192.168.1.1

DNS 192.168.1.5

Same error when trying to join network.

Hi,

Can you try disabling the windows firewall on the domain controller & the machine you are trying to join?

regards

Hi!

No firewall is enabled on both machines.

Hi,

This could be due to Windows 7 local security policy

On the machine joining the domain can you do the following:

click start, type local and open the Local Security Policy Manager.

Select Local Policies -> Security Options, in the right find "Network Secuity: LAN Manager Authentication Level"  and set to "Send LM & NTLM - use NTLMv2 session security if negotiated".

And then try it...

Regards

Can you also check that the DNS server on the Domain Controllerhas the _msdcs, _sites, _tcp and _tdp zones setup in the Local Domain? If they are not there you can run "netdiag.exe /fix" to re-create the DNS entries required.

When you attempt to join the domain just enter HHF as the domain - do not add the suffix

richardburwood: I did what you suggested ! "Select Local Policies -> Security Options, in the right find "Network Secuity: LAN Manager Authentication Level"  and set to "Send LM & NTLM - use NTLMv2 session security if negotiated"."

^ No luck

Can you also check that the DNS server on the Domain Controllerhas the _msdcs, _sites, _tcp and _tdp zones setup in the Local Domain? If they are not there you can run "netdiag.exe /fix" to re-create the DNS entries required.

^ Where do i run this command ? I tried from a cmd prompt to use netdiag.exe /fix But it dosent accept the command! - i do not use the suffix.


KCT I try to login to the HHF domain and get prompted for username and password.

KCT I try to login to the HHF domain and get prompted for username and password. - i do not use the suffix.

Hi JarIK,

If you login to the Domain Controller and click Stert -> Administrative Tools -> DNS the system willopen the DNS Management Console. Under the name of your domain controller there is a folder called "Forward Lookup Zones". In this folder there will be an entry for your Active Directory Domain (HFF). Open this and there should be several more folders (sub-domains) under this domain. There should be entries for  _msdcs, _sites, _tcp and _tdp. Do these exist? If they don't you can re-create the dns settings using "netdiag.exe /fix". FYI: To use netdiag.exe you need to install the Windows Server 2003 Support Tools (on the Windows CD). The support tools also contain dcdiag.exe that may be of use. (See: http://technet.microsoft.com/en-us/library/cc758202(WS.10).aspx)

Regards

When i run this command - can the network in someway go down ?

I dont want to rick this right now!

Good Question... I'm not sure... I did find this online:

"What does netdiag /fix do

Netdiag /fix  switch is very useful tool to correct issues with DNS and domain controller tests. 1. DNS Test: If the computer is a domain controller, Netdiag verifies all the DNS entries in the Netlogon.dns file to determine if they are correct and updates the appropriate entries if there is a problem. 2. Domain Controller Test: If the domain GUID cached in a local computer on your primary domain is different than the domain GUID saved in a domain controller, Netdiag tries to update the domain GUID on the local computer."

Looking at this it should not make a difference to the restof the network as it is only verifying DNS setup and adding the correct entries as required. However the decision is yours...

I was having the same problem.

Added the IP address of my DC as a WINS server on my Windows 7 pc and it joined right up!