Computer will not joint the domain
On the new computer (Win 7 Pro, 64 bit), went thru the Join Domain procedure. Control Panel/System/Computer Name, Domain, Workgroup does have the correct information. It keeps giving me the same error message "an active directory domain controller (AD DC) for the domain"kivu.com" could not be contact." I have joined two computers with everything the same and i didn't get this error message.
January 26th, 2012 6:26pm

ryayo wrote: On the new computer (Win 7 Pro, 64 bit), went thru the Join Domain procedure. Control Panel/System/Computer Name, Domain, Workgroup does have the correct information. It keeps giving me the same error message "an active directory domain controller (AD DC) for the domain"kivu.com" could not be contact." I have joined two computers with everything the same and i didn't get this error message. Have you looked into your DNS setup? Can you post the output of ipconfig -all from your Win7 Pc and from your AD DC. BTW if your AD is kivu.com, which is an external reachable dns domain, that setup is in my opinion not a good idea. For most setups it is better to use a subdomain like abc.kivu.com, which is not published to the internet. Wolfgang
Free Windows Admin Tool Kit Click here and download it now
January 26th, 2012 6:49pm

I don't have access to the DC but ipconfig -all gives host name................pcname Primary suffix............: Node type.................: Hybrid Ip Routing Enabled.....:No WINS Proxy Enabled....:No the domain is not Kivu.com, i was using that as an example.
January 27th, 2012 10:58am

Without seeing your client's DNS settings and comparing that to another system or validating your IP config on the DC/DNS server, its difficult to assist you. Without that information, my suggestion is that you run the ipconfig -all on a system that is not working and one that is working, then compare the results. The error message you received is typical of a problem resolving DNS records to locate your DCs. Its either a DNS client issue, or firewall filtering preventing communication with your DCs. Guides and tutorials, visit ITGeared.com.
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2012 11:05am

It might be the firewall filtering. I turned off the firewall and it still ddin't work. Ipconfig -all on my other machine which is on the network Host name..............................................:pcname Primary dns suffix...................................:Domain name Node type..............................................:Hybrid Ip Routing Enabled..................................:No WINS Proxy Enabled................................:No DNS suffix search list...............................:Domain name
January 27th, 2012 11:31am

I would try setting your AD controllers as your DNS manually in the adapter and see if you can join. If you can - voila you know the problem is your machine getting its DNS information. If it doesn't work then you know something else might be going on...
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2012 11:34am

Hi, Based on my research, I would like to suggest you perform the following to troubleshoot the issue: 1. Ensure you could ping your domain controller and the settings such as IP Address, DNS are correct. 2. Then turn off firewall and try setting AD controller as your DNS manually. 3. Enable NetBIOS over TCP/IP and ensure the TCP/IP NetBIOS Helper service is running. If the issue persists, please capture network package by following steps: 1. Download NetMon3.4 from the following website and install it on the computer http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f 2. Launch NetMon3.4. 3. In the NetMon3.4 window, click create a new capture tab. 4. In the new tab, select all the Network Adapters in the Select Networks window. 5. Then switch to Network Monitor, press F5 to start NetMon3.4. 6. Try to repro the issue. 7. Go back to the NetMon3.4 window and press F7 to stop the NetMon3.4. 8. Press Ctrl+S to save the NetMon3.4 file named what you like. Meanwhile, I noticed the following thread about the similar error and would like to share with you for your reference: Can connect to domain via static IP/DNS but not DHCP in Windows 7 Professional http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/4aa59cd1-a211-4972-a55b-faf950838b1a Hope this helps. Thanks.
January 31st, 2012 4:20am

Hi, Based on my research, I would like to suggest you perform the following to troubleshoot the issue: 1. Ensure you could ping your domain controller and the settings such as IP Address, DNS are correct. 2. Then turn off firewall and try setting AD controller as your DNS manually. 3. Enable NetBIOS over TCP/IP and ensure the TCP/IP NetBIOS Helper service is running. If the issue persists, please capture network package by following steps: 1. Download NetMon3.4 from the following website and install it on the computer http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f 2. Launch NetMon3.4. 3. In the NetMon3.4 window, click create a new capture tab. 4. In the new tab, select all the Network Adapters in the Select Networks window. 5. Then switch to Network Monitor, press F5 to start NetMon3.4. 6. Try to repro the issue. 7. Go back to the NetMon3.4 window and press F7 to stop the NetMon3.4. 8. Press Ctrl+S to save the NetMon3.4 file named what you like. Meanwhile, I noticed the following thread about the similar error and would like to share with you for your reference: Can connect to domain via static IP/DNS but not DHCP in Windows 7 Professional http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/4aa59cd1-a211-4972-a55b-faf950838b1a Hope this helps. Thanks.
Free Windows Admin Tool Kit Click here and download it now
January 31st, 2012 12:18pm

Thank you. I just re-imaged the laptop
January 31st, 2012 5:31pm

Thank you. I just re-imaged the laptop
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2012 1:29am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics