My German is not too good anymore, but it doesn't sound like the same
problem, really.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
I've posted this problems before but have some new information.
Suse 9.1, kernel 2.6.5-7.111-smp, reiserfs, SAMBA 3.0.9 (just upgraded to
3.0.20 today), OpenLDAP backend, as a PDC.
I've had a series of files get created in user profiles with a mtime of Dec
13, 1901 14:45. 'stat -c %Y' reports
The files are getting created on the client by all sorts of different
methods, MS Word, Excel, Acrobat, or from an email attachment.
It gets created on the server when the user logs out and the profile gets
synchronized.
Thanks for your reply - can you send me any information about the other
If using a guest account, I think null passwords must be enabled in the
global section.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Are the netbios names the same for all OSes or different?
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
It occurs to me that I should have attached the smb.conf files
--PDC--
[global]
        workgroup = DOMAIN
        server string = Primary Domain Controller
        null passwords = Yes
        passdb backend = ldapsam:ldap://XX
       Â
Jerry,
Wow, now this problem has changed a bit - the same user received yet another
file but this time with the correct times. He saved it to his desktop and
the times were once again correct. When he logged out, however, the file
time on the PDC was set to Dec 13, 1901 - Since the Windows
Please post a copy of your smb.conf
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
I agree with John's port 139 fix - you might also try setting domain master
= yes if there is not already another server serving this purpose.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Jerry,
In this particular instance, the user received the files via email from an
external source, so it's really hard to say exactly why the date is 0. I
can be sure, however, that the date is like that on the file before it
enters our network.
I've had similar problems before, for example
Could you send me a level 10 debug from smbd of the
file with a 0 mtime getting created ? I've got a
feeling something else is going on here.
Well, not exactly. The production server serves several users as minute so
a level 10 log would produce so much output it would be unusable.
Here's
I have Samba 3.0.9 running on SuSE 9.2, 2.6.5-7.111-smp kernel. SAMBA is a
PDC using OpenLDAP as a passdb backend. Workstations are combination w2k
SP3, SP4, and Windows XP SP1.
The problem I have is with profile synchronization. If a user obtains a file
that has a blank modified time, Windows
Greetings,
I have Samba 3.0.9 running on SuSE 9.2, 2.6.5-7.111-smp kernel. SAMBA is a
PDC using OpenLDAP as a passdb backend. Workstations are combination w2k
SP3, SP4, and Windows XP SP1.
The problem I have is with profile syncronization. If a user obtains a file
that has a blank modified
You should post your smb.conf and exactly what Windows error message you are
receiving.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
The write list directive is used to override the 'read only' or
'writeable' directive.
The best way to achieve what you want to do is put all the users that need
write access to this share in one group. Remove the write list
directive, and change the group owner ship of /daten/Install to that
PAM and SLAPD both usually write errors to /var/log/messages. Try doing a
follow (tail -f /var/log/messages) on one terminal while doing a getent on
another terminal.
--
To unsubscribe from this list go to the following URL and read the
instructions:
It has been my experience that each SAMBA process has a resident stack size
of about 3-4MB. You will have one SAMBA process for each active SAMBA
connection. NMBD memory use seems to be low, 2 processes at around 2-3 MB
each. So, let's say you have a domain with 100 users; plan on 300-400 MB of
the problem was the client. the owner played to much with the admin rights
the settings r completly changed.
but perhaps u can tell my what u mean with profile share?
It looks like from your config file that the logon path directive is
\\SAMBA_PDC\profiles\%U. This means that profiles
If a user belong to group 'a' logs into the windows PC
he can access the folder ab but he can also see the
shared cd folder. If he tries to access this cd
folder he is asked with username and pasword. If he
gives the correct username/password of a broup 'b'
I don't believe there is any way to create group policies on SAMBA domain
controllers.
However, you can make NT4 style domain policies. Use poledit from the
WindowsNT resource kit to create your policies. Save the policy as
ntconfig.pol in the netlogon share. These policies will work with
Can you please include your host OS and your smb.conf file?
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Modify your smb.conf file to include the necessary ldap parameters and then
set the LDAP secret password with smbpasswd -w.
Then use pdbedit to export your users to the LDAP database, like so:
pdbedit -i smbpasswd -e ldapsam
Good luck!
--
To unsubscribe from this list go to the following URL
is not
allowed to change this settings.
John, I'd be interested in testing this with you and helping with
documentation. Can you send me what you have?
Thanks,
Danny Paul
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
ldap passwd sync = Yes
ldap delete dn = yes
ldap suffix = dc=ZahidTractor,dc=com
ldap user suffix = dc=zahidtractor,dc=com
ldap group suffix = dc=zahidtractor,dc=com
ldap group suffix = dc=zahidtractor,dc=com
ldap machine suffix =
It doesn't appear that you have a profiles share. This is pretty important
if you want to save your profiles.
Also, you smb.conf file seems pretty bloated. Typically, I make my config
file as smb.conf.master. Then, I run testparm -s smb.conf.master
smb.conf. This command outputs the options
This is not a SAMBA isssue but a workstation issue.
Chances are, Windows is trying to connect as whatever user you are logged
into the machine as. Example, if you log in to the machine as user 1,
windows sends user1 as it's authentication information with each
communication. If you have one SMB
Sounds like the SAMBA machine isn't joined to the domain. Try that and see
if that helps.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
1st-SAMBA Problem is a terrible problem description. Read SAMBA Newsgroup
etiquette:
http://us1.samba.org/samba/ml-etiquette.html
2nd-Most errors can be pinpointed by tailing the samba log file. For
instance, if your log file was /usr/local/samba/var/log.smbd then do
'tail -f
Here are my questions:
1). Can someone give me more detail on the syntax errors that were
corrected?
There were certain problems in the samba.schema file of the 3.0.6 release
that went unnoticed until after the release. The SAMBA team quickly made
available a good samba.schema file and
Try removing these lines from the share definition and see what you get.
force group = +developers_group
...
force directory mode = 070
write list = @developers_group
--
To unsubscribe from this list go to the following URL and read the
instructions:
Hmmm. Glad to hear WINS fixed some of the issues.
I checked out your slapd.conf and everything looks fine there. I then
reread you previous posts and realized the computers and users are in
separate OUs. PAM/NSS only allows for one OU for Users, and since a
machine to UNIX is just another
Ok, now it sounds like the account SAMBA uses to sonnect to LDAP is too
restricted. Attach your slapd.conf.
John Schmerold wrote:
First I setup DHCP on the server - we were using the Linksys router to
provide DHCP
Then did following:
service smb stop ; service winbind stop ; rm -f
Thanks again, it's really helpful having someone that knows what they
are doing help out.
John
John Schmerold
Katy Computer Wireless
20 Meramec Station Rd
Valley Park MO 63088
636-861-6900 v
775-227-6947 f
Danny Paul wrote:
While it looks wrong, it is correct. It means the subnet
Do a tail -25 location of nmbd.log file,
likely /usr/local/samba/var/log.nmbd. This will give you the last 25
lines of the nmbd log file. See if there are any error messages relating
to name resolution problems or errors registering domain names.
If you are having such errors, stop smbd nmbd,
Please post a copy of your smb.conf
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
35 matches
Mail list logo
