Re: [Samba] Still mandatory profiles, every user same profile
Hi Ulrich, I have a similar problem like you described: I want several users to authenticate in your windows machine with your specific login/pass, but all of them use the same mandatory fixed roaming profile. Have you succeeded your setup with the Barlett sugestions? In that case, can you post your solution? Regards, -- Joel Franco Guzmán -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] upgrading samba
Hummm. Build from scratch.. I understand that the data files live in /var/lib (except the bind, where it lives in /var/cache/bind). But if your files are there... You should pay attention in the *tdb files yes. This are the data files, and the files that live in /etc. 2009/9/22 Bill Szkotnicki b...@uoguelph.ca: Thanks. In my case the .tdb files are in /var/cache/samba Is there a possibility that there are other files anywhere else? 1) /etc/samba 2) /var/cache/samba I was thinking of building from sources and then just trying the new daemon. That way I could go back to the old one easily if necessary. Joel Franco Guzmán wrote: Hi, I use debian but this should be similar. To backup your important files, backup the /etc/samba and /var/lib/samba directories doing like this, after stop the samba daemon: # cp -a /var/lib/samba /var/lib/samba.bak # cp -a /etc/samba /etc/samba.bak Then you could do the upgrade. If something goes wrong, reinstall the old version and restore the copied directories. Regards, # cp -a /var/lib/samba /var/lib/samba.bak # cp -a /etc/samba /etc/samba.bak Then you could do the upgrade. If something goes wrong, reinstall 2009/9/21 Bill Szkotnicki b...@uoguelph.ca: Hi, I would like to appempt a SAFE upgrade on my samba server. ( Centos 5.2 ) Currently the version is: # /usr/sbin/smbd -V Version 3.0.28-1.el5_2.1 There are many users logging on to it and accessing the shares. The last time I tried this ( quite a while ago ) something broke and we had to re-join many windows machines. It would be nice to have a strategy for rolling back if something does not work. Where are all of the important files? Would anyone have any advice, suggestions, indications of what to read, etc...? Thanks, Bill -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba slave with winbind fails to communicate with the PDC
Hi all, After the net rpc join successfuly established to the Samba PDC (net rpc testjoin ok), the following commands fail: # wbinfo -u Error looking up domain users # wbinfo -g Error looking up domain groups #wbinfo -t checking the trust secret via RPC calls failed Could not check secret # net rpc testjoin Join to 'RSP' is OK It appears that, still under valid relationship with the PDC Samba server, the winbind does not get the list from the PDC. I have zeroed this server /var/lib/samba and started samba and winbind again, rejoined the domain successfuly, but i can't get wbinfo work. My /etc/nsswitch.conf: passwd: compat winbind group: compat winbind shadow: compat #hosts: files dns wins hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis and my /etc/samba/smb.conf: [global] workgroup = RSP server string = Ultra server wins server = 172.17.1.9 dns proxy = yes log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d encrypt passwords = true passdb backend = tdbsam load printers = no socket options = TCP_NODELAY security = domain password server = MYPDCSERVER idmap uid = 1-3 idmap gid = 1-3 The samba version in the PDC Server is exactly the samba that of this server. Please, what should i do? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] upgrading samba
Hi, I use debian but this should be similar. To backup your important files, backup the /etc/samba and /var/lib/samba directories doing like this, after stop the samba daemon: # cp -a /var/lib/samba /var/lib/samba.bak # cp -a /etc/samba /etc/samba.bak Then you could do the upgrade. If something goes wrong, reinstall the old version and restore the copied directories. Regards, # cp -a /var/lib/samba /var/lib/samba.bak # cp -a /etc/samba /etc/samba.bak Then you could do the upgrade. If something goes wrong, reinstall 2009/9/21 Bill Szkotnicki b...@uoguelph.ca: Hi, I would like to appempt a SAFE upgrade on my samba server. ( Centos 5.2 ) Currently the version is: # /usr/sbin/smbd -V Version 3.0.28-1.el5_2.1 There are many users logging on to it and accessing the shares. The last time I tried this ( quite a while ago ) something broke and we had to re-join many windows machines. It would be nice to have a strategy for rolling back if something does not work. Where are all of the important files? Would anyone have any advice, suggestions, indications of what to read, etc...? Thanks, Bill -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Problem with 3.0.23 upgrade from 3.0.22 with rfc2307 patch
I think the release notes for the 3.0.23b has the response:
Member servers, domain accounts, and smb.conf
=
Since Samba 3.0.8, it has been recommended that all domain accounts
listed in smb.conf on a member server be fully qualified with the
domain name. This is now a requirement. All unqualified names are
assumed to be local to the Unix host, either as part of the server's
local passdb or in the local system list of accounts (e.g. /etc/passwd
or /etc/group).
The reason for this change is that smbd has transitioned from
access checks based on string comparisons to token based
authorization. All names are resolved to a SID and they verified
against the logged on user's NT user token. Local names will
resolve to a local SID, while qualified domain names will resolve
to the appropriate domain SID.
If the member server is not running winbindd at all, domain
accounts will be implicitly mapped to local accounts and their
tokens will be modified appropriately to reflect the local
SID and group membership.
For example, the following share will restrict access to the
domain group Linux Admins and the local group srvadmin.
[restricted]
path = /data
valid users = +DOMAIN\Linux Admins +srvadmin
Note that to restrict the [homes] share on a member
server to the
owner of that directory, it is necessary to prefix the
%S value
to valid users.
[global]
security = {domain,ads}
workgroup = DOM
winbind separator = +
[homes]
valid users = DOM+%S
--
|
| Joel Franco Guzmán .''`.
| self-powered by : :' :
| Debian Linux `. `'
| `-
On Ter Jul 18 06 18:03, Howard Wilkinson wrote:
Don,
you are a genius, this fixed it! Anybody know why?
Howard.
Don Meyer wrote:
Well, I didn't see the last bit you describe, but I don't run RFC2307
(yet). We we bit by very similar behavior when moving from 3.0.22 to
the 3.0.23 RC's. Turns out that the use-default-domain option is not
being universally applied to groups in 3.0.23. As soon as I changed
my valid users = +group statements to the format = +domain\group,
then this problem was fixed for us. Maybe it will do the trick for
you...
Cheers,
-D
At 07:41 AM 7/18/2006, Howard Wilkinson wrote:
I have managed to isolate where the problem is, now I need to work
out what the problem is?
I have a group
cohtech:*:16777225:lesley,howard,ecbull
in which I am a member - howard.
I have a
valid users = +cohtech
entry in smb.conf for the share I am trying to connect to, I get the
following reported in the machine.log file -
zebra.log: string_to_sid: Sid +cohtech does not start with 'S-'.
and the users get rejected. If I declare the user directly then
access is allowed.
This server gets its group database from the AD controllers via RFC2307.
Anybody know why group expansion may be broken in 3.0.23?
Don Meyer [EMAIL PROTECTED]
Network Manager, ACES Academic Computing Facility
Technical System Manager, ACES TeleNet System
UIUC College of ACES, Information Technology and Communication Services
They that can give up essential liberty to obtain a little
temporary safety,
deserve neither liberty or safety. -- Benjamin Franklin,
1759
--
Howard Wilkinson
Phone:
+44(20)76907075
Coherent Technology Limited
Fax:
23 Northampton Square,
Mobile:
+44(7980)639379
London, United Kingdom, EC1V 0HL
Email:
[EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] login to ms access db very slow on samba 3.x
Hi, try the ethereal sniffer, now at www.wireshark.org in the linux machine and observe the differences in traffic between the 2 and 3 releases of samba. I have the same problems with db databases files in samba server while at windows 2000 and windows 2003 it runs better. I'll soon make the sniff to see the differences. -- | | Joel Franco Guzmán .''`. | self-powered by : :' : | Debian Linux `. `' | `- On Ter Jul 25 06 17:00, [EMAIL PROTECTED] wrote: Hi Brian Thanks for the hint. Unfortunately I am not at all familiar with doing this. Would that involve strace? I took a glimpse at the man pages of strace, but I don't know if I could produce some useful output with it. But maybe I got you wrong and there's an easier way? I must admit that although I'm not totally samba-illiterate, I'm no pro either (obviously :) cheers Oli Brian Cowan [EMAIL PROTECTED] wrote on 25.07.2006 16:32:06: Have you tried running network traces with Samba 2.x and 3.x and comparing the results. I suspect that at least one newer smb feature is killing you... [EMAIL PROTECTED] wrote: hi everybody we have been reading through the archives for quite some time now, and could not find a solution to our problem. please excuse if we overlooked something and our question was already answered elsewhere... we have Samba version 3.0.14a-Debian running on (you guessed it) debian with kernel 2.6.8-2-386. ever since our migration from samba 2.x we have speed issues with an ms access database which gets accessed by multiple users through an access2000 runtime application running on windows clients (2000 and XP). when users log in to the database, it takes 3min until the login-window pops up and users can enter their credentials. since things are not slow for the first user, but for every user that tries to login afterwards, we are suspecting some problems with the lock file of the db or with file ownership... also, transactions seem to be going on at normal speed once after users are logged in (also for users who encounter the slow login problem). after reading through old postings, we have disabled oplocks and level2 oplocks, also Kernel oplocks, with no success. we made a new share containing only the database file (which is about 410MB in size), with no success. after comparing the old 2.x setup with the new one, we noticed that on 2.x (where everything ran smooth) guest access was enabled and everybody was accessing the DB as user nobody of group nogroup, so we tried the same setup on our 3.x server, forcing user nobody and group nogroup on our new 3.x server, hoping that would solve the problem. nada. we have tried changing the tcp send/receive buffer size after reading through tcpdump logs, but that was probably too far off. it seemed to us that we were not the only ones with this specific problem, but every hint we found was pointing to disabling oplocks - which we did. maybe one of you guys can help us out? any hint or help will, of course, be highly appreciated. maybe we have misconfigured something? oli relevant sections of /etc/samba/smb.conf: # Global parameters [global] [...] veto oplock files = /*.doc/*.xls/*.pdf/*.mdb/*.bsd/*.MDB/*.BSD/*.bsa/*.BSA/*.lbd/*. LBD/*.ldb/*.LDB/ veto files = /lost*found/.bash_profile/.bashrc/aquota.*/.ARK_NOBACKUP/ lock spin time = 15 lock spin count = 100 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=2920 sync always = no strict sync = no kernel oplocks = No [...] [dbs] path = /var/samba/dbs read only = no guest ok = yes oplocks = no level2 oplocks = no strict locking = no fake oplocks = no create mask = 0777 directory mask = 0770 force create mode = 0777 force user = nobody force group = nogroup veto oplock files = /*.MDB/*.mdb/*.bsd/*.BSD/*.bsa/*.BSA/*.lbd/*.LBD/*.ldb/*.LDB/ [...] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] strangely lingering lock, samba 3.0.22
Me too. Same bug and exactly the same problema. As Debian user, i will install the 3.0.23 from debian repository when ready. -- | | Joel Franco Guzmán .''`. | self-powered by : :' : | Debian Linux `. `' | `- On Ter Ago 01 06 15:35, Logan Shaw wrote: Hello everyone, Today a user (call them 'abc') came to me and described the following sequence of events: 1. They opened an Excel file, made some changes, saved it, and closed it. 2. They tried to open it again and got an error dialog within Excel that says this: File in Use FooBar.xls is locked for editing by 'abc'. Open 'Read-Only' or, click 'Notify' to open read-only and receive notication when the document is no longer in use. 3. They rebooted their desktop machine and tried again, and got the same dialog again. No matter what they do, the file remains locked. The same file is locked for other Windows users and on other Windows computers as well, so obviously there is some sort of state on the Samba server that is telling the clients that the file is locked. So, I logged into the Samba server (3.0.22 running on Slackware 10.2, with kernel 2.4.31), and tried to see if I could see any evidence of a lock. The file did not show up in the output of smbstatus --locks. Running fuser on the file didn't show that any process had it open. So apparently no process has it open on the Linux machine. Also, I noticed that if I make a copy of the file on the Linux machine (cp FooBar.xls FooBar-new.xls), the copy does not retain the lock. So, it would appear that this is not related to the actual contents of the file. I also tracked down the individual smbd that user abc's machine is connected to and killed it. Another one restarted, but the lock was still not released. For what it's worth, I have oplocks = no and level2 oplocks = no in my smb.conf, so presumably this isn't an oplock issue. Anyone have any ideas what's going on? As far as I can tell, this must be a server-related issue since all clients see the file as locked, and it's apparently not an issue with the contents of the file (like Excel writing some flag into the actual file contents itself), but I can't find any indication on the server that the file is locked. - Logan -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Temporary Profiles
On Sex Dez 02 05 13:48, Oliver Schneider wrote: If you are sure there is a solution in your book, I am going to buy it. That shouldn't be a problem. I don't want roaming profiles. It would be enough, if i get a local NOT temporary profile. if you clear the global logon path = the profile should be local. It's enough to do it. I have tried to get roaming profiles to work as a part of the solution for the local profiles but that didn't helped neither. All I get then was a temporary serverside profile. All I want is a not temporary profile, where my changes are saved... Oliver Schneider 2005/12/1, John H Terpstra [EMAIL PROTECTED]: On Thursday 01 December 2005 03:01, Oliver Schneider wrote: Hi, I have got a problem with samba for days now and I don't know how to solve it. My problem is, that it doesn't matter if I enable or disable Roaming Profiles, all I get is a temporary profile. If i enable Roaming Profiles, than i get a temporary serverside Profile. If I disable Roaming Profiles, than i get a temporary local Profile. Can somebody please help me? With Roaming Profiles I think it is a problem with Filepermissions. Root get's a full Serverside Profile (not the smb.conf below), but only root. I just want a local Profile for the users, so it is not so relevant. Please follow the examples in my book Samba-3 by Example. This book is the official Samba deployment guide. If you experince any problems with the examples in this book I will help you to find the cause by which the book mis-directed you. After all, I want the documentation to be correct and of true value. Samba-3 by Example provides fully documented, step-by-step, installation and depoyment instructions for complete networking solutions. It coveres simple networks and progressively introduces complex networking examples. Every necessary configuration file is provided. Every time I have helped people on this list who have reported problems with Samba deployment - issues such as logon scripts that will not run, roaming profiles that fail to work correctly, not being able to join a domain, and so on, the solutions in this book solved the users' problem. If you do not follow the documentation provided, you will possibly go through a more painful learning process. The choice is yours. - John T. Oliver Samba is PDC [global] include = /etc/samba/dhcp.conf socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 logon drive = H: hide dot files = yes domain master = Yes username map = /etc/samba/smbusers map to guest = Bad User printer admin = @ntadmin, root, administrator logon home = \\%L\%U\.9xprofile passwd program = /usr/bin/passwd %u wins support = true printcap cache time = 750 netbios name = fileserver cups options = raw printing = cups unix password sync = yes local master = Yes logon path = logon script = logon.bat workgroup = SJ os level = 65 printcap name = cups security = user add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = Yes preferred master = Yes load printers = yes passdb backend = smbpasswd [homes] comment = Home Directories valid users = %S browseable = No read only = No inherit acls = Yes [profiles] comment = Network Profiles Service path = %H read only = No # store dos attributes = Yes create mask = 0600 directory mask = 0700 [users] comment = All users path = /home read only = No inherit acls = Yes veto files = /aquota.user/groups/shares/ [groups] comment = All groups path = /home/groups read only = No inherit acls = Yes [printers] comment = All Printers path = /var/tmp printable = Yes create mask = 0600 browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 [netlogon] comment = Network Logon Service path = /var/lib/samba/netlogon write list = @user, root guest ok = yes locking = No -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO Reference Guide, 2 Ed., ISBN: 0131882228 Samba-3 by Example, 2 Ed., ISBN: 0131882221X Hardening Linux, ISBN: 0072254971 Other books in production. -- To unsubscribe from this list go to the following URL and read the instructions:
Re: [Samba] (no subject)
-- Joel Franco | | self-powered by | Debian Linux | | .''`. | : :' : | `. `' | `- | On Seg Nov 28 05 12:26, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joel, Joel Franco wrote: | Empirically, when a NT based is added to the | existing network, the database application runs | slowly (access data) in this client machine | and in others NT machines that are added to the LAN. | | If i substitute this samba server with a Win2k3 | Standard Server, the application latency backs | to the original (or close), before the NT clients. | This was a big deception to me and since then, i'm | trying to find why this happens but i'm specialist. What version of Samba are you running? Samba 3.0.20b-2. But this problem exists since old samba versions. | I have observed in the ethereal sniffer that exists a | lot of Locking AndX Request and Locking AndX Response | that is highly ping pong communication between | the server and the client, that certainly don't | permit a good brute transfer. I understand that must | exist a lock mechanism to not corrupt the file | database shared between others stations. Most people running pc based database apps disable oplocks on the server. Can you run a quick test with and without oplocks in the Samba share. The oplocks warn that could be problem on this enabled. If a client machine crash, the database could be corrupted, correct? Should I understand the oplocks is a tradeoff and have to be choosed between speed and corrupt probability? Thank You, cheers, jerry = Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc There's an anonymous coward in all of us. --anonymous -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDi0vaIR7qMdg1EfYRAgIUAJ9jkPtfLkm+enDbZNH8nVFFx6I9WwCfQWfm h3PNQINCD70+Tu6/atQdPeA= =2Gjd -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NT clients syncronyzing in a Samba PDC Domain
On Ter Nov 29 05 13:56, Doug Campbell wrote: I understand that i'm not using roaming profile, because the logon path is empty. The only difference in this domain is that i'm using winbind to the remote domain users (that is a trusted domain) be able to print in my domain. The message is something like: syncronizing \\server\username in SERVER. This happens just after logoff. Open Windows Explorer. Click on your C: drive Click Tools-Folder Options Click the Offline Files tab Uncheck Enable Offline Files and all the other boxes for that matter I think that should take care of the problem. Cool. It really disabled it. My question, however, is can it could be get activated if a made a classical samba and Windows instalation. Thank You, -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] file mode creation at a directory level
On Ter Nov 29 05 13:55, Taolizhong wrote: Josh Kelley [EMAIL PROTECTED] wrote: On 11/29/05, Taolizhong wrote: The above requirements seem simple, however, my problem is, because the share directory is neither under any of the members' home directory nor a seperate partition, and the system umask is set to 022, which is not supposed to be changed, whenever a new file is created, it automatically has permission as -rwxr--r--, not -rwxrwx--- that I desire. I guess my problem is related to how to file mode creation at a directory level. force create mode = 0770 Thanks a lot, Josh. The force create mode solves the problem partially --- now the group members have full access to the files. However, for some unknow reason, the permission for other doesn't work. They still have read access. In addition, it doesn't work on subfolders either. Please see the following: try valid users = @group1 bash-2.05# ls -ld share/ drwsrws--x 3 tech group1 512 Nov 29 13:50 share/ bash-2.05# cd share/ bash-2.05# ls -l total 2 drwxr-sr-x 2 guest01 group1 512 Nov 29 13:51 a -rwxrwxr-- 1 guest01 group1 0 Nov 29 13:49 test.txt Any further sugestions? Thanks, --Lingtao - Yahoo! Music Unlimited - Access over 1 million songs. Try it free. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Permission denied
I have used mount.cifs because i was having troubles with smbmount. On Ter Nov 29 05 08:34, malcolm wrote: I have a Windows 2003 server with a share I try and mount a drive as follows : cd ~ mkdir testsmb smbmount //servername/sharename /home/myname/testsmb -o credentials=/home/myname/smbpassword and everything seems OK but a ls of testsmb gives ?- ? ? ? ? smbtest you can cd to the directory but ls gives permission denied If I use the Gnome GUI it works OK This is RH FC4 thanks mal -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NT clients syncronyzing in a Samba PDC Domain
Hi, Plz, i have installed a Samba NT PDC Domain with XP Prof. and strangelly the machines are syncronizing with the Samba Server when the user Logoff of the domain. I've used the smb.conf below in others domains and XP clients have never synchronized before. I understand that i'm not using roaming profile, because the logon path is empty. The only difference in this domain is that i'm using winbind to the remote domain users (that is a trusted domain) be able to print in my domain. The message is something like: syncronizing \\server\username in SERVER. This happens just after logoff. Someone plz can say me what is this and how i disable it? My configurations... :~# net rpc trustdom list Password: Trusted domains list: REMDOMAINS-1-5-21-1370651826-174269758-184960113 Trusting domains list: none :~# The smb.conf is: [global] netbios name = SERVER workgroup = DOMAIN wins support = yes dns proxy = yes log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d security = user encrypt passwords = true passdb backend = tdbsam guest obey pam restrictions = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . load printers = no socket options = TCP_NODELAY domain master = yes local master = yes preferred master = yes os level = 65 unix charset = iso8859-1 add user script = /usr/sbin/useradd -m -g users %u add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null -g ntmachines %u add group script = /usr/local/bin/smb-addgroupscript %g add user to group script = /usr/sbin/adduser %u %g delete user script = /usr/sbin/userdel %u delete group script = /usr/sbin/groupdel %g delete user from group script = /usr/sbin/deluser %u %g set primary group script = /usr/sbin/usermod -g %g %u logon script = logon.%U.bat logon home = \\%N\%U logon path = logon drive = U: domain logons = yes idmap uid = 1-2 idmap gid = 1-2 winbind enum users = yes winbind enum groups = yes template homedir = template shell = /bin/false username map = /etc/samba/smbusers [homes] comment = Home Directories browseable = no writeable = yes create mask = 0644 directory mask = 0755 [netlogon] comment = Network Logon Service path = /home/samba/netlogon guest ok = yes writable = no browseable = no root preexec = /home/samba/netlogon/gen_logon.sh %u root postexec = /home/samba/netlogon/del_logon.sh %u [printers] comment = All Printers browseable = no path = /tmp printable = yes public = no writable = no create mode = 0700 [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no [geral] comment = Arquivos Publicos path = /home/geral writeable = yes create mask = 666 directory mask = 777 -- Joel Franco | | self-powered by | Debian Linux | | .''`. | : :' : | `. `' | `- | -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NT clients syncronyzing in a Samba PDC Domain
No, i think... The instalation is standard with classic components like Office, Outlook +Express, etc.. The synchronizing window (at logoff) appears strongly be of Windows environment. Thank You, -- Joel Franco | | self-powered by | Debian Linux | | .''`. | : :' : | `. `' | `- | On Seg Nov 28 05 15:57, Tomasz Chmielewski wrote: Joel Franco schrieb: Hi, Plz, i have installed a Samba NT PDC Domain with XP Prof. and strangelly the machines are syncronizing with the Samba Server when the user Logoff of the domain. I've used the smb.conf below in others domains and XP clients have never synchronized before. I understand that i'm not using roaming profile, because the logon path is empty. The only difference in this domain is that i'm using winbind to the remote domain users (that is a trusted domain) be able to print in my domain. The message is something like: syncronizing \\server\username in SERVER. This happens just after logoff. isn't it some 3rd party program that does it? -- Tomek http://wpkg.org WPKG - software deployment and upgrades with Samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] How to synchronise multiple samba server ?
-- Joel Franco | | self-powered by | Debian Linux | | .''`. | : :' : | `. `' | `- | On Sex Nov 25 05 11:24, Aurelien Vf wrote: Hi ! I got a new problem, the company I work for had just open a new office with a network ADSL link to the old one. We have one domain controler (samba on linux) and 50 workstations in windows XP. I need to put a second domain controler at the new office, but I don't know how to link the both and then to synchronise them ? (account and passwd) Do you want to have 2 separate domains (domain A and domain B) or do you want to have the same domain with the same users in both offices? In first case, you have to look at interdomain trusts and in case B i think (fixme) that you could be a PDC and a BDC to synchorinise it. Look at the official howto in this 2 topics. And finaly, if I reach this point, how can I do to know which one will validate my users ? Is there specials parameters I do write into smb.conf file ? Any help would be really apreciate... thx Au.Vf -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NT clients syncronyzing in a Samba PDC Domain
No, i think... The instalation is standard with classic components like Office, Outlook Express, etc.. The synchronizing window (at logoff) appears strongly be of Windows environment. Thank You, -- Joel Franco Guzmán On Seg Nov 28 05 15:57, Tomasz Chmielewski wrote: Joel Franco schrieb: Hi, Plz, i have installed a Samba NT PDC Domain with XP Prof. and strangelly the machines are syncronizing with the Samba Server when the user Logoff of the domain. I've used the smb.conf below in others domains and XP clients have never synchronized before. I understand that i'm not using roaming profile, because the logon path is empty. The only difference in this domain is that i'm using winbind to the remote domain users (that is a trusted domain) be able to print in my domain. The message is something like: syncronizing \\server\username in SERVER. This happens just after logoff. isn't it some 3rd party program that does it? -- Tomek http://wpkg.org WPKG - software deployment and upgrades with Samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Red X and guest user message in logs
-- Joel Franco | | self-powered by | Debian Linux | | .''`. | : :' : | `. `' | `- | On Sex Nov 25 05 19:00, Marco De Vitis wrote: Hello, I have a Debian Sarge machine running Samba 3.0.14a as PDC and file server. Everything runs smoothly, except for a random problem: users (on Win2000Pro clients) are often seeing a red cross on the main network share, as if it was disconnected. This red X seems to come and go at random. I had that problem of a radom red X in the mapped drive too when the server was a Win98 machine. The problem was hardware on this server. The red cross would not be a big issue itself, but it has an annoying consequence: when it appears, Windows thinks the connection is down, so if you save a file on the share while the red X is there you get an error dialog telling something like The connection to the server has been reset. The file cannot be saved. (recalling from memory and translating from Italian, so the actual English message might be very different). The file is saved anyway, but users are obviously alarmed by the message. I had a look at my Samba logs (level 2) around the time when an user told me he noticed the red cross, but didn't find anything special, exception made for the following message: [2005/11/25 17:14:51, 2] smbd/service.c:make_connection_snum(314) guest user (from session setup) not permitted to access this share (COMMESSE) The user was already authenticated on the domain, and didn't logoff, so I can't understand where does this guest access come from. Can this message be related to my problem? Here follows an excerpt from my smb.conf, as returned by testparm, with some more or less sensible data omitted. BTW, the log file where I found that message was named client_name..log, which is correct (see log file setting below). I really hope someone can give me some clues, as this has been going on for months now. Thanks in advance. - [global] unix charset = UTF8 workgroup = domain name server string = Server Linux, Samba %v passdb backend = tdbsam log level = 2 vfs:2 syslog = 0 log file = /var/log/samba/%m.%U.log max log size = 0 logon script = netlogon.bat logon path = \\%L\profiles\%U logon drive = Z: domain logons = Yes os level = 64 preferred master = Yes domain master = Yes enhanced browsing = No create mask = 0664 directory mask = 0775 hosts allow = 127.0.0.1, 192.168.1.0/255.255.255.0 ea support = Yes hide files = /desktop.ini/.DS_Store/ veto oplock files = /NTUSER.DAT/ map archive = No store dos attributes = Yes dos filemode = Yes [netlogon] path = /home/netlogon browseable = No [profiles] path = /home/samba/profiles read only = No create mask = 0600 directory mask = 0700 browseable = No [COMMESSE] path = a valid path invalid users = one username force user = another username read only = No vfs objects = recycle recycle:exclude = ~$* ~*.doc *~*.tmp *.bak recycle:touch = yes recycle:versions = yes recycle:keeptree = yes recycle:repository = .cestino - -- Ciao, Marco. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Red X and guest user message in logs
Suggestions.. Try sniff the ethernet communication with ethereal in the server (within a VNC server is cool), or try to increase the log level (3 gives you a lot information). -- Joel Franco | | self-powered by | Debian Linux | | .''`. | : :' : | `. `' | `- | On Sáb Nov 26 05 01:19, Marco De Vitis wrote: Joel Franco wrote: I had that problem of a radom red X in the mapped drive too when the server was a Win98 machine. The problem was hardware on this server. I already thought about a hardware problem, but one thing mostly keeps me away from this idea: supposing there was some hardware network fault, I'd expect to find traces of communication errors in Samba logs (and maybe syslog). Instead, I see no errors in there, apart from the guest user message I reported. -- Ciao, Marco. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] (no subject)
Hi All, I'm really sad that Win2k3 server runs a lot better in a shared folder that keep a file based database that Windows 9x and WinNT clients. Explaining it better... Here in Brazil, unfortunaly we still have a lot business that is based in the old file shared database, like Dataflex, Clipper and like. Then, they need a robust and fast server to centralize that files. With Windows98 clients and Samba 3 server, the performance of the access to this shared database file is good and because the ultra robust samba server (based in Linux), this configuration scenario was a excelent solution. However, the Windows 98 is stopping be supported by Microsoft and this is forcing the client machines of this business to migrate to NT based workstations (win2k and winXP usually). Here starts the problem... Empirically, when a NT based is added to the existing network, the database application runs slowly (access data) in this client machine and in others NT machines that are added to the LAN. If i substitute this samba server with a Win2k3 Standard Server, the application latency backs to the original (or close), before the NT clients. This was a big deception to me and since then, i'm trying to find why this happens but i'm specialist. I have observed in the ethereal sniffer that exists a lot of Locking AndX Request and Locking AndX Response that is highly ping pong communication between the server and the client, that certainly don't permit a good brute transfer. I understand that must exist a lock mechanism to not corrupt the file database shared between others stations. A quick observation in the ethereal with the 98 clients, show that the protocol is different and the sniffer have not a good knowledge of it (it appears like a raw traffic). I have not still observed the Win2k3 protocol with the NT stations. This maybe is my next step. My fundamental question is, why the different protocol is so slow and, supposing that the 98 protocol with the server is better (fast and safe - at least in this files database in my experience), how i can configure the samba server to just accept this old protocol or how to configure the NT stations to runs faster. Regards All, -- Joel Franco | | self-powered by | Debian Linux | | .''`. | : :' : | `. `' | `- | -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
