samba - Oct 2004 - SuSE 9.1 Pro

Is anyone aware of any specific problems with SuSE 9.1 Pro in regards to 
running Samba as a domain controller? I have been trying for a couple of 
weeks to get it setup but keep running into one roadblock or another.

Half of the time I can't see the DC at all unless I disable the SuSE 
Firewall altogether, other times I am able to see the DC just not connect if 
I have ports 137, 138, 139 and 445 open.

I haven't been able to find much help online or in the various forums that I
frequent and was wondering if anyone knew of any specific probelms with SuSE 
9.1 that I might not be aware of.

Thanks in advance.

--
Chuck Chauvin
Network Administrator
clchauvin@edcaugusta.com

Chuck Chauvin schrieb:
>Is anyone aware of any specific problems with SuSE 9.1 Pro in regards to 
>running Samba as a domain controller? I have been trying for a couple of 
>weeks to get it setup but keep running into one roadblock or another.
>
>Half of the time I can't see the DC at all unless I disable the SuSE 
>Firewall altogether, other times I am able to see the DC just not connect if
>I have ports 137, 138, 139 and 445 open.
>
>I haven't been able to find much help online or in the various forums
that I
>frequent and was wondering if anyone knew of any specific probelms with SuSE
>9.1 that I might not be aware of.
>
>Thanks in advance.
>
>--
>Chuck Chauvin
>Network Administrator
>clchauvin@edcaugusta.com
>  
>
Hi, the simple answer is dont use suse firewall,( iptables scripts are 
easy to google )
and study more chapters from Samba Browsing
I run many samba server under suse without any special problems
what you should now is taht you should not use a .local
dns domain on your internal nameserver , which is highly recommend
for a private network, in suse 9.1 this dns domains are resolved
by multicast for miracle reason, without having the magic to disable it.
Regards

Hi Chuck,
yast is a usefull tool, but
not very usefull for configure samba
your smb log tells the truth the failure can be seen there
try recreate the user
Regards
Chuck Chauvin schrieb:
> Actually the user is a domain user. And, as I stated in my example, I setup
> a brand new user in Linux and Samba with even worse results.
> 
> As far as my conf file goes, I moved the original smb.conf and recreated 
> this one using YaST.
> 
> --
> Chuck Chauvin
> Network Administrator
> clchauvin@edcaugusta.com
> 
> ---------- Original Message -----------
> From: rruegner <robert@ruegner.org>
> To: clchauvin@edcaugusta.com
> Sent: Tue, 05 Oct 2004 20:28:26 +0200
> Subject: Re: [Samba] SuSE 9.1 Pro
> 
> ---8<---snip!---
> 
> 
>>Hi Chuck now i think it is clear that your firewall is not envolved
>>anyway disable it until you fetch the bug.
>>at a short look
>>User bagginsadmin has Primary Group SID S-1-5-32-
>> > 544,
>> >  which conflicts with the domain sid S-1-5-21-2763611909-
>>969304523- > 3334035465. >  Failing operation. your user is not a 
>>domain user, your smb.conf is very small for a pdc but should be 
>>enough, as your samba does logs no blocking by a firewall is done in 
>>my suse setup i have passdb backend = smbpasswd:/etc/samba/smbpasswd
>>
>>check if the user is exist /etc/passwd
>>and create him with smbpasswd -a user
>>This should help you out , but i recommend to read more on samba faq 
>>and suse example conf as well, cause your missing very usefull 
>>parameters in your conf Regards
> 
> ------- End of Original Message -------
>