Since there's only a couple of server systems on the network that
actually need name resolution or to be seen via NetBIOS browsing. Is
there any reason not to run a static only WINS server with just the
information for those systems listed? If not, then how can one stop
the other systems from
If your windows clients use login scripts to map drives, then they don't
need WINS at all, since they resolve hosts via DNS.
However, if a client isn't using wins it will still use netbios
browser to locate resource on the network.I am not sure if you can
totally defeat this by pointing
On Tue, Dec 18, 2012 at 2:08 PM, Gaiseric Vandal
gaiseric.van...@gmail.com wrote:
If your windows clients use login scripts to map drives, then they don't
need WINS at all, since they resolve hosts via DNS.
I think that WINS is necessary for the clients to find the Domain Controller.
However,
On Tue, 2012-12-18 at 15:14 -0500, Chris Smith wrote:
On Tue, Dec 18, 2012 at 2:08 PM, Gaiseric Vandal
gaiseric.van...@gmail.com wrote:
If your windows clients use login scripts to map drives, then they don't
need WINS at all, since they resolve hosts via DNS.
I think that WINS is necessary
I'm not referring to Active Directory, the Domain Controller is a Samba 3 box.
On Tue, Dec 18, 2012 at 4:24 PM, Adam Tauno Williams
awill...@whitemice.org wrote:
??? With Active Directory I'm pretty sure that happens via a DNS query
(or series of them).
--
To unsubscribe from this list go to
