Re: Segregating networks VLANs or Subnets

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



If you prevent users from a specific subnet from even accessing your
network, you can leave NTFS permissions alone. 99% of admins out their don't
configure groups correctly. I doubt most could also get NTFS permissions
right. If you prevent the clients in the building access to each others
networks, you don't have to change any permissions. There is no need to NAT,
the firewall can route just as well. NAT is a feature of a firewall, not a
firewall in itself.


"Phillip Windell" <@.> wrote in message
news:eE7iUX3%23FHA.3568@xxxxxxxxxxxxxxxxxxxxxxx
> "Tonton" <Tonton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:0F25BDB6-0613-439A-BE85-CCE171321C0F@xxxxxxxxxxxxxxxx
> > Our company has about 4 PCs. But we are providing Internet access to a
> > number of other companies with their PCs. At present everyone can see
> > everyone else's files/folders which is not a good security practise. I
> want
> > to make sure that nobody can see anybody else's files/folders.
>
> You use NTFS permissions. That is what they are for. That is the first
area
> of security. You can't allow filesystem access to the "Everyone Group" and
> complain that everyone can see all the files. So that is the first thing
you
> do.
>
> Do *not* consider the fact the something shows in Network Places as having
> "access". Just because is appears on the Browse List (Network Places) does
> not make it accessable.
>
> Running ACLs on a LAN Router would work for only Layer3&4 traffic.
> Tradditional firewalls do NAT which is not appropriate. You want to
control
> traffic access, not "translate" it. That is why LAN Routers have had ACLs
> long before anyone invented NAT Firewalls. But LAN Routers only restrict
> between Network Segments for the most part,...they are not for creating
> detailed Access Schemes,...that is what the NTFS Permissions are for.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/ISA2004_AccessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
> http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
>
> Deployment Guidelines for ISA Server 2004 Enterprise Edition
>
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
> -----------------------------------------------------
>
>
>


.



Relevant Pages

  • Re: Data Access.
    ... Firewalls or other network gyrations are not the way to solve this problem. ... that includes shared folders with proper NTFS permissions. ... the firewall close port of all share resources. ... > But when share a resource, i need that only one interface can connect> to ...
    (microsoft.public.windows.server.security)
  • RE: can ping but not browse
    ... I have stopped the firewall. ... # are safed from all (security) hazards. ... firewall/bastion host to the internet ... # internet and to an internal network, ...
    (Fedora)
  • Re: Turn off all sharing and network discovery
    ... which is basically Windows XP running as a virtual ... It does need its own AV and firewall. ... unnecessary network resource sharing and resource discovery. ...
    (microsoft.public.windowsxp.general)
  • Re: Turn off all sharing and network discovery
    ... which is basically Windows XP running as a virtual ... It does need its own AV and firewall. ... unnecessary network resource sharing and resource discovery. ...
    (microsoft.public.windowsxp.general)
  • Re: Why not use NETBEUI on Windows XP ??
    ... Trusted zones means that firewall rules will be bypassed for any or certain ... not count on netbeui being a defense for such as long as smb connectivity ... while the connection is open. ... > Microsoft Networking components on my network. ...
    (microsoft.public.win2000.networking)