Re: <workgroup> is not accessible???

Just to let you know, as I understand it, desktop OS's can be master 
browsers... this can be the source of much pain..

For example,  if you happen to have all the same OS versions in a 
workgroup and one machine is very old/slow, and it never gets rebooted it 
will become the master browser and slow down the entire workgroup.

Or my personal favorite, if power user X brings in wiz-bang newest version 
of the desktop OS (newer than your server versions) on his new Sony 
laptop, his laptop is now the master browser.  (And as an added bonus, if 
he's configured home networking before bring in said gem, his shinny new 
lap is also the DHCP server and default gateway...)  We had someone here 
do this, talk about a pain to troubleshoot, and as the user kept rebooting 
his machine (because it was running so slow...) the network would go 
down... then up... then down again...

Ahhh, the joys of nonstandard protocols over TCP/IP...


Keith Blazek
MIS Coordinator


pctech-bounces@xxxxxxxxxxxx wrote on 12/30/2003 04:07:56 PM:

> If I recall, that isn't it because desktop versions of the windows OS 
won't
> become master browsers (recalling from very fuzzy memory).
> 
> ----- Original Message ----- 
> From: "David Gibbs" <david@xxxxxxxxxxxx>
> To: "PC Technical Discussion for iSeries Users" <pctech@xxxxxxxxxxxx>
> Sent: Tuesday, December 30, 2003 4:00 PM
> Subject: Re: [PCTECH] <workgroup> is not accessible???
> 
> 
> > David Gibbs wrote:
> > > I manually stopped & started Samba on the linux system and it 
started
> > > working.  Up till now I've been using Webmin to restart the samba
> server.
> >
> > I'm 99.9% sure it has to do with which computer is the master browser.
> >
> > I *THINK* if the samba server is the master browser, something goes 
wrong.
> >
> > I'm going to try setting the "OS Level" for Samba down to zero, so it
> > has the lowest priority WRT being the master browser.
> >
> > david