• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2000 Advanced Server....

I

imported_goku

Diamond Member
I'm setting up a system with windows 2000 advanced server at home and I've been trying to get the whole domain/active directory thing working and I had a few questions.
1. Does the server have to be a DHCP server? Like can I have my router be the DHCP server and just have this computer on the network as a domain controller? Or do I have to have two NIC cards in the computer, one for the internet (in) and one out so it can act as a DHCP server...?
2. I'm a little confused about the reverse lookup zone and forward lookup zone thing, on the reverse lookup zone, it's asking for an IP address, do I makeup one or what?

I have the book Teach your self Windows 2000 server as reference for setting up the server. My biggest problem right now is the fact I'm unable to get one of my systems on the network to join the server and I'm not sure why.
 
Originally posted by: goku2100
I'm setting up a system with windows 2000 advanced server at home and I've been trying to get the whole domain/active directory thing working and I had a few questions.
1. Does the server have to be a DHCP server? Like can I have my router be the DHCP server and just have this computer on the network as a domain controller? Or do I have to have two NIC cards in the computer, one for the internet (in) and one out so it can act as a DHCP server...?
2. I'm a little confused about the reverse lookup zone and forward lookup zone thing, on the reverse lookup zone, it's asking for an IP address, do I makeup one or what?

I have the book Teach your self Windows 2000 server as reference for setting up the server. My biggest problem right now is the fact I'm unable to get one of my systems on the network to join the server and I'm not sure why.
Click to expand...

1) No your server doesn't have to serve DHCP.
2) Reverse lookup takes a known IP address & returns a name. Use the IP of the machine you're creating the entry for.

Viper GTS
 
Originally posted by: goku2100
I'm setting up a system with windows 2000 advanced server at home and I've been trying to get the whole domain/active directory thing working and I had a few questions.
1. Does the server have to be a DHCP server? Like can I have my router be the DHCP server and just have this computer on the network as a domain controller? Or do I have to have two NIC cards in the computer, one for the internet (in) and one out so it can act as a DHCP server...?
2. I'm a little confused about the reverse lookup zone and forward lookup zone thing, on the reverse lookup zone, it's asking for an IP address, do I makeup one or what?

I have the book Teach your self Windows 2000 server as reference for setting up the server. My biggest problem right now is the fact I'm unable to get one of my systems on the network to join the server and I'm not sure why.
Click to expand...

1 a. it does not have to be the dhcp server, it's fine to have your router be the dhcp server, but it really depends on what you want to do.

1 b. regarding the dual nic cards, you only need one unless you plan on using your server also as the firewall.

2. reverse look up etc would be in your DNS. you can set up your dns server after you install the OS no? hmm, if you do have to set it up now, it will be the same subnet your server is assigned to. eg. if you have assigned your server an ip address of 192.168.0.100 then it will be 192.168.0.x.
 
Originally posted by: PlatinumGold
1 b. regarding the dual nic cards, you only need one unless you plan on using your server also as the firewall.
Click to expand...

Thought about addressing this too, but since it's been brought up...

If you have the hardware to do it a dedicated firewall is a better way to go (unless as he mentioned you're using this machine as your firewall in which case it should NOT be your DC).

Smoothwall will run on a seriously old machine, I have it running on a P2 333 with 192 MB & it's happy as a clam.

Viper GTS
 
Using Win2k server for DHCP will give you a lot more configuration options to pass to the DHCP clients on your network, so it might be of interest.
 
Originally posted by: Viper GTS
Originally posted by: PlatinumGold
1 b. regarding the dual nic cards, you only need one unless you plan on using your server also as the firewall.
Click to expand...

Thought about addressing this too, but since it's been brought up...

If you have the hardware to do it a dedicated firewall is a better way to go (unless as he mentioned you're using this machine as your firewall in which case it should NOT be your DC).

Smoothwall will run on a seriously old machine, I have it running on a P2 333 with 192 MB & it's happy as a clam.

Viper GTS
Click to expand...

thanks😉 and I was wondering if I'm required to *actually register a domain name to be a domain controller with in an intranet.
 
Originally posted by: goku2100
Originally posted by: Viper GTS
Originally posted by: PlatinumGold
1 b. regarding the dual nic cards, you only need one unless you plan on using your server also as the firewall.
Click to expand...

Thought about addressing this too, but since it's been brought up...

If you have the hardware to do it a dedicated firewall is a better way to go (unless as he mentioned you're using this machine as your firewall in which case it should NOT be your DC).

Smoothwall will run on a seriously old machine, I have it running on a P2 333 with 192 MB & it's happy as a clam.

Viper GTS
Click to expand...

thanks😉 and I was wondering if I'm required to *actually register a domain name to be a domain controller with in an intranet.
Click to expand...

no, only if you have a domain already registered and you want to run exchange server, other than that, dynamic dns is a better option.
 
also, if you do set up a DNS Server and give it a non registered domain name you have to make sure not to make the domain a . domain. don't have a zone in the dns that is just a "."


 
1. No, but then your workstations won't be participating in dynamic updates. I would suggest that you allow the server to run DHCP, and disable it on your router. You only need one NIC card, either way. DHCP has very little to do with "Internet Connection Sharing", which I assume you're thinking about.

2. With such a small setup, you could just skip DNS and setup a WINS server. In your DHCP, add the dns servers that your router would otherwise have set for the workstation(s). Or, to take advantage of dynamic updates (it is an AD/DHCP/DNS integration), use DNS instead of WINS. You won't have to worry about setting the dns records because dhcp will take care of it for you.

also:

For your IP ranges, you should either use 10.1.1.1 - 10.255.255.254, or 192.168.1.1 - 192.168.255.254. There is also a Class B range (starts with 172) but I never bother with that one. 😛 I personally like the Class A range, 10, because it is such a clean number to deal with.

So for example, if you go with 10.1.1.4 as your server, and use a dhcp range for your workstations of 10.1.1.200 - 10.1.1.250, then you could set your router to use a static IP of 10.1.1.1 and make sure to add that as your gateway in the DHCP configuration.

When you set up a domain, it can't be something public. So it would be something like "home.domain". You could use "goku.dom". All of your workstations would end up with the suffix after the host name, like "workstation1.goku.dom". In your DHCP settings that suffix would be your domain.
 
Do you need to setup a DNS on the Domain Controller in order to join/access the domain? I'm currently having trouble joining/logging into the domain and I'm not sure if it's because of my DNS configuration or not.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top