Why waist a bunch of time an effort doing something that doesn't matter
anyway? "Seeing" things on a network is meaningless,...accessing things on
the network is what matters. What is "seen" is determined by what is listed
in a compiled Browse List on a Domain Master Browser,...what is accessed is
controlled by File System Permissions in the form of Share Permissions and
NTFS Permissions,..and by Application permissions such as with things like
SQL Server, Exchange Server, etc. The permissions is where you need to
concentrate your efforts.
Even if you stopped them from "seeing" things, they can still access them if
the permissions let them. "Seeing" things in Network Places is not a
prerequisite for accessing resources. Network Places is just "eye candy"
and a convienience.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Maki" <(E-Mail Removed)> wrote in message
news:6C7FEB65-E621-418A-8E63-(E-Mail Removed)...
> Hello!
> Hope somebody can help me out.
> I've just setup a basic network. Single 2003 server domain controller,
with
> 10 machines attached to it. I've got control over DHCP,DNS,
everything...no
> wins running
> Point is, im trying to prevent users from seeing things through entire
> network (seeing other clients, servers) etc. I do not want to go to every
> computer and disable netbios over tcp, and i've already tried the 001
> microsoft thing in scope options with a value 002, but without success...
> Is there anyway i can prevent clients from seeing each other through
network
> neighbourhood (and seeing the network), by applying some setting from the
> server itself?
>