Managing Users and Groups
Additional users and groups can only be administered in WinGate 2.1 Pro.
WinGate 2.1 Lite does not allow addition or deletion of User or Group records.
WinGate can log individual user data. To do this you must create individual
users, and set their access rights. This process is very similar to user
administration in Windows NT.
When WinGate is first installed, or if the user database is lost, WinGate will
create a basic database with the built-in users and groups.
Administrator
This user can not be deleted. When WinGate is installed the Administrator
account has no password, but they must set a password immediately. Initial administration can only be done on the WinGate machine. This user has full control over all WinGate functions. Qbik recommend that
this account is only used for an initial setup, and as a backup account for the
system administrator.
Guest
The guest account has no default password and cannot be deleted. Guest is the
account that all unknown users access by default. You can give any rights to
the Guest user, but by default, users with Guest privileges only have rights to
access services, but no configuration rights.
User assumptions
These are an easy way to log user activity without requiring users to
authenticate with WinGate. You can set up assumptions based on machine name or IP
number, so when a user connects from a known computer, they are assumed to be a
given user.
It is not mandatory to add further users. For small WinGate installations, you
may decide that no one needs to be tracked individually.
Some considerations
You have the options to implement any of these policies plus many more at your
discretion:
Setting up individual users or groups is so simple that most people with this
feature will choose to do so.
Remember these points:
Allow administration only on WinGate machine, or predetermined machines
Require authentication or not
Have separate accounts for all administrators
Require authentication, but have shared user accounts (eg per class, see below)
Accounting to monitor access levels
Groups per company division
Accounting per person
allow guest access or not
If someone is accessing WinGate services from an unknown location (i.e. no
location entry) without authenticating, they will be user Guest
You can set rules per group, so make use of groups as they save you set up time
Individual WinGate Users can belong to several Groups
Accounting does not have to be enforced (i.e. charged), but it is useful to
see who uses the Internet the most. You can also stipulate that someone A shared user account is very useful. Setting up one or more user accounts
that can be used by different people is a way of tracking the usage of a group.
This is most likely to be used in schools, where a whole class can use one user
account (e.g. Room4). A tutor can have an individual account, but be in the same
group and an Admin group. This way you can monitor the group usage and won Assumptions can save people logging in. If certain machines are only ever used
by one person, then give them an assumption and they won If you setup your bindings in a secure way, your network can