Re: Controlling internet access...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"Homer J. Simpson" <root@xxxxxxxxx> wrote in message
news:uISEuT5gHHA.4704@xxxxxxxxxxxxxxxxxxxxxxx
The Filters block by IP(s) on a schedule, URL, MAC or Domain.
The Firewall will Allow/Deny by Source/Destination, IP Range, Protocol
and Port Range on a schedule.

This pretty much confirms what I was saying. There is only one PC in
that
household. The filtering needs to be done with respect to the Windows
user.

Nobody, huh?

The folks who are trying to control this are now telling it'd be perfectly
acceptable if this one user has his internet access blocked entirely.
Other
accounts must remain untouched however.

I suppose removing that user's access to Internet Explorer would do
it--but
obviously, just deleting any shortcut pointing to iexplore.exe is not
foolproof enough.



If you require no networking capabilities at all (assuming this is just a
stand-along machine) you could release the IP or just disable the NIC. In
both cases your extra users would have to have "user" permissions not
administrator. Other than that I think you'll have to start looking into
third party alternatives.



.

Relevant Pages

  • Re: Controlling internet access...
    ... The Firewall will Allow/Deny by Source/Destination, IP Range, Protocol ... and Port Range on a schedule. ... This pretty much confirms what I was saying. ...
    (microsoft.public.windowsxp.general)
  • Re: Controlling internet access...
    ... The Firewall will Allow/Deny by Source/Destination, IP Range, Protocol and ... Port Range on a schedule. ... This pretty much confirms what I was saying. ...
    (microsoft.public.windowsxp.general)
  • Re: Allow Wimba Live Classroom via ISA 2004 on SBS 2003
    ... Maybe I can get it to work by defining the custom protocol with primary UDP ... If not a custom access rule, to what rule do I attach the custom protocol? ... Port Range From: 5998 To: 5998. ...
    (microsoft.public.windows.server.sbs)
  • Re: PC Anywhere Outbound
    ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
    (microsoft.public.isa.clients)
  • Re: PC Anywhere Outbound
    ... > I have created a protocol in the Toolbox with the following information: ... Port Range = 5631-5632 ... Direction = Outbound ... > SECONDARY CONNECTIONS ...
    (microsoft.public.isaserver)