Forum Home
Press F1
Thread ID: 47202	2004-07-19 05:28:00	Advice on network structure for small business	LynH (669)	Press F1

Post ID	Timestamp	Content	User
253484	2004-07-19 05:28:00	I need advice on a suitable network structure for a small business. We have 6 staff, 3 desktop PCs and 1 laptop (2 x WinXP Pro, 1 x Win2K Pro, 1 x Win95), all linked by Ethernet 10/100 using 2 hubs. What do you recommend as a suitable structure for sharing files, internet connections, e-mail and running an order system (to be available from all PCs)? And would a Server of some sort be of use? If so, what software would be best to use on the Server? I have managed to get all PCs running on the Ethernet network, but know nothing about installing or setting up a server. I'd appreciate some discussion on the benefits and usability of of server software if anyone can put it in fairly straightforward terms. Thanks for your help	LynH (669)
253485	2004-07-19 05:43:00	What do you use for internet at the moment? And how is it connected?	kiki (762)
253486	2004-07-19 05:51:00	Because you are only using so few PCs, a server isn't really necessary . There are a few questions that would help determine what's best for you: 1) What internet connection do you have? 2) Are you very strict on security? (Esp . for filesharing) 3) Are you incredibly fussed about performance? 4) When you say email, do you mean to host your own e-mail server, or download it from an ISP, such as xtra, paradise, or ihug? 5) What is the physical layout of your offices? Will the all be in the same room? Different floors? (Studio, etc . ) 6) Although you didn't mention it, are there any other devices you will be sharing? (I . E . Printers, faxes copiers . . . ) However, a server could be advantageous . By no means does this mean a supercomputer, but an old PIII could do the job . If you don't want a server (cost, etc), then I suggest that you connect one computer to the net and share it from there . Bear in mind it will generally have to be on all the time . Also, depending on your ordering system, you could use this computer for this purpose too . An old computer could, however, be used for a server if you could get one . You could use this dedicated machine to sit in the corner and, a) run a database for your ordering system, b) share the internet, with a firewall on it for extra security, c) create a dedicated folder for sharing files, e) an internal email server (if you need one) . You download the trial copy of Windows Server 2003 to see how logging in to the server each day suits your fancy . This provides centrally controlled security, and the ability to administer each computer from a central location . This "client-server" setup improves performance and ease of administration, but given your size this shouldn't be a problem anyway . It does, however, mean that you will not have to bog down any other computers with this role . The "peer-to-peer" setup I described earlier (using a computer that's serving) can be easier to use and set up, but will not provide optimum performance . Although that shouldn't be a concern . In the end of the day, a dedicated server is really something you should need only if you were concerned about internet security So you have two options: 1) Peer to peer . --> Connect the internet to a computer, and share it from there . This will be one of the work computers . --> Share all the files you want on each computer . --> Attach the printers / copiers to separate machines and share them individually . --> Individual logins for each PC . Each staff will need their own . --> Put the database for the ordering system on any of the computers . --> Easy to set up . No extra machine to maintain . 2) Client-Server --> Connect all devices (i . e . printers, copiers) to the server . Connect the internet to the server . --> OPTIONAL: Run a login system . This means that anyone can log onto any computer . --> Share a folder on the server, and make sure people put the files on the servers for others to grab . --> Put database on the server, for the ordering system . --> Higher power bill . --> Don't have to worry about turning computers on and off . --> Other PC's not bogged down with hassles . That's a pretty breif rundown . This Windows 95 machine, what are it's specs and what do you use it for? Because of it's limited networking capabilities, it is best to use peer-to-peer with Windows 95 . If you want more info, you can email me at apgnrussia [at] hotmail [dot] com (in profile) . Hope that helps .	Growly (6)
253487	2004-07-19 06:09:00	Wow - there's a lot to take in there . Answers to the questions at the top are: 1) Internet connection: IHUG satellite card in Win2K PC (dial-up modem for outwards connection) . Not shared, as I've been too chicken to play with Internet Sharing settings . Other XP PCs use their own 56K modems . Win95 PC doesn't need Internet . 2) Security: Want to keep finance info on network private, and would prefer to have business e-mails private as well . 3) Performance: (see 5, below) . Speed for copying between PCs is generally okay - gets slow when transferring 189MB Outlook PST file . 4) Email: Currently sharing Outlook PST (main copy on Win2K PC) via a Windows Briefcase (in Shared Docs on WinXP machine) . PST is available to all user-logins (not ideal) . We have enough domain e-mail addresses available to set up individual ones for all staff . However need some way to retain copies of staff e-mails when they are quoting work . (Using BCC to copy message back to us has been suggested) . 5) Physical layout: Win2K and WinXP PCs separated by 70m . Amazingly, Cat5 cable and 10/100 Ethernet handles this distance okay except when it is hot and windy . Performance can be slow transferring large volumes of data . 6) Shared devices: Networked laser printer on Win2K PC .	LynH (669)
253488	2004-07-19 08:43:00	Realistically if you want to get the best productivity out of your office pc's you need to get a server. Peer to peer networking with everyone sharing files and folders and all using the same email pst is a recipe for disaster. I would suggest a cheap file server running MS Small Business Server as it comes with ISA, SQL, Exchange (which is damn handy for managing multiple email addresses and mailboxes) etc. Set up a firewall on the server to protect your network, put a suitable backup device in the server (DVD or tape whichever your budget/tastes prefer) put your shared files (ie documents, accounting data etc) on the server, put the hub by the server, plug everyone into it and leave it running 24/7. Then everyone can share the resources located on the server, everyone can use their own harddrives to store private stuff and everyone's email can be split and delivered to the correct recipient. Servers are dead cheap these days and there is really no reason not to use one. It makes sharing info that much easier, coz everyone knows where to find it, rather than searching for the pc it might be on only to find that person hasn't booted up yet. Ethernet and CAT5 has a range of about 100m but can be boosted by adding a hub or switch along the cable length to boost the signal. :-)	Sb0h (3744)
253489	2004-07-19 08:58:00	Well, to add to the above: 1) Internet connection: You could leave it as it is and share it, or plug it all (modem and card) into a server, then share it. 2) When you say other's use their own modems, do they use their own accounts? I'm sure that would cost a bit of money.... 3) Performance: as for the wind and heat, the only things you could do to stop that are probably keep it cool and sheltered. (Is it outside?!). Higher grade cables (i.e. Cat 6) are designed to handle worst conditions. The only draw back to transferring large files the way you do now is security. If a server were to have these files (and you constantly update them), then it would be a bit faster to do this because there aren't so many processes hindering it (again, this is variable.) One thing I can suggest to speed this process is to , on the server, set up an FTP server that can copy the files. This, in my experience, has been miles faster than going through the windows system. 4) In terms of physical layout, it would be a lot less hassle if you could control al the network related things from one point - hence a server. 5) The last benefit I'll mention is that of security- If you run a Windows Server (NT, 2000, 2003) , you can set up a "Domain Controller". This basically means that the server will create user accounts, and will store user information on the server - in a central location. Things like addresses, emails and phone numbers of employees can be kept here. Subsquently the employees can use this one account to log on to any of the computers - and maintain the same setting each time. You can, with this account, limit access to folders, printers, the internet.... The security advantages are tremendous. However, in the end of the day, the choice is yours.	Growly (6)
253490	2004-07-19 10:09:00	One point about small networks that is often over looked is the cabling - I would suggest getting a cabling professional to install structured cabling so that it looks professional and that cables are out of sight! A good option for a small LAN is to use Linux with SAMBA server for your file server. This can easily be set up to act as a internet gateway too. No licence costs! There are a number of people on this site who know how to do this - in my spare time I look after a school with 7 workstations using Linux as the server and XP on the desktops.	JohnD (509)
253491	2004-07-19 10:26:00	I agree, structured cabling is good . If you don't want a pro to do it, you can do a pretty good board with runners around the room . Linux is a good idea - but if you are not confident then the upkeep may prove a hassle . Although it is extremely fast (just use FTP, not Samba) - it doesn't provide the login feature . Remember, trial 2003 still available for download - you can make your mind up later on after you see the benefits .	Growly (6)
253492	2004-07-19 10:37:00	>Linux is a good idea - but if you are not confident then the upkeep may prove a hassle. Although it is extremely fast (just use FTP, not Samba) - it doesn't provide the login feature. Not really sure what you are saying here Growly? Why use FTP when SAMBA makes the Linux server act almost exacly as a 2000 server with all the features you want - Windows domain login with centralized login control, ....	JohnD (509)
253493	2004-07-19 10:46:00	Samba is a Domain Controller?!?! No one told me this!!!!!!! Ive always known SAMBA to be the file sharing server for linux, using the SMB protocol that Windows uses - that's why I suggested FTP, as it's faster . Got any definitive articles for me? :p	Growly (6)
1 2