• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 371
  • Last Modified:

Domian Controller Win Server 2008 r2

I have set up a Domain Controller in a Windows 2008 r2 environment. I used the defaults and setup the DNS.  So far I have the server acting as the DHCP and the "Client" computers are connecting through the server (I think).  I have a router in the mix and the server is connected to it.    Here are some numbers:

Router
192.168.2.1
DHCP is disabled

Server:
Lan 1

IP Address 192.168.2.2
Subnet 255.255.255.0
Default Gateway 192.168.2.1

DNS 192.168.2.2
ALT  192.168.2.1

LAN 2
IP Address 192.168.2.3
Subnet 255.255.255.0
Default Gateway 192.168.2.1

DNS 192.168.2.2
ALT  192.168.2.1

The DHCP range is 192.168.2.101 to 200

I can look at the leases in the Server and all of my computers and printers are listed.

I have added the computers in question to the Active Directory. (As well as the user)


Anybody have any ideas
0
Pat Clancy
Asked:
Pat Clancy
1 Solution
 
Adam BrownSr Solutions ArchitectCommented:
Well, it's generally recommended that a Domain Controller only have 1 NIC...but I'm not sure if I'm reading your post correctly. Is there an issue you're running into with this setup?
0
 
Darius GhassemCommented:
You need to disable all network cards except for one if you are running this server as a DC. DCs shouldn't be multihomed servers.

Second you need to remove ALT  192.168.2.1 this is not a internal DNS server for your domain. When you are on a domain your DCs, member servers, and clients should only point to internal DNS servers which are usually DCs only.

After doing the above go to command prompt ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix
0
 
BawerCommented:
just a question, why you have two nics in the domain controller, although a DC can have two NICs if the ranges are different however i see both the LAN IPs are from similar subnet,
0
 
Pat ClancyCEOAuthor Commented:
I did not know that I could only have one NIC I have disabled the second one. I am working on solution 2 at the moment.

I'll let you all know what happens and thank you for you quick responses.

Thanks
0
 
Pat ClancyCEOAuthor Commented:
I also went into the properties of the computer that I wanted to join the domain and added the Address to the DNS port. then was able to join the domain straight way.  Thank you for your help.
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now