Neighborhood Network

I had an environmenet WINDOWS NT 4.0 and since I did the
migration to Windows 2003 Server.
I have 3 IP domains at same Windows domain .
10.1.222.x, 10.2.222.x,10.3.222,x.
I have two WINS servers, Two DNS servers in 10.1.222.x.
Since the migration when i go to neighborhood network, I
could see all pc in my network (10.1.222.x) but not the
rest. is it very important for all my users but I don't
know how to make it? it sounds like it might be a WINS
(NBT) issue. But i have two WINS server, up and running
and all clients and servers are configured with the
address of these WINS servers!!!
ANY IDEA PLEASE????

WINS only provides netbios naming,...it doesn't by itself, make Network
Neighborhood work. You must combine it with "Netbios over TCP/IP" and there
must be a machine on each subnet that is able to act as the master browser
for that subnet.

BTW - You have three networks or "subnets", they are not domains,...if you
call them domains you will confuse people.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Technical-MS" <Technical-(E-Mail Removed)> wrote in message
news:425701c42b65$153ac1c0$(E-Mail Removed)...
> I had an environmenet WINDOWS NT 4.0 and since I did the
> migration to Windows 2003 Server.
> I have 3 IP domains at same Windows domain .
> 10.1.222.x, 10.2.222.x,10.3.222,x.
> I have two WINS servers, Two DNS servers in 10.1.222.x.
> Since the migration when i go to neighborhood network, I
> could see all pc in my network (10.1.222.x) but not the
> rest. is it very important for all my users but I don't
> know how to make it? it sounds like it might be a WINS
> (NBT) issue. But i have two WINS server, up and running
> and all clients and servers are configured with the
> address of these WINS servers!!!
> ANY IDEA PLEASE????
>
>

Hi.

The following is a list of recommendations to consider when setting up browsing on
your network:

For any registry setting below, see article Q136712

1) Disable the ability of all but a few servers to participate in browsing
elections on each subnet (need 1 browser for every 32 machines). The setting in the
registry is MaintainServerList = No (or disable the browser service if NT/W2k).
This will prevent machines that are rebooted often from initiating a browsing
election and cause different servers to be elected as the master browser at
frequent intervals. This is the single most important thing you can do to stabilize
your browsing environment.

2) On the few servers that will participate in browsing elections, they should be
servers that are rarely rebooted. Never disable a PDC's ability to participate in
browsing elections. Pick one server per subnet to be the master browser and set it
to IsDomainMaster = True

3) Verify that all machines are configured to use WINS servers. Make sure there is
a domain <1Bh> record in all WINS servers for each domain that you are attempting
to browse. The domain <1Bh> record should contain the IP address of the PDC for
that domain. In addition, make sure that the PDC's server name is also registered
in all WINS servers under the name type of <20h>.

4) Use the utility called browstat to determine which machine is the master browser
for the subnet. If you are having browsing problems on that subnet, verify often
which server is the master browser and make sure the role is not changing often.
Check the System Event log for any indication that browsing elections are being
initiated frequently. If the above recommendations are followed, I would expect
browsing elections to take place but every few days.

5) Make sure that there are no device that forward UDP port 138 broadcasts. This is
a classic problem with IPHelper configurations on routers for DHCP.
They not only forward DHCP broadcasts, but a number of other things as well.
Never configure a potential browse master to be a DHCP server, and have IPHelper
configured on any router to forward DHCP requests to it. This is not much else in
an environment that will more effectively destabilize browsing than forwarding UDP
port 138 to another subnet.

6) Always disable any multihomed server from participating in browsing elections.
If the PDC is multihomed, move that role to another server or make the PDC
single-homed. Any RAS server should be considered multihomed.

7) If the above recommendations have been followed, and a given subnet is still
having flakey browsing problems, you more than likely having a problem with the
master browser of that subnet. In that case I would disable that ability of that
machine to participate in elections and select another machine to take that role, and initiate a browsing election using browstat.
--------------------
>From: "Technical-MS" <Technical-(E-Mail Removed)>
>Sender: "Technical-MS" <Technical-(E-Mail Removed)>
>Subject: Neighborhood Network
>Date: Mon, 26 Apr 2004 01:04:22 -0700
>
>I had an environmenet WINDOWS NT 4.0 and since I did the
>migration to Windows 2003 Server.
>I have 3 IP domains at same Windows domain .
>10.1.222.x, 10.2.222.x,10.3.222,x.
>I have two WINS servers, Two DNS servers in 10.1.222.x.
>Since the migration when i go to neighborhood network, I
>could see all pc in my network (10.1.222.x) but not the
>rest. is it very important for all my users but I don't
>know how to make it? it sounds like it might be a WINS
>(NBT) issue. But i have two WINS server, up and running
>and all clients and servers are configured with the
>address of these WINS servers!!!
>ANY IDEA PLEASE????
>
>
>

--
Sergio Moreno
Microsoft Windows Networking

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.