Setting up a 5 computer network...(software)

[aggressor]

Hi, thanks for reading and possibly helping me

All the computers are running Win2000, networked through a switch. All the hardware is set up and in working order.

I need it set up like this, but I don't know what the easiest way would be. Right now my only option is by sharing\passwording directories, but I would like it so any user can log on to any 1 computer and set the restrictions correctly. IE one person could use 1 computer, then switch to another computer and have the same exact access\files available just by logging in with a set username and password. Is that possible? If it isn't, how about the regular way each person being assigned their own computer and having to use a login\pass to get into windows, then using passwords and such to enter directories?

There are going to be 2 "admins" who need access to everything, along with 3 other computers who have limited access to certain directories. The admins will have a private directory for admins only, along with 1 public directory, along with 1 private directory per user. First time doing a network setup like this so I am in the dark

 

[pwass]

Ive seen it done before but only using a server and im guessing you dont want to give one of those computers up. it used microsoft netware

 

[TexDotCom]

It sounds like the best thing for you to do would be to have a peer-to-peer network with local accounts for each user on each machine. That, or go with a star type network where there is a server going to the switch, which then goes out to all the other computers. Personally, I would go with the star type.

Regarding the way you currently have it setup, the netware option seems to be the best, but I don't have much experience with that.

Hope this helps at least a little bit.

 

[ktwebb]

Netware is Novells Network Operating System (NOS), currently at V6 I believe. Not dead yet but not breathing to well. As it relates to microsoft, there is a netware network client logon, and MS also has their own version of IPX/SPX, called NWLink. It's been awhile since I had to worry about Novell Netware but it is a completely different entity that Microsoft's Server OS's. Well the lines are blurred actually because Win2000 Active Directory is very similar to Novells Directory structure, Netware Directory Services (NDS). Anyway, just wanted to clarify that. It's not Microsoft's Netware, though they might want to swallow it up eventually.

 

[PELarson]

Your best option would be to setup a Linux server and connect the Win2000 WS to it using Samba.

 

[rearden888]

I would suggest setting up one of the computers as a Win2K server as a PDC, if you have access to that software. Then you can set all the other computers to log in to that domain and use login scripts, user profiles, and policies set up on the server to make sure their desktops and permissions are consistent across the network.

 

[aggressor]

I decided to go with rearden888's way but I don't really know what I'm doing ;D
Is the thing I want called Terminal Services? Is there anywhere I can read up about setting up a domain?

 

[ktwebb]

You have the workstations in place so you don't really need terminal services. If you just wanted thin clients, or dumb terminals as your workstation, diskless computers that use the server's resources predominately then you would install terminal services.

Windows 2000 Terminal services

A simple Windows2000 server would give you what it sounds like you want, a single login authentification for each client PC to access resources across the domain structure and structured desktop resource sharing community for each user. There really isn't a Primary Domain Controller (PDC) or Backup DC in a Windows2000 active directory environment. Each additional server you added would just be added to the Active directory forest. It a little complex to draw out in a forum reply and you really don't have to be a MCSE to run a Windows 2000 server/client network, though it doesn't hurt of course. Then you would use login scripts, policies and profiles, as rearden888 mentioned, to define what each user's desktop looks like and what resources they have rights too.

Understanding Windows2000 policies
Profiles and Group Policies Primer

Login scripts are run when a user logs in. Batch files you write to complete auomated tasks upon intial user login.

What are Login Scripts?

 

[aggressor]

OK, I got a copy of Win2K Serv. I have Active Directory set up, with logins made, etc. I shared some directories, limited access to certain accounts made in Active Directory. It works, directory access to the shared network drives work. Is there anything else I can do? (I know there is ). Is there a way to save profiles (desktop settings, internet cache, etc) on the server side instead of the client? Any other neat things? Did I even do it correctly?

This is my first big networking project, so I don't know much

Also, I realize what I'm doing is very basic, and I wonder if it can it be done with regular Win2K Pro, except with all the logins stored locally per computer instead of on the server?

 

[PELarson]

Just tried it for the first time tonight on my test system. Boiled down.

I created a directory on the server, I called it Profiles, shared it. In the Active Directory Users and Computers, I highlighted my user name and in Properties>Profile add the UNC name(\\myserver\Profiles\pelarson) to the Profile Path. Copied my profile to the server using Control PanelSYstem>User Profile>Copy To. Made sure the type was Roaming. Signed into my laptop and the desktop settings and My Favorites where there, mail data wasn't copied, nor anything in the local settings directory. Desktop shortcuts worked fine except for the programs that aren't installed on a given PC. I could get around that by moving the program shortcuts to the All Users directory on each PC.

 

[anime]

you can make your w2k server machine as a domain controller. With dhcp/wins/dns installed. You can have other clients to log on to your domain by creating custom login script. You as admin can create type of account you want your user to have when they logged on to your domain. It's quite simple actually.