How to set up a local network with Internet access, with Win 7 as a server?

Question

Computer networks

Gentlemen, good time to all!
There are N number of computers with different operating systems from win xp home basic to win 8.1 with a license for educational institutions, there is a network, but everything was done by someone like me, i.e. all through the 5th point. A typical beam network with a “server” on win xp home, also on some machines there is some kind of code called traffic inspector (for which I still don’t understand) everything works for now, but it needs to be better, more specifically, account control is needed , distribution of roles, etc. If there was a Win Server, everything would be easier, but it is not there, and I poked around with it for a long time and stubbornly, and then only once. (ubuntu\debian will not work because of my curvature).
Comrades experts, attention to the question!
Is it possible to implement all this using Win 7?
PS Due to the fact that my knowledge is limited mainly to connecting printers and scanners, I would be grateful for good links on this and all related issues, I understand that Google is cool, but it mostly gives garbage.

Answer 1

A traffic inspector is needed to limit the output speed to the Internet for each client.
Having windows7, you can raise a nat server, but it will not allow you to control the ip addresses of clients, the speed of Internet access, and generally do some meaningful actions. Everything will "just work" without being fine-tuned.
It is configured in the "Network Control Center" - change the adapter settings - pkm on a network connection that leads to the local network - properties - access - allow other users to use the Internet connection of this computer.
After that, this network interface will be assigned a static address, and it will start distributing ip addresses automatically. It remains only on all client machines to set up automatic receipt of an ip address.

Answer 2

Concerning uchetok - it is possible to create network storage with limited access on the server. To do this, we create a bunch of users on the server and network folders. For network folders - right click - properties - security - change - add, set permissions for folders to warn the user from doing so. We mount the server to the workstations as a network drive, and as a result, each student accesses the network drive, sees all the folders, but can only enter his own by entering his login password.

Answer 3

Well, the last thing - on each workstation, we create a password-free, local student user, and cut his rights to the very tomatoes and the admin user - with admin rights. In Windows, the widest possibilities of prohibitions / permissions for the user, which are available through the registry, up to a white list of allowed programs and actions. More details can be found in Google or in the book "Windows 7 Secrets for Professionals".
Well, in conclusion - all of the above, these are wild crutches that are fenced in many educational institutions, due to lack of qualifications and time. It's far from the best way, damn labor intensive to maintain and deploy, but it works. If you still go this way, then you should think about learning wshell, cmd and powershell, because in the conditions of such working groups, even such a routine operation as creating a new shortcut on the desktop will result in a living hell without automation.

Answer 4

Raise a domain on samba, it will be VERY difficult for you, but a good experience. It is better to do it first on virtual machines. Then screw on Squid.
NB! if you will use win7 as a "server" do not forget about the limit of the number of connections (20) via SMB.