sns-emea
asked on
How to block a website from ISA 2006
Even after adding the link for e.g. http://www.youtube.com/* in URL Sets - Block Website, the user still can access it. It works for some days and then all of a sudden all of my users can access it and then again it blocks by itself. What could be the reason ?
what rule do You have for this url set?
ASKER
I have a policy called Internet in this policy Action is Allow from Internal to External and under exceptions Block Website (URL) is there.
why don't You try explicit deny rule for this url set?
ASKER
how ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The simplest thing to do is create a Domain Name Set (not a URL Set) with names like *.evilsite.com and add it to the Exceptions Box in the TO Tab of the HTTP/HTTPS Rule you are already using.
No need to create any new Rules. Simple,...clean,...efficie nt.
No need to create any new Rules. Simple,...clean,...efficie
nslookup returns these IP address for www.youtube.com
213.139.49.83
213.139.49.90
213.139.49.84
213.139.49.86
213.139.49.80
213.139.49.89
213.139.49.87
adding these ip addresses to computer set and put it in exception list in the rule would return better performance than adding domain name set.
ISA/TMG performs reverse DNS lookups on the IP address to determine whether the IP address matches any of the blocked domain names. Reverse DNS lookups are expensive and often fail or lead to delays.
213.139.49.83
213.139.49.90
213.139.49.84
213.139.49.86
213.139.49.80
213.139.49.89
213.139.49.87
adding these ip addresses to computer set and put it in exception list in the rule would return better performance than adding domain name set.
ISA/TMG performs reverse DNS lookups on the IP address to determine whether the IP address matches any of the blocked domain names. Reverse DNS lookups are expensive and often fail or lead to delays.
Could just use a Domain Name Set that includes *.youtube.com
with IP#s I've had more dependable results with an Addrress Set rather than a Computer Set,...not sure why,..but it is what I have experienced.
with IP#s I've had more dependable results with an Addrress Set rather than a Computer Set,...not sure why,..but it is what I have experienced.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was my mistake :)