Discussion Locked

BEST SETUP FOR FILE/PRINT SHARE NETWORK

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

What is the best setup for a file/print share network. I have 10 stations (Win98) all considerably new. I have 1 server (WinNT) As of now it has 3 NIC's in it. The servers NIC's are connected to a NetGear 16 Port 10/100mpbs hub and so are each of the computers. Right now the situation is ok, but I feel there is more I could do. I want to know how to setup from scratch or what I can do. I am not stating the proto's, adapter's etc. because I basically want a from "scratch" or beginning answer. There is only one computer connected to the internet and it is also connected to the network. The network is a LAN.

What is the best and fastest configuration for a file/print sharing network!?!

PLease help me fill this empty thought...

8 replies

by ntoz

First, I think the three network cards are a bit overkill. If your using two of them for fault tolerance through the servers bonding, I can understand. If you just have three cards in there though to service your 10 stations, its not really buying you anything, just additional load on the server from a services stand point.

Second, a migration to Windows 2000 at this point might be a good thing before you get too entrenched, its easier to go from nothing to 2000 then migrating.

Third if you do go to Windows 2000 or XP, you can setup quota management and keep users at bay as to how much disk space they use.

Fourth Centralizing all users data files on a home directory will enable you to wipe and replace a system with out worry as to what might be on the system. You can then create images of the systems and keep them on the server for quick deployment.

by ntoz

If Windows 2000 is not an option, Windows NT should do just fine for the type of enviroment you have. You might look to using logon scripts in which to configure the Windows 98 systems mapping to drives, home directories and shared resouces. You could lock those windows 98 systems down a bit, in doing so preventing the install of outside software, changing of important settings, and other items that get users in trouble. Placing the profile on the server that would pick it up upon logon to the domain. By centralizing the users files on the server, you can ensure a backup of those files from the file server. Which leads me to another important thing GET A GOOD BACKUP DRIVE, GET NEW TAPES, ROTATE TAPES with an off site tape at the end of theweek, get a safty deposit box at a bank and drop it off once a week. REPLACE TAPES as they go through cycles. VERIFY YOUR BACKUP. Test your backups occationaly to a test system. Im running out of ideas this turn around the block, email me if you have questions. The Windows NT 4.0 Resouce kit has a host of information and you also should get a good book on Windows NT Server, Sybex makes a number of them Mark Minasi has a good book on it as well, NT 4.0 books also can be had cheep on EBAY in usedbut good condition.

Pete

by mckaytech

From a network design perspective, the single biggest boot to performance you could offer would be to upgrade the hub to a switch. The three server NICs are not really buying you anything except load on the server, particularly when plugged into a hub rather than a switch.

For your size of network, I would start with an NT4 or W2K server with a single server-class NIC. Depending on how mission-critical the server is, I would look for it to have tape backup (mandatory), RAID5 or mirroring, and lots of RAM.

To that I would add a capable switch. Not all switches are equal and you generally get what you pay for - a higher price will usually bring a higher-speed backplane and greater expansion possibilities.

I would set the network up as a pure IP network since you do have Internet access and could potentially then share the connection from the workstation (although I think a Cable/DSL router is preferable).

That having been said, if you want to tune your existing setup, youwant to first identify the bottlenecks and direct your attention to them. Is your CPU maxed out? Are there lots of page swaps because of insufficient RAM? Are there lots of collisions on the network because it is not switched? Is your cabling upto snuff? And so on. Quite often, I've seen lots of money spent and time invested in the wrong things. For example, if the CPU is pegged all the time, a new switch, additional NIC, or faster workstations would be a fruitless investment.

regards!

paul

by cavedweller

From the beginning...

I would start with a small server with expansion possibilities and set it up as PDC. RAID is a must as is a UPS and tape drive. The smaller Dell PowerEdge servers can be purchased this way. You can order them with 1 processor and add another when (if) you need it. Get the highest density memory you can afford so that you still have some empty sockets to add more. Other manufacturers probably have similar products.

A stackable switch such as the 3Com 3300 series lets you buy one unit now and stack a few more as your needs grow. These are available with a variety of high-speed uplink ports. Plug it into the UPS too.

If you can afford it, install a seperate machine with firewall software and use it to connect to the internet. If you have an external web server, run it there. This way external requests don't bog down your PDC and it isn't exposed directly to the world either.

The HP network printers are easy to configure. I setup print queues on the PDC using DLC protocol to the printers. Clients print to the PDC's queue. This allows you to redirect the queues to different printers if one fails or you want to add another and pool them without having to change the settings on all the clients.

How fast is fast enough (when do you stop tweaking?) When the solution is acceptably fast for the users. You can always make a little improvement here and there but getting the last 5% in performance can take 95% of your time.

This discussion is closed to new replies.