Win2k pro w/windows 2000 server 1

[daren33]

I am preparing to setup a windows 2000 server network with windows 2000 proffesional workstations. I ran into all kinds of problems the last time I tried to do this as I am from an NT backround. It's not the same as setting up NT. What is the proper sequence as far as adding computers to a domain, setting up a domain, etc... Thanks, Daren

 

[FilthPig]

1. Install Windows 2000.
2. Set up DNS.
3. Run DCPROMO to install active directory (makes it a domain controller).
4. Add computer accounts.

Anybody who reads enough of my posts on very broad subjects will run into this advice:

I recommend Mastering Windows 2000 Server by Mark Minasi. Has good information for newbies and NT Veterans.

...I wonder if I can buy stock. Marc Creviere

 

[cvtech]

I was wondering, is there anything special that has to be done if the windows 2000 server is running on a connection from mediaone linksys router that is configured for DHCP? If the linksys router is assigning IP address by DHCP but fixed IP's are setup on the server what must be done in order for the 2000 workstation to see the domain?

 

[FilthPig]

Yeah, make sure that DHCP is handing out your local DNS server to the clients instead of your ISP's. If you still want the ISP's DNS to handle internet lookups, then set it up as a forwarder on your local DNS.

If you have your forward lookup zone in DNS set to allow dynamic updates, and your 2kpro machines set to register their connection in DNS (default), then machines will create their own host entries also. Marc Creviere

 

[tertone100]

Good info from FilthPig, also a good book. Your Linxys router can act as a Dhcp or you can use your own addresses. Be sure that if you use it as a Dhcp the adresses of your servers are not in the dhcp scope. You should always use static addresses for your servers and be sure that they are on the same subnet. If you are not sure about Dns,Windows can configure it for you (free of charge) when you run dcpromo. If you configure Dns yourself be sure to creat a forward lookup zone (a must),active directory intagrated and allow secure dynamic updates. You can also creat a reverse lookup zone to resolve IP to host.

 

[Masterpjz9]

I would disable DHCP on the router and enable it on the 2k server. Have the server give the gateway to the internet (router)

 

[cvtech]

In reference to the message below. My router is the DHCP server. How do I make DHCP hand out my local DNS server to clients?



Yeah, make sure that DHCP is handing out your local DNS server to the clients instead of your ISP's. If you still want the ISP's DNS to handle internet lookups, then set it up as a forwarder on your local DNS.

If you have your forward lookup zone in DNS set to allow dynamic updates, and your 2kpro machines set to register their connection in DNS (default), then machines will create their own host entries also.
Marc Creviere

 

[tertone100]

Your linksys router will not hand out the IP of your local Dns server because it is only an allocator. You can either manually enter your local dns on your workstns or like Masterpjz9 say's disable DHCP on the router and enable it on the 2k server. Have the server give your wrkstns the gateway to the internet (router). With W2k dhcp use 006 Dns &003 Router to hand out Dns and gateway to wrkstns. You do not need to enabel forwarders to resolve internet requests, Therefore do not delite the root zone. However you will have to forward ports #53 udp & tcp to your internal dns server to resolve internet requests. Like FilthPig says your W2k Pro's will register there own host (A)records in dns. If you have a reverse lookup zone your dhcp will update your pointer record (ptr)in dns. If in dhcp you choose the option ALWAYS UPDATE DNS then your dhcp server will update both your (A) & (PTR) records, thus your dhcp server will be the owner of these records.


FilthPig, smart cookie (he must be a canadian)

 

[FilthPig]

Pretty close, grew up in Michigan.

...And actually if I remember correctly, if you give your LinkSys router your local DNS as it's DNS server, it'll hand that out to DHCP clients.

That said, as a matter of personal preference, I like to have my servers doing the work, and would have DHCP on the 2k server. This means static IP's for the router and the 2k server.

I mentioned forwarders because a lot of ISPs want you to use their DNS servers, and a lot of times it will be faster using theirs because you can get results from their cache.

You shouldn't have to forward port 53 on the router, since all DNS queries using that port will be going out. DNS query returns come in on different (+1000) ports. Marc Creviere