Question : Cannot browse my network place

I have a windows 2003  server setup as a stand alone server. In the network there are 5 remote locations each connected through a vpn back to the main office I can not browse computers through my network places. The only ones that are seen are the ones in each office locally. In the remote offices the dns is pointed to the server in the main office. Netbios over tcp has been initiated. Also the LMhosts has been started. I can still not see  any other workstation on the wk3 server except the local office. I have contacted the isp who moniters the routers and are wide open.

Answer : Cannot browse my network place

The domain master browser populates a list of folks in My Network Places.

The way the Browser service works, (in the default browser configuration), is the clients will transmit a Netbios broadcast to show all available Master Browsers, "I AM HERE". If a Master Browser does not reply meaning it is not found, then an election can be forced by that client. The client can elect anything from another client to a mass storage device for a Master Browser. Sometimes you can get a couple master browsers on a single domain. Then, you will see workgroup comptuers disappear from time to time.

2PiFL is right in saying the router is blocking Netbios: I will explain later.

There are multiple ways to set up a configuration to help the master browser server communicate with the clients:

1) The default configuration requires you are all able to communicate by using netbios broadcasts  on UDP ports 137, and 138. So, any IP port blockage can interfere with the master Browser service. Since these Netbios broadcasts are transmitted on UDP ports 137 and 138, the client can be transmitting into some sort of port blocking. That could include, VPN tunnel, NAT translation, Software/Hardware Firewall, Different Subnet, Different IP space for Multi homed domains, or some other sort of port blocking problem.

There are three potential fixes to the above blocks of the Master browser service:

2) One is to stop the blockage by lowering your guard (meaning lower the port blockage like a firewall block). This will create vulnerabilities in your network and is not recommended.

3) The second is to use WINS instead of these Netbios Broadcasts to help your master browser see a list of comptuers.  I recommend you use the WINS configuration to help the Master Browser populate the list of computers in My Network Places.  I recommend this method and the link below will show you how to use WINS and the WAN configuration to work with the Master Browser Service.

4) The third is to use the Server Service and enable File and Print Sharing on all IP stacks. Most will say that File and Print sharing is a Vulnerability to the network and recommend you turn that off. I am on of those people.

This link is the best link I have found to explain the Master Browser Service. It is a little lengthy, but definately worth the read if you really need to know why.

http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true

The link I provided above will tell you the differences between a domain master browser, a master browser, and a backup browser. It is good information for someone with browser issues. The second piece of information needed to understand the problem will be the WINS/WAN configuration of the Master Browser Service.

When you fix your configuration by Using WINS, may I recommend you create a backup browser? Otherwise, you will loose clients if you ever stop the WINS service or drop the DC.