Computer Browser Service across multiple subnets

[owaiskt]

I've got around 20 computers spanned across multiple subnets in a network. They all are configured to be a par tof the same workgroup called "Workgroup". All the computers are running windows 2000 profesional.

My issue is that i cannot see the computers from different subnets in Network Neighbour hood, although i can ping across those from anywhere in the network.

I know i have to use computer browser service to achieve the functionality. But the question is how do I do so. The computer browser service is running by default on all the computers.

My questions are is it possible to define the computer role in CBS or is it automatically assigned based on some criteria.

On referring to the document from microsoft for CBS, i came to understand that for every subnet there needs to be a different master browser and i need to have a master browser for the whole work group, but how can these be defined?

Also, as mentioned before, i have different subnets on the network and they are being linked using CISCO C3750's, so can i still work with work groups or do i need to setup domain for this purpose.

I appreciate if anyone can assist me out there.

[sc302 Veteran]

this may help you:

Lmhosts File

NetBIOS name resolution is typically performed through broadcasts, which will resolve names only on the local subnet. To resolve names of computers located on another subnet, the Lmhosts file (located in the directory systemroot\System32\drivers\etc) must be configured. The Lmhosts file must contain a NetBIOS name?to?IP address mapping for all computers that are not on the local subnet.

To implement communication between subnets and the domain master browse server, the administrator must configure the Lmhosts file with the NetBIOS names and IP addresses of all browsers. To ensure that the master browse server for each subnet can access the domain?s PDC, the PDC for each domain must have an entry in the Lmhosts file for each master browse server. Also, each entry must have the tag #DOM, which designates the named computer as a domain controller.

To guarantee that the domain master browse server can request the local browse list from the master browse server of each subnet, the Lmhosts file on the domain master browse server must contain entries for all the potential master browse servers. Thus, the Lmhosts file on the master browse server of each subnet needs to contain the following information:

IP address and NetBIOS name of the domain master browse server

Domain name, preceded by the tags #PRE and #DOM

[+BudMan MVC]

You know I am not sure it will work without a domain.. Normally once you get to the point that you are running multiple segments, you have enough machines where a domain would make sense.

I have to ask -- WTF you have multiple segments for with only 20 machines?? If you want browsing to work - and broadcast name resolution the easiest fix would be to flatten your network. I see little reason for multiple segments with only 20 machines. Are you doing ACL's between the segments? Please tell me your not using soho routers and natting between the segments!!

http://support.microsoft.com/kb/117633

How browsing browsing over a multi-subnet TCP/IP network works in a domain and in a workgroup

Multi-subnet TCP/IP network browsing support is available only in a domain environment

http://networking.nitecruzr.net/2005/08/br...ss-subnets.html

If a workgroup is segmented, there will be no domain (workgroup) master browser, and no ability for servers on one segment to be seen from another segment. Segmented workgroups simply can't be browsed across segment boundaries.

Kind of hard to have a DOMAIN master browser without a domain ;) You could always just run a wins server if you want netbios name resolution across segments, samba will do this and even act as your PDC, etc. so you could get browsing to work ;)

But with only 20 machines - unless you have some security reason you have the machines in different segments, and are actually using ACL's between segments, etc. I would just flatten your network out. Now if you had 200 machines or 2000 multiple segments might come in handy but with 20.. Not really unless done for security reasons.

[+BudMan MVC]

Ok I just reread your post -- the 3570's did not kick in the first time ;) Quite often in these small ma and pop shops (20 machines) you see soho routers used to add more ports vs switches, etc. But with 3570's seems you got some decent networking hardware in place.

So are these segments in the same building, or campus -- or do you have wan connections connecting the segments?

Again unless you have specific security requirements, or wan connections between the segments? It would be just easier to flatten the network this would allow broadcasting for netbios names and also allow for 1 machine to be the master browser for the segment.

Do you have a machine being used as a server? Do you have a machine that is on 24/7/365? If so I would set this machine up to be the master browser - and then set the other machines to not be able to be master browsers - this will limit the number of elections, and if all of them are running 2k pro -- they are all at the same level and any of them could be the master browser, so you could have it switching between machines and mess up the browse list, etc.

As already mentioned if you do not have windows server os running -- there are free options to having a domain be it for central userbase or just for wins and network browsing with samba. Another free option to the windows server OSes is to grab a copy of ClarkConnect - there is a free version and this can be used ad your Domain Controller and be your PDC and wins, and your domain master browser, etc.

Even if you flatten the network - I would pick a machine and set it up to always be the master browser and turn off the other machines from being able to do so -- this will make for much more stable network browsing.

This can be done with this reg key.

http://www.pctools.com/guides/registry/detail/54/

Control Network Browser Elections at Registry Guide for Windows