All computers get included in browse lists...

Post #135,616

1/14/04 7:04:15 AM

...and no, you can't restrict where a share gets advertised to. Sorry.

Post #135,643

by deSitter

1/14/04 9:19:03 AM

Seen with own eyes

Company had a large complex domain structure for NT 4 network. Workstations all (clone) installed with a "DATA" share by accident. Getting a net neighborhood to pop up took forever - the data shares were all removed (SMS script) and browsing went to normal.

Yes, you'll always all computers in a browse list, but that is a different matter (WINS). To see what I am talking about, try to connect to a printer on some remote domain to which you can authenticate. After a couple of seconds of thinking, you'll see a list of only those computers that have advertised printers. WINS will trade its list of machines with other WINS servers, but advertised shares stop at the domain unless otherwise instructed (at the "domain master browser"). This is called "m-mode" resolution - the local domain controller is asked about remote shares instead of contacting the remote controller on the domain where the share lives - that is, leave it up to local WINS and the domain trusts. Basically, NetBIOS name resolution is a complex disaster because unless you explicity tell all the machines how to behave, they all shout at each other constantly.

NetBIOS is not routable but NBT is, because it is encapsulated in IP (we've had this argument before). The issue is WINS, not routability.

-drl

Post #135,680

by pwhysall

1/14/04 11:37:22 AM

1/14/04 11:39:10 AM

You're making it up.

Table 9.1 NetBIOS Node Types

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Node Type	Description
B-node (broadcast)	B-node uses broadcast NetBIOS name queries for name registration and resolution. B-node has two major problems: (1) Broadcasts disturb every node on the network. (2) Routers typically do not forward broadcasts, so only NetBIOS names on the local network can\r\nbe resolved.
P-node (peer_peer)	P-node uses a NetBIOS name server, such as a WINS server, to resolve NetBIOS names. P-node does not use broadcasts; instead, it queries the name server directly.
M-node (mixed)	M-node is a combination of B-node and P-node. By default, an M-node functions as a B-node. If an M-node is unable to resolve a name by broadcast, it queries a NetBIOS name server using\r\nP-node.
H-node (hybrid)	H-node is a combination of P-node and B-node. By default, an H-node functions as a P-node. If an H-node is unable to resolve a name through the NetBIOS name server, it uses a broadcast to resolve the name.

\r\n

\r\nFrom [link|http://www.microsoft.com/mspress/books/sampchap/4245.asp#5|http://www.microsoft...mpchap/4245.asp#5]\r\n

\r\n

\r\nI'm nobody's fool but mine, Ross :)\r\n

Edited by pwhysall Jan. 14, 2004, 11:39:10 AM EST

Expand All History

Post #135,702

by deSitter

1/14/04 1:12:40 PM

1/14/04 1:15:01 PM

OK H mode

It's been a while since the NT 3.51 tests :)

In any case you know what I meant, but thanks for going into C-mode:

C mode: When a forumer's memory has holes, Peter will switch into C-mode or "correction" mode, in which vast amounts of MCSE study bits will be searched for terminology :)

-drl

Edited by deSitter Jan. 14, 2004, 01:15:01 PM EST

Expand All History

Welcome to IWETHEY!