On Wed, Mar 5, 2008 at 11:39 AM, Tom Miller <[EMAIL PROTECTED]> wrote: > ... in the main building I'd like to be able to see all PCs in "entire > network".
"Network Neighborhood" and it's decedents are all driven by the NetBIOS browse list. For cross-subnet browsing to work, you pretty much need WINS. WINS is pretty easy to set-up for most smaller networks, so I'd suggest just going that route. (The third-party Samba software has (or had) a feature which would propagate the local browse list to non-local browse masters, in effect registering non-local names by proxy, but that's a kludge at best, and not something I'd recommend.) Since you're not running AD/DNS, I assume you're using NetBIOS for name resolution. If so, I'd strongly recommend WINS anyway -- it will make name NetBIOS registration a lot more reliable. If you combine WINS with setting the NetBIOS node type to "Peer", you should also see a substantial reduction in broadcast traffic. > I know this issue will go away once we migrate to Active > Directory and register PCs in DNS, Even Active Directory doesn't give you browsing in NN. You can browse or search the directory, and that is good enough for most purposes, but AD doesn't appear in NN, so if that's what you want, you're going to need NetBIOS and WINS, even once you have AD deployed. -- Ben ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
