Bug in ENS Policies: BAN LIST ?

[jacksnyderc]

Wingate 5.2.3
Windows 2000 Server

How do I get the "Ban List" to work in ENS Policies ?? Banning
some sites by servername does not work as it seems to have
been intended?

The "Advanced" tab where I have only allowed by request type
seems to work fine (serverport = 80, 25, 110, 443). Yahoo messenger
(latest version) uses port 25 also, so I am attempting to block traffic
by servername in the Ban List, but with no joy.



I have read all the posts in this forum, saw some folks having
problems with the same.

Can Qbik confirm if this is a known bug?


Thanks in advance,
Jack Snyder

[MattP]

Hi Jack,

We haven't seen any bugs with policies. Can you detail how you setup the bans? Did you make sure you changed default policies to are ignored?

With the beta version which is currently available you can control the applications that the WinGate Internet Clients are permitted to use, so if you want to ban an application you could consider this as an option.

Regards,

Matt

[jacksnyderc]

Using ENS with trasparent redirection:

and Default Rights(system policies) : are ignored
-------------------------------------------------------
Created the policies for ENS as follows:

Added in Ban List tab:
This criterion is met if : servername contains "gator"

Under Advanced tab:
Specify which rights recipient has rights for is checked,
and have created different filters, each filter having a
single criteria for type of request (eg. http, https, ftp, etc)

-------------------------------------------------------

Whereas policies based on request types are working properly,
the ban list policies are not, am confused..

regards,
Jack

[Nev]

Using ENS with trasparent redirection:

and Default Rights(system policies) : are ignored
-------------------------------------------------------
Created the policies for ENS as follows:

Added in Ban List tab:
This criterion is met if : servername contains "gator"

Under Advanced tab:
Specify which rights recipient has rights for is checked,
and have created different filters, each filter having a
single criteria for type of request (eg. http, https, ftp, etc)

-------------------------------------------------------

Whereas policies based on request types are working properly,
the ban list policies are not, am confused..

regards,
Jack

Hi Jack,

Have several jobs that wish to deny staff access to certain web resources, majorly 'messenger' type processes and web mail for example.

I don't use policies as you do, but the following is the most streamlined and always deny's access afaict.

Apply a system policy that users must be at least assumed.
Apply a system policy and ban list for example 'xyz' to be banned.

In all services apply 'Must also be granted' from the global system policy works really well, nothing with 'xyz' will be granted.

The beauty of the System policy is that it's easy to implement in a service with the front pull down box.

However this may not suit your needs with specific access rights for users.

Cheers,
Nev.

[adrien]

Hi

When the ENS reports connections to the WinGate engine it only reports IP addresses (not server names).

So you would need to ban servers by their IP address rather than their name, since WinGate cannot guarantee that a reverse name lookup would work (or be available due to inconsistencies in DNS configuration on the internet).

In your case this would require you to look up the range of IP addresses used by gator.com and then block those.

Adrien

[jacksnyderc]

Adrien, that is true, I hope this gets fixed in the
next release, otherwise it will remain a source of
confusion for new users. Thanks.

Nev., I will take up your sugesstions.. as soon as
things get more complicated in my organization.
Thanks!

Jack