setting up a network in an office.. need help?

Question

Ok my office ordered a few new desktop to replace some really crappy computers. All the new computers have windows XP pro on them. My question is what is the best way to set up a network?

This is how it works here.. there is a server that holds all the offices data. All the computers have to be connected to that server but not necessarily to each other. Once logged in to any network computer the person should be able to access the server without typing in any username/password.

However, I need to set it up so that users can access the server from a remote address (home for example), yet if they do so it should require a username/password.

I'm not sure how the internet is currently set up, but would this require a static IP address? (I think we already have this).

Also, i've always wondered this.. what is the difference between "WORKGROUP" and "DOMAIN" .

Appreciate any advice.. thanks.

Sorry I problem made my question sound like I am computer-illiterate, but I have set up networks before and am just a little unfamiliar with domain networking. I set up home networks all the time but just wanted a few tips on domain networking for making it secure. Basically I just need the server to be secure so that no one not in the office can access it.

Answer 1

Look this is not a easy job & it can't be done by a novice. From your letter I could understand that the network technique you asked for was for Domain based net working not work group.

Answer 2

I really have to agree with jbgood. Very, very hard to answer your question accurately here.
When you say "server", do you really mean a server (with a server operating system) or just a workstation you use as/call a server? There is a huge difference.
You have two options; workgroup and domain. A workgroup is easier to set up, but much less functional. A domain is much more difficult to set up, but... sheez... gives you a world of options.
WORKGROUP: Internally, this would work like any home network (assuming you have less than 10 computers on-site). You can run the XP wizard, or do it manually (you said you have some experience), to set up a standard, run of the mill small network. Externally, you'd need a static IP address and a router that supports VPN connections (access and authentication). You then configure the router with authentication/access restrictions (typically username/password). It would also need to issue DHCP addresses. Anyone inside the network would be able to access shared files/printers as with any simple network. Anyone outside would first have to authenticate against the router to establish the VPN. Once the VPN is established, they could access shared files on the server just as if they were there locally.
DOMAIN: This is beyond your skill, unless you're willing to take some time, sit down with the book and do it step by step. Your only rational choice is Small Business Server 2003. It has huge advantages.
1. Active Directory to authenticate users, apply security policies, group polices, share files, etc.
2. Routing and remote access to handle authentication, remote access, etc. (You can use a "dumb" router)
3. Remote Web Workplace. Users can remotely access your server without VPN. Using a web browser, they go to the RWW website, enter their username/password, and then access your server or other computers. MUCH simpler than VPN.
4. The setup is wizard driven, with to-do lists, etc. making setup for the novice a lot easier. (Us "old pros" hate the wizards, but hey, it actually works).
There are scores of other features, but these are key to your question.

QUICK AND DANGEROUS: You can also use port forwarding on the router to forward TCP port 3389 to your "server's" internal IP address. Anyone using remote desktop would "remote" to your public static IP address. This would redirect remote desktop to the server. Assuming you have username/password login requirements on the server, they could access the server remotely without VPN. However, this opens up a huge security hole for anyone with some hacking skill, and only one user at a time could access the server remotely. This is possible, but not recommended. (Kind of like getting down the mountain by jumping off a cliff. It will get you there quickly, but....)

Answer 3

No chance this can be answered effectively here. You absolutely need a network professional on-site to handle your this install. Attempting this kind of work based on answers you found on Yahoo is a guaranteed disaster.

Sorry, tell your boss to open up his checkbook again.