From: W. Alan Robertson (warobertson@xxxxxxxxxxxxx)
Date: Wed May 30 2001 - 20:21:18 GMT-3
Well,
Here I go again, following up my own post... I just found the answer
I was looking for...
If I use:
dlsw icanreach netbios-exclusive
I disable netbios explorers. The assumption is that I will have
corresponding "dlsw icanreach netbios-name servername1" statements,
but I'm pretty sure that if I omit them, it will have the desired
effect.
Here's the link (watch the wrap):
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr
/ibm_r/brprt2/brdlsw.htm#xtocid2671113
Has anyone done this before? Does anyone have a better method for
accomplishing this?
Alan
----- Original Message -----
From: "W. Alan Robertson" <warobertson@earthlink.net>
To: "Groupstudy - CCIELAB" <ccielab@groupstudy.com>
Sent: Wednesday, May 30, 2001 7:00 PM
Subject: DLSW: Allowing all SNA, but Denying all NetBIOS
> Since we've had a flurry of DLSW today (Three posts or so), I
figured
> I'd let one loose as well...
>
> As the topic indicates, I'd like to prevent the exchange of all
> NetBIOS reachability information across the enterprise. What is the
> best way to go about this? I can't seem to find a cure all "dlsw
> disable netbios" command, or anything resembling it. The best my
> peers have been able to come up with is hard coding names as being
> unreachable, preventing explorers. This sounds like a tremendous
pain
> in the a** to me as they will have to constantly keep an eye out for
> new hosts being searched. It sounds like a logistical nightmare to
> me.
>
> I've been pouring through the documentation... Where's the magic
> bullet?
>
> Alan
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:57 GMT-3