[windows2000] Re: Net view not listing all
- From: Frank Monroe <Frank.Monroe@xxxxxxxxxxx>
- To: "'windows2000@xxxxxxxxxxxxx'" <windows2000@xxxxxxxxxxxxx>
- Date: Mon, 2 Sep 2002 16:59:54 -0400
Win 95 systems are not supposed win browser elections, unfortunately, they
do.
-----Original Message-----
From: Robert Funderburk [mailto:robfunderburk@xxxxxxxxxxx]
Sent: Friday, August 30, 2002 11:20 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: Net view not listing all
OK, except . . .
How is a WIN 95 system going to win a master browser election, with NT 4 and
2000 clients on the same subnet? Master browser elections are won based on
OS version, then OS revision, then by whether or not you have a server OS
installed. Also, you can force a system to be a master browser with a reg
fix, and you can force a system NOT to be a master browser with a reg fix.
----- Original Message -----
From: "Frank Monroe" <Frank.Monroe@xxxxxxxxxxx>
To: <windows2000@xxxxxxxxxxxxx>
Sent: Friday, August 30, 2002 4:13 PM
Subject: [windows2000] Re: Net view not listing all
>
> I have to agree with Microsoft on this one. You should have a master
> browser on each subnet. If this was working before, I can only assume
there
> was some Windows 95 system acting as the master browser on the working
> subnets and maybe that system is gone. The reason why I say this is
> disabling the browser on a Windows 95 system is not as simple as setting
the
> service to manual on NT. Also, even if you do set it to manual on NT, it
> may be started by another service and then become the master browser. If
> you want to turn off the browser elections, you should set the service to
> disabled. But you should still leave two NT/2000 systems with it set to
> automatic per subnet.
>
> -----Original Message-----
> From: Costanzo, Ray [mailto:rcostanzo@xxxxxxxxxxx]
> Sent: Friday, August 30, 2002 3:38 PM
> To: 'windows2000@xxxxxxxxxxxxx'
> Subject: [windows2000] Re: Net view not listing all
>
>
>
> Here is the alleged solution. I don't know enough to know if this makes
> sense.
>
> About a year ago, I wrote a script to set the browser service to manual
> startup on all our workstations since we have a WINS server. After doing
> that, everything was fine, and we were no longer have "browser wars" on
our
> network. Then, ten months later (about two months ago), we suddenly were
> only seeing 6 of our 48 remote locations. That was right around the time
we
> got a new router.
>
> Our network guy spent a lot of time on the phone with Microsoft today, and
> according to them, 9 times out of 10, these problems are not router
related.
> The supposed solution is to start the browser service on one workstation
in
> each remote location (each subnet?). What's a subnet? I don't know. Our
> IP address configuration here is as such:
>
> 192.168.1.* - main office
> 192.168.101.* some remote location
> 192.168.102.* some remote location
> 192.168.103.* some remote location
> 192.168.104.* some remote location
>
> and so on. Is each of those a "subnet?"
>
> I don't buy this solution of enabling the browser service on one computer
> per subnet. The reason I don't buy it is that we had the browser service
> disabled on all of our workstations for 10 months, and everything was
> totally fine. And isn't it normal to have the browser service disabled in
a
> WAN when you have a WINS server?
>
> I'm going beyond the things that I know about here. All I can do is
> theorize, but I can also question things that just don't seem to make
sense.
>
> Thanks for any wisdom,
>
> Ray at work
>
> > -----Original Message-----
> > From: Frank Monroe [mailto:Frank.Monroe@xxxxxxxxxxx]
> >
> >
> >
> > Keep in mind, the browser list really doesn't have anything
> > to do with DNS
> > or WINS except to find who is the master browser for the
> > subnet that you are
> > on. Once your client finds this out, it queries that server.
> > The browser election process in each subnet will determine
> > who is the master
> > browser for that subnet. Each master browser has to be able
> > to determine
> > who is the master browser for the other subnets so that they
> > can all tell
> > each other what is in their individual browser lists so that
> > each subnet has
> > a complete list.
> >
> > If you have any clients that are marked hidden, they of
> > course will not show
> > up in the browser list. If none of the clients in a subnet
> > have the browser
> > service running, that subnet will not show up in the list. A
> > lot of times,
> > Windows 95 systems win the browser election and become the
> > master browser of
> > a subnet, but do a poor job at it. Also, if you have routers that are
> > forwarding broadcasts, this will cause the election process
> > to break and you
> > may have subnets that think someone system on another subnet
> > is the master
> > browser for that subnet and no system will be elected for that subnet.
> >
> > Frank
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************
>
>
> ==================================
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>
> http://thethin.net/win2000list.cfm
>
> ==================================
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>
> http://thethin.net/win2000list.cfm
>
==================================
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
==================================
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
Other related posts:
