On Thursday 12 July 2001 01:26 pm, Ian C. Sison wrote:
> i've got several clients hooked up to a samba-pdc using samba 2.2;
>
> For the life of me i cannot find out why it takes so long a time for the
> windows clients to recognize the samba pdc. If i try to log on, it will
> say 'no domain controller available'. But the samba server is there up
> and running. I've tried using DHCP and pointing the netbios name server
> to the samba server (same machine), and enabled/disabled WINS support in
> the samba server, still, it takes around 30m or so for the win clients to
> see the PDC.
>
> Has anyone any experience in this? It's really frustrating. Sometimes it
> takes me an entier morning to resolve this. And then suddenly and
> mysteriously domain logons will work.
>
It sounds like you have another server announcing itself as PDC (probably an
NT box?) and the clients are waiting out the election process. Note that a
linux client with nmbd running will join in the election process for master
as well. Clients that cannot connect to server can initiate an election
process too.
When we encountered this problem before, this was what was causing our
problem. If this is the case in your situation too, you may want to check
out your "os level" parameter in the smb.conf. A value of 0 will mean that
you will always lose to a Window machine. The higher it is set, the better
your chance of winning an election. The man page of smb.conf says that 65
will always make you win (unless another machine is set similarly).
You may also want to check out "local master","preferred master" , and
"domain master" and set these appropriately for your application (probably to
yes?).
Hope this bit of info helps.
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
