Given a DC environment where very few (1-3) hosts actually need to be discovered via browsing is there a good way to limit what is browseable? I'm thinking of something like a read-only WINS - where WINS provides only those servers that need be contacted and doesn't allow client registrations. Such as a wins.dat that only contains the following: =======================================VERSION 1 0 "MYDOMAIN#1e" 1325615798 0.0.0.0 e4R "MYDOMAIN#1c" 1325572378 192.168.1.4 e4R "FILESERVER#00" 1325615798 192.168.1.6 64R "FILESERVER#20" 1325615798 192.168.1.6 64R "MYDOMAIN#00" 1325615798 0.0.0.0 e4R "DOMCONTROL#20" 1325572378 192.168.1.4 66R "DOMCONTROL#00" 1325572378 192.168.1.4 66R "DOMCONTROL#03" 1325572378 192.168.1.4 66R "MYDOMAIN#1b" 1325572378 192.168.1.4 64R "FILESERVER#03" 1325615798 192.168.1.6 64R ======================================= With a p-p node type clients can browse for the needed info as shown above but wouldn't see all of the other client systems in the browse list. Unfortunately the wins.dat file will not maintain a read only status and all of the clients will end up getting registered (and in the browse list). Am I missing something? Thanks, Chris
From: Chris Smith <smb_77 at chrissmith.org> Date: Mon, 2 Jan 2012 14:29:43 -0500> Given a DC environment where very few (1-3) hosts actually need to be > discovered via browsing is there a good way to limit what is > browseable?To set "browse list = no" solves your issue? --- TAKAHASHI Motonobu <monyo at samba.gr.jp>
On Tue, Jan 3, 2012 at 11:59 AM, TAKAHASHI Motonobu <monyo at monyo.com> wrote:> To set "browse list = no" solves your issue?I think that may do what I want. Just need to make sure that the Domain Controller can be discovered by the clients. Thanks!