Connecting new machine to Domain Controller

So i've recently taken over the role of network administrator at my office. I refreshed a few desktops lastnight with Windows 7, but to the life of me.. could not get them to connect to the domain controller, which runs on server 2003.

Kept receiving errors pertaining to the DNS, could not reach DNS I believe.

-De-selected the IPv6 config
-Set the DNS to the new add, to that of the domain controller(although I left the IP dynamic, should this be a static IP)?

-The new machines are all dynamic in IP and DNS, but so were the old ones. Should I set a static to these new machines to add to the domain?

15 answers Last reply
More about connecting machine domain controller
  1. Is your DHCP is set to give the DNS? Look at one of the systems that is still on the domain and see what their dns settings are.
  2. Yes, its strange. The DNS on all machines are dynamic, when checked via ipconfig/network connections.

    How would I check if the DHCP is providing the DNS?
  3. Refreshed, exactly what did you do? A complete wipe and network installation of the Os ect via a server deployment ?
  4. Ping the Dhcp address, via the local machine.

    See if it returns a ping and latency across the network.

    You can do the same with a Dns numbers assigned to the network card of the host machine, and check the assigned Dns server numbers are correct. And the subnet address.

    You can do this through CMD prompt of the host machine with Ip config.
    Click on the start pearl ect, in the search box type cmd.
    A dos window will open.

    Type: Ipconfig/all it will pull up all of the details the Dhcp server assigned to the network adapter, Dns look up server Ip adresses, Ip of assigned to the network adapter of the host machine, and its subnet address it is working on within the network. Ping each of these see if you get a return. That way you can work out what setting is wrong. Using a static ip adress on a Dchp setup server will result a conflict because it has already assigned the details to another network adapter on the network and cannot release it due to it being in use already.
  5. Are you using Pro or Ultimate version? Home Premium can't join didn't specify which is why I ask.
  6. I'm assuming you have Windows 7 Pro. Try using the fully qualified domain name.
  7. zugzug_64 said:
    Are you using Pro or Ultimate version? Home Premium can't join didn't specify which is why I ask.

    Anonymous said:
    I'm assuming you have Windows 7 Pro. Try using the fully qualified domain name.

    You two had the same thought I did.

    As for getting it to do it, there is a way but it isn't supported natively on a fresh install. There was a user a few years back that had the same issue and his answer can be found right here on Tom's. You can read over it HERE .
  8. I'm using Ultimate.. Full Wipe, local install(small office). Also, thank you for reminding me weaselman.. for whatever reason, our network was being slammed lastnight..latency like I hadn't seen before. Could this be causing the error as well?
  9. If you are trying to establish this computer as the domain controller or just simply connect it to the domain, and there was high network traffic, you were probably hitting a major bottleneck because both the DC and the server were too busy trying to compensate for the already existent traffic.
  10. Awesome link hedwar! I will try a few steps and update the thread when I get back in the office. Thank you all
  11. a good way to check is nslookup
    click start type cmd and hit enter
    type nslookup
    does it resolve the fqdn?
    can you ping the dns server?
  12. nslookup can provide a breakdown of network errors?
  13. i would run
    click start type cmd hit enter
    net stats workstation
    that would show you network errors
  14. Nslookup.exe is a command-line administrative tool for testing and troubleshooting DNS servers. This tool is installed along with the TCP/IP protocol through Control Panel. This article includes several tips for using Nslookup.exe.
  15. Update. So apparently the domain's firewall settings are overriding the settings I am setting via GPO and the local firewall. I have disabled the domain firewall via regedit.
    Disabled the firewall via GPO and enabled incoming connections.. even stopped and disabled the service.. yet I am getting download speeds on this machine at 14mbps.. UPLOAD IS AROUND 0-.5MBPS on this machine only..and it takes about 4 hours to download a 3mb file from the web. This is the newly wiped, clean windows 7 install.

    The firewall is disabled on the domain controller and I cant seem to locate firewall settings via GPO in the DC(server 03 sp2). We are running a comcast bus. modem, netgear switch and a linksys router. DHCP is being provided by the router.

    Any ideas on this? I am stumped.
Ask a new question

Read More

Domain Controller DNS Windows 7