Hey guys - in the context of this thread I have managed to squeeze out the information that for my final interview I'll probably be asked two things, one will be to go through a set of acronyms explaining what they stand for or mean (like IP address, HTML that sort of thing) and the other will be to explain how I would advise in a situtatin where an organisation is moving on from a standalone machine and say they want a network. Now that is a pretty open ended question. I would be aiming to try to cover good practices in the process and thought I would canvas opinions and input here as a way of mulling things over and a kind of "revision". Some things I know already (though they may be open to question or debate):- Start from the budget, expectations, and need. Sharing a printer and internet access via a router seem sommon sense. Consider the effect on budget if software is to be server licensed. A server is surely a very good start point - would a network without one have so much value? Is a samba server a valid option, even if all clients are M$ based? Ensure there is a network chart as part of plan, ports are numbered, a naming standard for machines (some of these considerations in case in future there are other offices or networks interlinked). What sorts of things am I missing or need covering here? All input from the considerable experience out there - but remember this is in a voluntary sector situation and not a commercial one.