<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Sugumar:<br>
<br>
I assume you got my address from the MUUG roundtable posting, so I will
post my reply there. I am new at setting up Samba, so others may have
more accurate or helpful information for you.<br>
<br>
I basically followed the example in <a class="moz-txt-link-freetext" href="http://www.quickfixnotebook.com/">http://www.quickfixnotebook.com/</a>
which is well worth buying from Copperfields if you have a number of
setup issues to deal with using Fedora Core. I think most of the
examples in the first edition are for FC1, but the author is aware of
FC2 and FC3.<br>
<br>
Using FC4, I had trouble with SE Linux enabled. Only after extensive
Googling did I find that SE Linux was the cause of my woes in setting
up Samba. Contrary to the web info I found, re-enabling SE Linux
afterward did NOT allow proper directory sharing, and I continue to
boot without SE Linux enabled.<br>
<br>
The Samba Howto
<a class="moz-txt-link-freetext" href="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/">http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/</a> is helpful,
and there are examples of smb.conf files in the fast start section
including one for a domain controller
<a class="moz-txt-link-freetext" href="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/FastStart.html#id2524276">http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/FastStart.html#id2524276</a><br>
<br>
To answer your questions:<br>
1) to make your Samba server a PDC, you need to set its priority
higher than that of your competing Windows machines. The smb.conf
setting<br>
os level = 65<br>
is generally sufficient.<br>
I am also using <br>
domain master = yes<br>
security = domain<br>
but I think security = domain is not necessary to make Samba your PDC.<br>
Take that info with a grain of salt.<br>
<br>
2) I am using <br>
passdb backend = tdbsam<br>
No configuration of the database was required. Everything was just
there. I am not using LDAP - it looks like there is considerable
setup, and it is probably not necessary unless you plan on scaling up
to a large network with subnets on it.<br>
<br>
If you are using a similar system and this is even remotely helpful, I
would be glad to post or send my smb.conf file.<br>
<br>
sugumar c wrote:<br>
<blockquote
cite="mid20051203043622.5614.qmail@web30605.mail.mud.yahoo.com"
type="cite">
<pre wrap="">hello
How to configer samba PDC server and how to use
LDAP server
pls explan. i am waiting for your replay
bye
sugumar.c
--- Dan Martin <a class="moz-txt-link-rfc2396E" href="mailto:ummar143@cc.umanitoba.ca"><ummar143@cc.umanitoba.ca></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The problem is SE Linux.
I finally found the solution to this problem on
Google by adding more
search terms
</pre>
</blockquote>
<pre wrap=""><!----><a class="moz-txt-link-freetext" href="http://readlist.com/lists/redhat.com/fedora-list/14/73268.html">http://readlist.com/lists/redhat.com/fedora-list/14/73268.html</a>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> >>This two services was working OK before
>>my
>>update from FC3
>>
>>I think that it was having something to do with
</pre>
</blockquote>
<pre wrap="">SE, because to
</pre>
<blockquote type="cite">
<pre wrap=""> >>solution
>>this I had to turn off SE, reboot, then turn on
</pre>
</blockquote>
<pre wrap="">SE & reboot again,
</pre>
<blockquote type="cite">
<pre wrap=""> >>this
>>(I think) relabeled the entire file system &
</pre>
</blockquote>
<pre wrap="">after this; no more
</pre>
<blockquote type="cite">
<pre wrap=""> >>problems with the smb & ppp0 services getting
</pre>
</blockquote>
<pre wrap="">working ok.
</pre>
<blockquote type="cite">
<pre wrap=""> >>
</pre>
</blockquote>
<pre wrap="">I booted after turning off SE, and it works - after
many frustrating
hours of looking for the problem in Samba.
Dan Martin wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I have been playing with Samba 3 on FC4 for over 3
</pre>
</blockquote>
<pre wrap="">days now, and it's
</pre>
<blockquote type="cite">
<pre wrap="">starting to get not fun.
Samba appears to be up and running and the network
</pre>
</blockquote>
<pre wrap="">is functional.
</pre>
<blockquote type="cite">
<pre wrap="">When I browse the network on my Windows machines
</pre>
</blockquote>
<pre wrap="">(one is Win 2000 pro
</pre>
<blockquote type="cite">
<pre wrap="">the other is NT4) I am prompted for a
</pre>
</blockquote>
<pre wrap="">username/password, then the
</pre>
<blockquote type="cite">
<pre wrap="">server shows on the network. I can open its
</pre>
</blockquote>
<pre wrap="">folder, and I can browse
</pre>
<blockquote type="cite">
<pre wrap="">a tmp share inside (path /tmp) subject to the
</pre>
</blockquote>
<pre wrap="">permissions of the
</pre>
<blockquote type="cite">
<pre wrap="">subfolders.
When I try to access the home folder named "user"
</pre>
</blockquote>
<pre wrap="">I get the error
</pre>
<blockquote type="cite">
<pre wrap="">\\Linuxserver\user is not accessible. The network
</pre>
</blockquote>
<pre wrap="">name cannot be found.
</pre>
<blockquote type="cite">
<pre wrap="">It appears that authentication is working, as I
</pre>
</blockquote>
<pre wrap="">can login at the
</pre>
<blockquote type="cite">
<pre wrap="">prompt, and the subfolder representing the home
</pre>
</blockquote>
<pre wrap="">directory is named
</pre>
<blockquote type="cite">
<pre wrap="">after the user. Permissions under Linux should
</pre>
</blockquote>
<pre wrap="">not be an issue, since
</pre>
<blockquote type="cite">
<pre wrap="">I have granted universal access to /home and all
</pre>
</blockquote>
<pre wrap="">subdirectories. If I
</pre>
<blockquote type="cite">
<pre wrap="">try to browse folders that I do not have access
</pre>
</blockquote>
<pre wrap="">to, I get a different
</pre>
<blockquote type="cite">
<pre wrap="">error - access denied.
Since the default mapping of the [homes] share did
</pre>
</blockquote>
<pre wrap="">not seem to work, I
</pre>
<blockquote type="cite">
<pre wrap="">have even tried setting the smb.conf parameter
path=/home/%S
to no avail.
I have tried numerous other things, and a Google
</pre>
</blockquote>
<pre wrap="">search turned up
</pre>
<blockquote type="cite">
<pre wrap="">dozens of dead ends.
Does anyone have ideas re
1) the above problem
2) how to 'flush the cache' so that I don't have
</pre>
</blockquote>
<pre wrap="">to log on and off on
</pre>
<blockquote type="cite">
<pre wrap="">Windows every time I try a change in Samba
3) how to determine on the Linux machine which
</pre>
</blockquote>
<pre wrap="">windows user is
</pre>
<blockquote type="cite">
<pre wrap="">accessing from the network so I can confirm
</pre>
</blockquote>
<pre wrap="">authentication is correct
</pre>
<blockquote type="cite">
<pre wrap="">(like a 'who' command for Samba)
</pre>
</blockquote>
<pre wrap="">
--
-Dan
Dr. Dan Martin, MD, CCFP, BSc, BCSc (Hon)
GP Hospital Practitioner
Computer Science grad student
<a class="moz-txt-link-abbreviated" href="mailto:ummar143@cc.umanitoba.ca">ummar143@cc.umanitoba.ca</a>
(204) 831-1746
answering machine always on
_______________________________________________
Roundtable mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Roundtable@muug.mb.ca">Roundtable@muug.mb.ca</a>
<a class="moz-txt-link-freetext" href="http://www.muug.mb.ca/mailman/listinfo/roundtable">http://www.muug.mb.ca/mailman/listinfo/roundtable</a>
</pre>
</blockquote>
<pre wrap=""><!---->
                
__________________________________________
Yahoo! DSL – Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
-Dan
Dr. Dan Martin, MD, CCFP, BSc, BCSc (Hon)
GP Hospital Practitioner
Computer Science grad student
<a class="moz-txt-link-abbreviated" href="mailto:ummar143@cc.umanitoba.ca">ummar143@cc.umanitoba.ca</a>
(204) 831-1746
answering machine always on
</pre>
</body>
</html>