11 replies
by erickdrny Accepted solution
by pthompson Accepted solution
by rajagopalan.durairajan Accepted solution
Options provided by Thompson would really work !
Simple firewall on the 2000 server would be good to restrict the individual/group of computers ( based on their IP's ) accessing .
For website restrictions , you can consider gateway's / firewalls with web / content filtering options !
by erickdrny Accepted solution
by rajagopalan.durairajan Accepted solution
Hey forgot to mention , Simple firewall on the 2000 server ( this would be a software based firewall , free version of Sygate would be good ) ;
Just wanted to make it clear!
Have good one!
by pthompson Accepted solution
by dumphrey Accepted solution
some good linux freeBSD based software firewalls that install on pretty much any old hardware you have laying arround. A 486 with 128 MB ram and 2 nics will be more then enough to run a SOHO network.
http://www.pfsense.com/
http://www.ipcop.org/
http://smoothwall.org/
http://m0n0.ch/wall/
Are the biggies I know about. Any of the 3 will provide all you need at the cost of some old hardware.
Another solution is to dig around for a pre-built embedded platform and install one of the above on it (Sokris or WRAP are the 2 that pop to mind).
by greybeard770 Accepted solution
Since you only want to block certain computers you need to start with something like
IPCONFIG /SETCLASSID=NOINTERNET
that corresponds to DHCP settings for everyone using that computer. After that, if all nodes are on the same subnet, you can leave the Default Gateway value blank. You might also direct them to a DNS server that only knows local addresses and does not forward.
There is also a registry entry to set the TTL to a value that would not be enough hops to get out of your building.
If there is a domain you want to keep everybody out of, you can claim to be the SOA in your own DNS for that domain.
Obviously, none of these options are perfect and the hackers will figure a way around them if given time. Some options even make the statement to employees that "We don't trust you." And if you can't trust people, maybe they should not be working with equipment that can be misused.
by dumphrey Accepted solution
by greybeard770 Accepted solution
We have SOA (Standard Primary) DNS entries in addition to the normal Active Directory domain for things like spywarebuddy.com and adbuddy.com that have no entries. That way when email or web pages would direct people to those sites it gets a Page Not Found error which we prefer to loading more spyware. You could of course add badgirlspretendingtobegoodgirls.com or whatever you are trying to protect your people from.
We also use the /SETCLASSID option to grant longer leases for desktops and shorter ones for laptops. http://support.microsoft.com/kb/240247 is a good place to start for more on that subject.
by jose.gouveia Accepted solution
Erick .. if you have the users login on to your Domain .. you can deploy some customize scripts with IPCONFIG /SETCLASSID=NOINTERNET
in it! Still, I would use a Firewall to keep my mind in peace!
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending