Discussion Locked

Designing an NT network

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am planning to implement a server-based Windows NT network. I currently have a facility with 20 workstations and will double this amount in the next month or two.
The workstations are on two different floors.
I am seeking suggestions for currentand future requirements, and suggested protocols and channel access methods best suited to this situation.A good suggestion would be considered extremely valuable to me.

9 replies

by shmaltz

If all you are looking for is file sharing plus file security, and easy management (backup, printers) then there is not much you have to do. You did not mention what OS the workstations run, but I assume win9x.
I also assume that for now you are talking to start with one server with file sharing and domain security for 40 users. I also assume that you know how to install programs and windows NT server, plus how to manage a domain.
Hardware and Design:
Get a computer that has SCSI hard drive dont go with IDE harddrive. If possible make sure it has hardware RAID (I like level 5, which improves file read and write plus its fault tolerance, for RAID 5 you will need at least three harddrives).
Backup, get a good backup drive (I like the DLT).
Memory, with the prices so low get at least 512MB.
CPU go for the Ghz ones (again since its so cheap why not).
Power, you should get a UPS (if you are not in california it dosn't have to be an expensive one for your environment).
Partition, make one partition for the OS which should be around 4 GB (in most cases this is enough), use the rest for the data.
Naming is one of the most important things (I know some people disagree). Name your servers in a way that it will be easy to remember what server you are talking about (the same goes for workstations, No its not a good idea to name workstations after the user that logs on to it, rather name it after the department or room where it belongs, like finance1, finance2 and so on). The same goes for the domain name.

by shmaltz

Installation:
Set up windows NT or 2000 server (if you want to use active directory you can do it but I wrote the above hardware recomendations for an NT Domain not AD, and you should know AD very good before you set it up its not as easy as NT domains).
In NT setup chosse as Primery domain controller (PDC).
After the installation is complete, install the latest service packs (SP6a).
For protocols use only TCP/IP (dont use any other), set up the server as an DHCP server (unless you have another computer that acts as an DHCP server). Next setup WINS. Next setup the backup software, you can either use the one that comes with windows NT or buy third party software to do that. With windows NT backup program you also have to schedule it to run (unless you want to baby sit the computer when it runs the backup).
Next setup the users and the passwords. Set the security on the folders they will be using (always assign security to local groups and not global groups or users, users should always be a member of a global group not local).

by shmaltz

Client side:
On the client side you should make sure on all win9x machines that in the properties of client for microsoft networks the check box logon to windows NT domain controller is checked. For windows NT workstations make sure they join the domain. (you should create a policy for the win9x clients that dosnt let them use windows if they didnt log on to the domain).

by shmaltz

Network:
As for the 2 different floors, since we are only talking about 40 users you dont have to user routers, you can go by with switches (dont use hubs). I would set it up: one switch on each floor and then link all the floors together by another switch (if you have more then one switch per floor then always link all the switches to the same switch otherwise you going to end up with to many hardware hops to reach a workstation). If you only use 2 switches (one for each floor) then just uplink one to the other, and when you get a third one also get a 4th to do uplink.

by shmaltz

Some suggestions:
Move all your localy connected printers that are shared, to the server (using something like JetDirect).
You can do the above slowly since I assume you already share files you will not have to force every one at once to log on to the server. Just have them logon to the workstations with a username thats valid on the domain and it will work.
If you currently use NETBeui you can stay with it for a while and after every thing else works out you can do the TCP/IP and WINS.
Hope this helps.

by wmr029

Not knowing your exact needs I am assuming that you are basically looking for file and printer sharing. Some rules of thumb I follow.

1) Always go with a minimum of two domain controllers. Your users will NOT forgive you if they can not log onto the network.

2) For printer sharing. (assuming you have more than one printer) Split them across available servers. If one server goes down users can still print to anothe rprinter controlled by an different server. Again users are very unforgiving when they can not print.

3) For basic file sharing look at a NAS appliance. They are etremly cost effective. Dell offers a unit whichn when configured as a RAID 5 device, provides over 100GB of useable disk space for under $2500.

4) Protocols: TCPIP at a minimum.

5) Tape Backup. I try to size my solution so I cna do a full backup on one tape. IF your backup windows allows it I would do a full backup every night. This may seem wasteful, but it really makes it easier to do a restore for a client and can drastically reduce the time to reload a system.

This discussion is closed to new replies.