• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

Setting up a Windows 2000 Domain-controlled network

Status
Not open for further replies.
Here's the setup we have at work, sorry if it isn't very clear, I'm not an expert in office networks...

Two Dell "Precision 620" workstations (each with dual P3 1GHz, 256MB RAM, and SCSI HDDs), AFAIK one of these towers is controlling the "Domain" while the other is running Windows 2000 Server, the latter is connected to a ADSL modem and running an ISA Server for internet sharing. There is no router, instead everything is connected to a 10/100Mbit Ethernet hub/switches. There are about 15 client PCs in all offices that are running Windows 2000 and are controlled by the main server with strict privileges given by the system administrator. Very soon a custom-built database application using MS Access will be running on most client PCs, this too will need to be under strict control from the administrator.

Is this an ideal setup for the current hardware available? Are there any obvious improvements that can be made? Would buying new hardware add substantial benefits?

I would truly appreciate any feedback.
 

capslock

Is jealous of Matlock's emoticon
Given that you have one Primary Domain controller you should have at least one other server running as a backup domain controller, most likely they are both running Windows 2000 server. If all the client computers and servers are Win 2000 or higher you should set your domain in 'native mode'. It's fine if you're using an ISA server but make absolutely sure that you have only one NIC (ethernet card) on the primary domain controller, or will get a host of problems.


I think the solution you're using is fine given the small size of your network.
 
Thanks capslock, that's reassuring... But I'd like more feedback from other users if possible.

demi, would accept Amazon Gift Certificates as payment? I can't use PayPal :p
 
MS Access? Noooooo! I don't suppose you have any control over that but Access has almost zero concurrency controls so if everyone is using (well, writing) to the same database it could get ugly very quickly.
 
cubicle47b said:
MS Access? Noooooo! I don't suppose you have any control over that but Access has almost zero concurrency controls so if everyone is using (well, writing) to the same database it could get ugly very quickly.

That's the management's fault for outsourcing the system to a cheap developer.

umm, so it should've been SQL or something?
 
Status
Not open for further replies.
Top Bottom