Different Network with One Domain Controller

I have 5 Network Locally and with One Domain Controller Windows 2000 how I add different Networks Clients in One DC with one NIC card and Kindly tell me the Minimum requirement of hardware and for Additional DC Hardware I am waiting for earlier response.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Very sparse question – we probably need much more info for a great answer – so I will try for a good answer.

A – if 5 nework locally is 5 client machines and one server, then you need a 8 port switch to connect them and the appropriate cabling between systems and switch.

B – “how I add different clients” – from each workstation logged in as local administrator “Join the domain”.

C – minimum hardware is totally determined by the applications and traffic you will be running. I have old Proliant 800 with dual PIII cpu’s, 1 GB ram, small raid (4-17GB Scsi drives as 52GB array) using Intel Pro100 Server NIC (i960) and serving as primary login for 100 users.
a – the primary login server needs a good NIC and enough memory for concurrent sessions.
b – CPU speed is not near as important.
c – drive space only matters if it is the only server in the domain. Storage appliances mean most DCs should not be used for file servers.

That should get you started – Good luck.

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Faisal1
    Hi; I have following Networks , , , and and I have 100 Clients on each network so How I join different Networks on One Domain Controller kindly tell me Thanks for reply
    0 pointsBadges:
  • Admiral
    Fisrt of all, Where are all these clients? Are they all in the same building? Second, what is the specifications of your server that you current have as a Domain Controller, Because with 500 users you will need something that can handle 500 users. Also, if you haven't you will also for your DC protection, want to replicate it with another server. The different local network shouldnt be an issue to add them to the DC. Give me a little more detail and I will be more than happen to assist you
    0 pointsBadges:
  • Petroleumman
    Hello, Based on your addressing scheme for each of your five networks, it appears that you are using NAT and each of your networks is actually a subnet of a single domain. If this is the case then it is possible to join all of your client computers regardless of the subnet to the domain and host them on one DC, if your not concerned with performance or reliability. What's your plan should your single DC fail? One DC leaves you with a single point of failure for 500 clients, if it goes down your entire network goes with it. You did not mention physical location of your subnets, are they all local or are some remote? Depending on connection speeds your going to have very slow logon times at best for all remote sites and any downstream subnets in a local configuration. Some of your slower connections could fail all together during logon leaving them useless. Have you thought out your DHCP and DNS schemes? If your planning on running these services your DC your going to be taxing it's resources pretty hard, especially during start of business hours when logon traffic is highest. Best practice would suggest setting up one DC per subnet. DHCP should be local to each subnet and each subnet should host a replica DNS server to speed things along. Remember, W2K DC's use Active Directory which relies heavily on DNS. You may consider re-thinking your plan and requesting additional resources for your project or you could be in for a lot of sleepless nights! Good Luck!
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: