[ale] SAMBA problem solved! New problem . . .

[Greg]

Windows uses a system of values in an election as follows (partial list):
NT server 4.0 	33
"  "      3.5	32
" Workstation 4.0	17
Windows 98			2

and following this os election each is assigned a value dependant on its
role, i.e. PDC, WINS client, Preferred Master Browser, Active Master
Browser, etc..

Machines w/ the highest version of the election protocol win, then the
priority goes to OS, then the machine with the setting of Preferred Master
Browser, then by client name.

So, to use Samba you need to do several things:
set the os value
set the role setting
set it to force an election

don't forget to remember that the local master browser does not necessarily
be the domain master browser.

This is a complicated subject (I have just spent a number of hours
re-configuring a clients machine w/ samba) and I would suggest you use
Google or buy some books (Using Samba - O'Reilly or "Samba Unleashed" are
the 2 I have that deal specifically with samba) to get up to speed on this.
Or you can hire me ;-() and I will take care of everything.  Samba is part
M$ and part Unix as well as configuring both client and server, so you need
to know how to traverse the gulf that divides them.

Greg Canter


> -----Original Message-----
> From: ale-admin at ale.org [mailto:ale-admin at ale.org]On Behalf Of
> ChangingLINKS.com
> Sent: Sunday, December 15, 2002 7:09 PM
> To: ale at ale.org
> Subject: Re: [ale] SAMBA problem solved! New problem . . .
>
>
> I agree. The Win boxes are gonna drop anyway. Well, I tried the
> solution of
> adding the os level line, and it did not work. I tried setting it
> to 65 and I
> tried setting it to 1.
> Restarting SAMBA does not work. I stopped samba and the Win box
> still could
> not see itself or browse the network. It seems as though the
> Linux server has
> "jammed" the Win machines (not my other Linux box) from the network.
>
> The ONLY way to get it working is to physically disconnect the Lin Samba
> Server from the network! The other Linux box does not run Samba,
> and does not
> create a problem at all.
>
> Anyone seen this problem?
>
> Drew
>
> On Sunday 15 December 2002 14:46, you wrote:
> > ChangingLINKS.com wrote:
> > > I was having a problem getting all of the Windows machines
> the ability to
> > > write to a shared directory. The solution was to add the line
> "[homes] "
> > > Without that line, Samba was not completely authorizing the users to
> > > write, but did allow the users to read.
> > >
> > > The next problem is that is seems as though I must start Win
> before Lin.
> > >
> > > 1. I turn on the Win boxes. I turn on the Linux Samba server.
> Everything
> > > works right.
> > >
> > > 2. I turn OFF the Win boxes. I turn the Win boxes on. (The
> Linux server
> > > stays up)  The Win boxes CANNOT see each other and cannot see
> the server.
> > >
> > > 3. To fix the problem, I must shut down the Linux box, start
> the Windows
> > > machines (which see each other again) and then start the server.
> > >
> > > One would think that it would be common for Win boxes to be
> shutdown and
> > > turned on around a Lin server. Does anyone else have this problem? Is
> > > there a solution that will allow me to drop my Win boxes
> without losing
> > > network connectivity?
> >
> > I think it's just a matter of time for the windows boxes, but rather
> > then have to shutdown the Linux box, stopping/starting samba should be
> > sufficient.  Generally that would be something like:
> >
> > /etc/rc.d/init.d/smb restart
> >
> > This may vary from distro to distro.
> >
> > > Drew
> > > _______________________________________________
> > > Ale mailing list
> > > Ale at ale.org
> > > http://www.ale.org/mailman/listinfo/ale
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>
>

_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale