LICENCING QUESTION...

[mcit]

Can someone tell me, as far as I ca deduct, the way the licencing for wingate works is that each connection through the wingate server must have it's own licence. This goes for outgoing connections [from the internal network to the internet] but it appears that incoming [from the internet to the local network] also count as a licence. Therefore if you have a 6 user licence, and have 5 simultaneous internal connections, and you wish to map ports for file sharing or remote control applications, then you are going to run into problems once that last licenced connection is used.

Is this correct? and if so, should it not be that only OUTGOING connections should be licenced?

If I should happen to have this all wrong, then can someone tell me why with a 6 user licence I can map ports, but have problems getting connections through them, whereas when I revert to the trial version of wingate [unlimited users] the problem appears to vanish?

This issue is occuring on wingate 5.2.3.

[adrien]

Hi

We count any connection from anywhere as a user. Each user then needs a license. Some types of sessions we don't count, but these are only Remote Control (GateKeeper), WGIC control sessions, and DNS sessions.

So yes, if you are running a server, and you have lots of people connecting in, then they will consume license counts as well.

Furthermore, if you have many local concurrent users, you could be blocking some of these inbound connections.

So basically when you provision the system, you need to not only consider internal users connecting out, but external users connecting in as well.

Adrien