• 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.

* I just upgraded my NT Server 4.0 to Windows 2000 Server...I need a little help. *

N

nEoTeChMaN

Diamond Member
I get this annoying window pop-up about Active Directory service setup everytime I boot into Windows.

I don't know much about setting it.

I just want to maintain my Domain name "Domain".

It kept asking for some DNS address which I don't need.

How do I set it correctly?

Thanks in advanced.
 
If you installed AD, then you MUST have a Dynamic DNS server to maintain the domain. In W2K, MS finally linked the IP domain to the Windows domain (they're the same now).

If you installed Active Directory, it would have forced you to either point to a DNS for your domain, or install DNS on the AD server.

More info?

--Woodie
 
That is plain suck!

I just want to maintain a server and my Domain name is: Domain.

I shouldn't have to set up a DNS just to run a server.

I guess, I'll have to go back to NT Server 4.0.
 
Why do you want a domain? It's not that hard to set up your own little DNS server on the Active Directory (=Domain Controller) server. You just configure it for a non-public IP domain name (domain.local??), give it some private IP addresses, and set it up to forward requests to your ISP for Internet stuff.

I have a W2K server that's on 24x7, which does DNS & DHCP for my little 4 computer home LAN. I didn't bother with AD, since only two of the boxes are W2K, and I didn't want the performance overhead.

I guess the real question is what the benefits of a domain are for you.

--Woodie
 
I have 3 computers connect to the server. All 3 computers are a member of the domain called: Domain.

Can you explain a little more how to set it up?

Windows 2000 server kept popping up the Active Directory and demand for a DNS.

What am I suppose to put in there?
 
For the DNS IP address (which is what it's looking for?) put in the IP address of the server itself.

Once you get past that, do you really want a Windows domain?

Assuming that you do, on top of your current install you need to install/configure DNS.

In the "Configure Your Server" wizard, go ahead and install DNS. If it asks you, you are NOT a root server. Almost forgot, have your internet connection up when you install the server--it's going to try and contact the root DNS servers during install/configuration. I don't remember when exactly it does this, but it does this.

Go ahead and launch the DNS MMC (admin Tools - DNS). You need to create a "forward lookup zone". MS speak for setting up a normal DNS. See above note on not being a root server. Select a domain name--I suggest a non-internet one, like domain.local or 4CP.local or domain.idiot or some such. You're trying to avoid getting into future DNS issues, like if the domain name you choose shows up on the internet. As I remember it, the rest wasn't too bad to just follow the wizard.

If you want, you can configure the DNS using the Hints tab, and put in the DNS servers from your ISP. (Optional). Now configure your clients to point to your DNS server, and they'll route all their DNS queries to your DNS, which will forward Internet requests out to the internet, and handle internal ones (like MS Domain stuff) itself.

I'm having one issue--something on my network is triggering a Dial-on-Demand every hour, and I can't figure out who it is, so I can kill it. I suspect the DNS server might be doing it, but I can't prove it yet.

--Woodie

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top