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