Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

How to block msn live messenger

Jun 14 07 4:29 pm

Hi,

which port should i block..my blocking for msn messenger doesnt work for msn live messenger anymore..have they changed the port number or are they using port 80??

there are so many palces which i can set banlist /policies..which one should i use??

i see them in ENS,under www proxy,under user(system policies)...which will be processed first?

Thanks

Jun 14 07 9:03 pm

which port should i block..my blocking for msn messenger doesnt work for msn live messenger anymore..have they changed the port number or are they using port 80??


As far as I am aware, when passing through port 80 (usually via WWW Proxy Server) it will try to connect to an HTTP URL Containing Gateway.dll - And when it is using the NAT or WinGate Internet Client (WGIC) conneciton method it will connect to Server Port 1863.


there are so many palces which i can set banlist /policies..which one should i use?? i see them in ENS,under www proxy,under user(system policies)...which will be processed first?


To begin with you need to decide what connection methods you are going to have available on your LAN. And remember that depending on how many you have will result in how much you need to configure.

Proxy connection method = WWW Proxy Server policies.
NAT connection method = Extended Networking Service policies.
WGIC connection method = Winsock Redirector Service policies.


And you can either use the Ban List or the Policies. So for example if you only have the WWW Proxy Connection method available, and the "Everyone" group currently has no restrictions, User may be unknown and the Default Rights = Are Ignored - then you could do the following.



Image

Jun 14 07 10:04 pm

we are accessing website via www proxy...i just created a test group and set it to block a test port..every thing works for this group but we cant access mail.yahoo.com and www.gmail.com the rest of the sites are ok..and i nv block this 2 sites..

from the system messgae of wingate,it shows authenticationn fail for the machine...the machine is already in the assume list ,can surf internet but the two above mention site..Thanks

Jun 15 07 3:44 pm

jlpk007 wrote:we are accessing website via www proxy... 8<---but we cant access mail.yahoo.com and www.gmail.com..8<--- Thanks


Wonder if this could be HTTPS traffic being denied in the WWW Proxy?

In the WWW proxy service --> HTTPS field add port 443 and report back if it helps.

Jun 18 07 11:29 pm

Nev wrote:
jlpk007 wrote:we are accessing website via www proxy... 8<---but we cant access mail.yahoo.com and www.gmail.com..8<--- Thanks


Wonder if this could be HTTPS traffic being denied in the WWW Proxy?

In the WWW proxy service --> HTTPS field add port 443 and report back if it helps.

thanks for your help..now it works.
I have another problem.

I have a list of DHCP user(ip range (192.168.0.100-119) )which is being assumed as "DHCP USER" GROUP.I block msn access for this particular group.
Certain user from DHCP pool need to access msn ,how do i assume them under another group instead of "DHCP USER" GROUP.
I tried assuming this particular via machine name but it doesnt work.Pls advise thanks

Jun 19 07 2:38 pm

Hi,

You could add these users to a new group and create a new policy action for that group giving unrestricted access. WinGate always uses the least restrictive policy so the users that are in the unrestricted group will not have their access denied.

Matt

Jun 20 07 4:22 pm

MattP wrote:Hi,

You could add these users to a new group and create a new policy action for that group giving unrestricted access. WinGate always uses the least restrictive policy so the users that are in the unrestricted group will not have their access denied.

Matt


i notice the assumd by pc name doesnt work..
this group of using are using dynamic ip and not fix..so i cant create another group base on IP...how do i assumed by machine??
i tried machinename.domain and machine ,both doesnt work.
Thanks

Jun 22 07 9:42 pm

The computer name and mac address assumptions require that WinGate is the DHCP server for your client computers. If WinGate is not the DHCP server for your network, then it will not know these details.

Jun 23 07 5:12 am

thanks for the clarification...my wingate is not the dhcp server....
Post a reply