Re: [Samba] More pam_winbind trouble
I've found the problem. As it turns out, it was me suffering from accute cranial rectalitis. Note to interested parties regarding try_first_pass and use_first_pass: I had, for some reason that now escapes my comprehension, assumed they had behavior differen than what they truly have. I had assumed that "try_first_pass" implied attempting to authenticate with stored credentials, but asking for new ones if old ones weren't found (correct behavior) or if authentication failed (incorrect behavior). try_first_pass simply means "obtain credentials if there are none stored", whereas use_first_pass means "use whatever is stored ONLY". Thus, if the stored credentials are wrong, neither of these flags will cause pam_winbind to ask the user for new credentials if the stored credentials fail authentication. This is the correct behavior because if the stored credentials are wrong, and we get new credentials, and those are wrong as well, we run into a scenario whereas we have two bad credentials that need to be passed to other modules in the chain, and no objective criterion to select one above the other (we can only pass along one set of credentials). Sorry for the trouble. My setup is now complete (I think :) ). I'll be posting a nice little howto which includes how to set up kerberos (GSSAPI) enabled SSH access, AD-centric authentication (with password change using the unix passwd command), and automatic password changing on expiry (through pam), within the next couple of days. I also came up with a backported patch from Samba 3.0.22 to Samba 3.0.20 allowing for the automatic password change on expiry. I'll post that as well for interested parties. Cheers Diego Diego Rivera wrote: Hello all. Sorry for the re-post, I MUST remember to turn off HTML text and GPG signing... First off, I'm using Samba 3.0.22 and can't risk to use Samba 3.0.23rc1 because I have no "valid" test environment for it. My problem is this: I'm using pam_winbind to authenticate users against ActiveDirectory, and whenever they enter a bad password, pam_winbind will fail 3 times in a row, but the user is only asked to enter the password once (the first time). This, of course, is resulting in a lot of needlessly locked accounts. I tried substituting with pam_krb5, and it worked fine, which means it's a logic problem with winbind. However, there's other reasons I can't use pam_krb5. I'm trying to figure out where the logic fault is within pam_winbind, but it would help if whoever wrote it could shine a light my way. I'm in the process of comparing the pam_winbind code from 3.0.22 with 3.0.23rc1 to see if I catch anything obvious. The toughest part is "filtering out" all the new stuff. If I come up with a patch to fix this, I'll submit it for review. This is the last remaining step in getting my environment up and working. Once it's verified to be OK, I'll be posting a small howto for what I've done, as I'm sure others may be interested in doing similar things. Thanks Diego -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Slow file transfers from server to XP clients
I had a similar problem in the past and the problem was I locked the NIC and I think the switch (HP Procurve 4000M I think) at 100Mb/full. Seemed like a good idea at the time. Changing the ifconfig to auto-config and the hub as well resolved the issue. This is a known documented issue with the link negotiation architecture from what I remember. There was a HP whitepaper on it. Scott... Scott Burns NETCON Technologies Inc. Voice: +1.519.652.0401 Fax: +1.519.652.9275 E-Mail: [EMAIL PROTECTED] Web: www.netcontech.com -Original Message- From: Bret Holbrook [mailto:[EMAIL PROTECTED] Sent: Saturday, June 03, 2006 9:15 AM To: samba@lists.samba.org Subject: [Samba] Slow file transfers from server to XP clients Hey everyone, I'm sure this topic has been discussed, but I've looked through history and done google searches and just haven't found a resolution yet so I'm hoping the experts can help me. Running Fedora Core 5 and Samba ??? Not sure the version off-hand. Clients are XP Professional The problem is miserably slow file transfers from the server to the XP clients (and it's primary purpose is a file server) and I mean along the lines of 4.5 to 5 hours for a 5 gig directory. This is over a 100mb switched network with a really good HP managed switch. Transferring the same directory from client to client takes less than 45 minutes. Transferring data to a Win 98 client on the other hand moves much faster, not as fast as win to win but acceptably fast. I have had the same exact problem through about six generations of Linux/samba from RedHat 9 and each version of Fedora. Each time I have done a complete format/re-install and same problem. I have also tried switching the Nic in the server with a working pull from a client and no change. I even forced the Nic to 100 full in dos before placing in the Linux box. Really at an end of my knowledge which was limited in the first place, just not sure why this isn't working and really trying to avoid putting 2k3 on there. Any Help would be greatly appreciated, or if the topic has been discussed ad-nauseam then if you could post some links or point me in the right direction that would be helpful. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Doh !
OK bury head in sand job ! Samba smb.conf is working fine. I was getting thrown by [EMAIL PROTECTED]:/mnt/samba/archive/dave-comp_backup$ touch test [EMAIL PROTECTED]:/mnt/samba/archive/dave-comp_backup$ ls -al total 12 drwxrwx--- 1 dave dave 4096 2006-06-01 21:13 . drwxrwx--- 1 dave dave 4096 2006-06-01 21:07 .. drwxrwx--- 1 dave dave 4096 2006-06-01 21:05 2006-06-01_21.04.10.326411.dave-comp.ful -rw-rw 1 dave dave0 2006-06-01 21:13 test [EMAIL PROTECTED]:/mnt/samba/archive/dave-comp_backup$ where I expected -rw-- as defined in smb.conf. However when I actually accessed the file it was restricted as in smb.conf ie --rw--. the ls -al just shows how it was mounted. Doh - Oh well wont forget that again in a hurry :) Dave -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Slow file transfers from Samba
Scott, That fixed the problem. Unbelievable, I've been dealing with that problem for almost two years. I can't believe I didn't think to try that. I erroneously assumed that if you had a 100mb switch plugged into a 100mb card you were going to get 100mb out of it. I'm almost ashamed of myself having been an IT Administrator/Manager for about 15 years. Anyway, thank you very much for taking the time to offer up a solution, you have truly made my day. Many thanks, Bret -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] changing name of PDC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I currently have 2 Samba Servers on a Network. One is PDC, the other one is Domain Member Server. Now I have to switch the roles of the 2 servers without changing their names. I tried to switch configs, smbpasswd and secrets.tdb, I deleted browse.dat and wins.dat, but still the clients try to authenticate against the old server. I even removed one of them from the domain and inserted it back again, but while joining, it sill connects to the old one. I now got my Network running again by making the old server a backup domain controller, but I will have to remove it in the near future. Is there any way to get the clients to connect to the new server? Regards, Thomas - -- * * Thomas Widhalm Unix Administrator * * University of Salzburg ITServices (ITS) * * Systems Management Unix Systems * * Hellbrunnerstr. 34 5020 Salzburg, Austria * * [EMAIL PROTECTED] +43/662/8044-6774 * * gpg: 6265BAE6 * * http://www.sbg.ac.at/zid/organisation/mitarbeiter/widhalm.htm * * -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEgvH8kbjs3GJluuYRAu4LAJ9UIWnsg9YLcw95WpxoRZ3MEhXMbwCgiE5t p7RE4z5CGdhtwhd/MGVEUrI= =J82r -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] changing name of PDC
The simple way to do this is to make your member server a domain controller. SWAT has a wizard for this. Since you are not using LDAP however, you will have problems with accounts. They will not follow the promotion. I refer you to chapter 5 of the Official Samba Howto Collection (http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/samba-bdc.html). You may be able to get the new domain controller working by copying the entire directory containing your tdbsam files to your new machine. Make sure Samba is shut down on both machines before doing this! Afterwards, start up Samba only on the new server. On the old domain controller, move (not copy) the tdbsam directory elsewhere. This should stop the machine from retaining its old SID. Next, use the SWAT wizard to demote the old domain controller to a domain member server. Under no circumstances have both machines running as domain controllers at the same time! Either one could be picked up and the changes will not replicate between servers. Also, only one server should be running WINS at any one time. NOTE: by not changing the machine names, you will have to adjust the clients (or the logon scripts) if you are moving shares from the old domain controller to the new one. Good luck. Thomas Widhalm wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I currently have 2 Samba Servers on a Network. One is PDC, the other one is Domain Member Server. Now I have to switch the roles of the 2 servers without changing their names. I tried to switch configs, smbpasswd and secrets.tdb, I deleted browse.dat and wins.dat, but still the clients try to authenticate against the old server. I even removed one of them from the domain and inserted it back again, but while joining, it sill connects to the old one. I now got my Network running again by making the old server a backup domain controller, but I will have to remove it in the near future. Is there any way to get the clients to connect to the new server? Regards, Thomas - -- * * Thomas Widhalm Unix Administrator * * University of Salzburg ITServices (ITS) * * Systems Management Unix Systems * * Hellbrunnerstr. 34 5020 Salzburg, Austria * * [EMAIL PROTECTED] +43/662/8044-6774 * * gpg: 6265BAE6 * * http://www.sbg.ac.at/zid/organisation/mitarbeiter/widhalm.htm * * -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEgvH8kbjs3GJluuYRAu4LAJ9UIWnsg9YLcw95WpxoRZ3MEhXMbwCgiE5t p7RE4z5CGdhtwhd/MGVEUrI= =J82r -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] Enabling a user w/ more than 14 char passwd prompts for a password.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Warren Beldad wrote: > I have created a user with a password of 15 characters... > then disable: > -bash-3.00# smbpasswd -d user1 > Disabled user user1. > > Enable: > -bash-3.00# smbpasswd -e user1 > New SMB password: > > Why is this happening? Is there any limitation for > the number of password characters? > we would like to limit to 14 chars but we don't know > of any consequences. Our bug. Fixed in 3.0.23rc1. cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFEgyp4IR7qMdg1EfYRAqwfAKCxFY+rpu6JdXCC5hvIvC+tExeHpACfUVVA DJwNFfsTslNP4RB9zj6wxLA= =jGU5 -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] RE: Domain trusts regression (I hope) 3.0.21c -> 3.0.23pre1, rc1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gautier, B (Bob) wrote: > Looks like it might be: the DS_DOMAIN_IN_FOREST flag > has been dropped from the rpccli_ds_enum_domain_trusts > call in winbindd_ads.c (but not from the call in > rpcclient/cmd_ds.c, where the symbolic value is not > used, btw. This means that in 3.0.23rc1 winbindd > and rpcclient currently give you different 'trusted > domains' lists.) I'll look into it. Please file a report at https://bugzilla.samba.org cheers,. jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFEgys+IR7qMdg1EfYRAn6/AKCpi4ai8z3fpVjym96dp4Gq4/TKXACdHMap LNMuDW4ufhxWH3udP8GrvCU= =dIVZ -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] kerberos and ads join.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aurélien Bras wrote: > Hi, > > All is working fine, I just wondering why if I delete > my tickets kerberos, "net ads join " is still > working, kerberos isn't needed ?? > > I typed these command : > > net ads leave > kinit destroy > > and "net ads join" still working We create our own ticket cache in one does not pre-exist. cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFEgykYIR7qMdg1EfYRAjiQAKDEbTVo2xHcLat7KTa5WC2h/NB+WQCgv5sP qCtKFMr+ULcTm34uOZWtTHU= =spw0 -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] trouble with file group owners with Samba 3.0.22.
Hi Ken, check "Primary Group" setting for user administrator. I think this is your problem. In w2k3 and w2k there is setting called "Primary Group" under the Member of tab in Properties of Administrator. Regards Tom Ken schrieb: We're running Samba 3.0.22 on a Debian system with kernel 2.6.16.16. The file system is jfs with POSIX ACL and Security labels support. We have setup winbind so our Samba server grabs the user names and passwords from our NT PDC. I have tried creating files with two users. One is called scanner2 and belongs to the windows group scanning. The other user is Administrator and belongs to the group Domain Admins. When I create the file with the user scanner2, the file's group owner is scanning, which we want. However, when I create a file with the user Administrator, the file's group owner is Domain Users. We would like it so anything created by Administrator has a group owner of Domain Admins. Any help would be greatly appreciated. Thanks. --Ken -- Thomas Dorsch IT Services EWT Multimedia GmbH & Co. KG Volkhartstrasse 4-6 86152 Augsburg Tel. +49 821 3106 311 Fax. +49 821 3106 399 http://www.ewttss.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba and DOS Attributes
I am trying to run a critical DOS (xBASE - Foxpro) application on a Suse Linux Enterpise Server with Samba 3x... I have turned off Oplocks2, but left oplocks on( without it, performance is miserable). Various command issued through the DOS Program, Record and File Locking, Copying Files, etc.. are causing Samba to change the file attribute in Linux to Read Only (Clients can't write to the files). A simple chmod -R 770 clears the problem until it comes back again. The DOS attributes don't change, even though Samba has the file a Read Only, the DOS attribute (looking from a command prompt), is still Read/Write...? Samba doesn't seem to like working with DOS, Are there any options I can set or change, or am I missing something basic. Any suggestions will be appreciated... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba BDC + LDAP slave Referral errors
We use sambaPDC + LDAP On our BDC we have a replicated ldap slave. Everything seems to work fine. Hower, in the smbd log file we have the following messages (only on the BDC's) [2006/05/31 15:25:08, 1] passdb/pdb_ldap.c:ldapsam_modify_entry(1495) ldapsam_modify_entry: Failed to modify user dn= uid=pc01233$,ou=Machines,dc=brrc,dc=be with: Referral [2006/05/31 15:25:08, 0] passdb/pdb_ldap.c:ldapsam_update_sam_account(1720) ldapsam_update_sam_account: failed to modify user with uid = pc01233$, error: (Success) [2006/05/31 15:25:08, 1] passdb/pdb_ldap.c:ldapsam_modify_entry(1495) ldapsam_modify_entry: Failed to modify user dn= uid=pc01233$,ou=Machines,dc=brrc,dc=be with: Referral [2006/05/31 15:25:08, 0] passdb/pdb_ldap.c:ldapsam_update_sam_account(1720) ldapsam_update_sam_account: failed to modify user with uid = pc01233$, error: (Success) Can someone prevent this errors? Does samba/openldap need to be changed? What is actually happening? With more Debug info: log level = 2 passdb:3 auth:3 in smb.conf [2006/05/31 15:32:48, 3] auth/auth.c:check_ntlm_password(219) check_ntlm_password: Checking password for unmapped user [EMAIL PROTECTED] with the new password interface [2006/05/31 15:32:48, 3] auth/auth.c:check_ntlm_password(222) check_ntlm_password: mapped user is: [EMAIL PROTECTED] [2006/05/31 15:32:48, 3] auth/auth.c:check_ntlm_password(268) check_ntlm_password: guest authentication for user [] succeeded [2006/05/31 15:32:48, 2] lib/smbldap.c:smbldap_open_connection(692) smbldap_open_connection: connection opened [2006/05/31 15:32:48, 2] passdb/pdb_ldap.c:init_sam_from_ldap(499) init_sam_from_ldap: Entry found for user: pc00829$ [2006/05/31 15:32:48, 2] passdb/pdb_ldap.c:init_sam_from_ldap(499) init_sam_from_ldap: Entry found for user: pc00829$ [2006/05/31 15:32:48, 3] auth/auth.c:check_ntlm_password(219) check_ntlm_password: Checking password for unmapped user [EMAIL PROTECTED] with the new password interface [2006/05/31 15:32:48, 3] auth/auth.c:check_ntlm_password(222) check_ntlm_password: mapped user is: [EMAIL PROTECTED] [2006/05/31 15:32:48, 3] auth/auth.c:check_ntlm_password(268) check_ntlm_password: guest authentication for user [] succeeded [2006/05/31 15:32:48, 2] passdb/pdb_ldap.c:init_sam_from_ldap(499) init_sam_from_ldap: Entry found for user: pc00829$ [2006/05/31 15:32:48, 2] passdb/pdb_ldap.c:init_ldap_from_sam(912) init_ldap_from_sam: Setting entry for user: pc00829$ [2006/05/31 15:32:48, 1] passdb/pdb_ldap.c:ldapsam_modify_entry(1495) ldapsam_modify_entry: Failed to modify user dn= uid=pc00829$,ou=Machines,dc=brrc,dc=be with: Referral [2006/05/31 15:32:48, 0] passdb/pdb_ldap.c:ldapsam_update_sam_account(1720) ldapsam_update_sam_account: failed to modify user with uid = pc00829$, error: (Success) [2006/05/31 15:32:48, 2] passdb/pdb_ldap.c:init_sam_from_ldap(499) init_sam_from_ldap: Entry found for user: pc00829$ [2006/05/31 15:32:48, 2] passdb/pdb_ldap.c:init_sam_from_ldap(499) init_sam_from_ldap: Entry found for user: pc00829$ [2006/05/31 15:32:48, 2] passdb/pdb_ldap.c:init_sam_from_ldap(499) init_sam_from_ldap: Entry found for user: pc00829$ [2006/05/31 15:32:48, 2] passdb/pdb_ldap.c:init_ldap_from_sam(912) init_ldap_from_sam: Setting entry for user: pc00829$ [2006/05/31 15:32:48, 1] passdb/pdb_ldap.c:ldapsam_modify_entry(1495) ldapsam_modify_entry: Failed to modify user dn= uid=pc00829$,ou=Machines,dc=brrc,dc=be with: Referral [2006/05/31 15:32:48, 0] passdb/pdb_ldap.c:ldapsam_update_sam_account(1720) ldapsam_update_sam_account: failed to modify user with uid = pc00829$, error: (Success) Kind regards, Ivo Zwonarz. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Intermittant browsing problems
Rich Mozingo Assistant General Manager Lakewood BlueClaws 732-901-7000 x 103 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbclien and tar archive creation
hi all, i have a a problem when I use smbclient with tcN options. when in the share nobody file is changed smbclient make a tar file with empty directory. someone as idea ? maybe a bug ? tnx -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] puzzling samba failure
I can't work out why the samba server can't seem to authenticate at the moment. I stopped and started the nmbd and smbd and the LDAP server but to no avail. i've copied the output I get from some of the samba commands. I'm running it on a unix server, solaris 8. regards Anna [EMAIL PROTECTED] # ./smbstatus Samba version 2.2.8a Service uid gid pid machine -- No locked files [EMAIL PROTECTED] # ./smbclient -U abarnes -L localhost added interface ip=156.145.179.27 bcast=156.145.179.255 nmask=255.255.255.0 added interface ip=156.145.179.31 bcast=156.145.179.255 nmask=255.255.255.0 added interface ip=156.145.179.29 bcast=156.145.179.255 nmask=255.255.255.0 added interface ip=156.145.179.33 bcast=156.145.179.255 nmask=255.255.255.0 added interface ip=192.168.1.27 bcast=192.168.1.255 nmask=255.255.255.0 Password: session setup failed: NT_STATUS_LOGON_FAILURE [EMAIL PROTECTED] # ./smbpasswd abarnes New SMB password: Retype new SMB password: ldap_connect_system: Binding to ldap server as "uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot" ldap_connect_system: Binding to ldap server as "uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot" No user to modify! Password changed for user abarnes. Failed to modify entry for user abarnes. Failed to modify password entry for user abarnes -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Maximum samba file transfer speed on gigabit...
Ok so maybe someone can explain this to me. I've been banging my head against the wall on this one for several weeks now and the powers that be are starting to get a little impatient. What we've got is an old FoxPro application, the FoxPro .dbf's being stored on a Linux fileserver using Samba (Fedora 3 currently, using Fedora 5 on the new test server). We're having speed problems (don't mention the fact that we should be using a real SQL server - I know, I know). So I'm thinking what I need to do is to increase the speed at which the server can distribute those .dbf files across the network. We'd been getting somewhere between 10-20 MB/s, depending on file size, etc. We've already got a gigabit network. So, I'm thinking to myself, "a gigabit is 125 MB/s, so we should be going a LOT faster". Ok, so I know it's only really about 119 MB/s (darn 1000 B = 1KB vs 1024 B = 1KB marketing crap). Whatever. That's a lot faster than 10-20 MB/s. I've got a bottleneck, I tell myself. The hard drive light on the old server is blood red all the time and top reports high (~10-40%) iowait. Must be the hard drive. So we upgrade from 2x 10K RPM SATA 1.5Gbps drives in RAID-0 to 4x 15K RPM SAS 3.0Gbps drives in RAID-10. That should do it. Nope. No difference, no change whatsoever (that was an expensive mistake). Then it must be the network card is the bottleneck. So we get PCI-E Gigabit NICs, I learn all about rmem and wmem and tcp window sizes, set a bunch of those settings (rmem & wmem = 2500, tcp window size on Windows = 262800 as well as so_sndbuf, so_rcvbuf, max xmit, and read size in smb.conf = 262800), still no change. No change! I can run 944 Mb/s or higher in iperf. Why can't I even get a FRACTION of that transferring files through Samba? I mean, hard drive speed shouldn't be the issue - a single one of these SAS drives is supposed to sustain 90+ MB/s, and I have four of them raided together. The NICs are testing out at nearly 1Gb/s. Is there REALLY that much overhead for Samba? Isn't there something I can do to increase the efficiency of the file transfer speeds? It doesn't seem to matter which settings I use in Samba, the best I ever get is about 22 MB/s, and it sometimes bogs down to around 12 MB/s. Assuming nothing else is the bottleneck, that's about 100 Mb/s - 175 Mb/s, or 10-18% of the theoretical limit of gigabit ethernet. The Windows clients never write the data received over the network to the hard drive, it loads it up into memory, which should be fairly fast, as are all the clients - 2.8+ GHz, 800MHz FSB, 10K RPM SATA drives, etc. Besides that, these fast SATA drives ought to be able to write more than 10-15 MB/s for a file transfer anyway. What am I missing here? Is the overhead for Samba really that significant, or is there some setting I can change, or am I overlooking something else? Thanks for your help, and maybe you guys can spare my head any more injury from the banging it has been getting over the past few weeks. -BJ Quinn -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba 3.0.22 on solaris9 does not start as daemon
I'm trying to start smbd (samba 3.0.22) as daemon (smbd -D --configfile=/etc/smb.conf) on solaris 9 sparc with current recommended patches but the smbd process never returns from trying to become a daemon. Samba was built with ldap, (heimdal) kerberos and active directory support using gcc 3.3.2 from sunfreeware. Solaris 9 is a new install on a development machine with production patches. The build was based on notes in http://lists.samba.org/archive/samba/2006-May/120930.html except that the heimdal version is 0.7.2 and no configure patch was applied (to heimdal configure). Other software versions: openldap is 2.3.20 bison-1.34-sol7-sparc-local m4-1.4.2-sol9-sparc-local make-3.80-sol9-sparc-local db-4.2.52.NC-sol9-sparc-local binutils-2.11.2-sol8-sparc-local flex-2.5.31-sol9-sparc-local Also disabled solaris 9 ld and gssapi samba 3.0.22 (from samba.org) nmbd starts and runs as a daemon without error. The log output from smbd -D --configfile=/etc/smb.conf and smbd -F --configfile=/etc/smb.conf is identical. The daemon version of the logout is below. Can anyone suggest where to look next to resolve this? The eventual objective is to run samba as a member server in an AD mixed mode domain. Thanks, Neil -- email: [EMAIL PROTECTED] [2006/06/01 14:12:44, 0] smbd/server.c:main(805) smbd version 3.0.22 started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2006/06/01 14:12:44, 5] lib/debug.c:debug_dump_status(368) INFO: Current debug levels: all: True/30 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0 rpc_parse: False/0 rpc_srv: False/0 rpc_cli: False/0 passdb: False/0 sam: False/0 auth: False/0 winbind: False/0 vfs: False/0 idmap: False/0 quota: False/0 acls: False/0 locking: False/0 msdfs: False/0 [2006/06/01 14:12:44, 2] param/loadparm.c:do_section(3671) Processing section "[homes]" [2006/06/01 14:12:44, 8] param/loadparm.c:add_a_service(2446) add_a_service: Creating snum = 0 for homes [2006/06/01 14:12:44, 10] param/loadparm.c:hash_a_service(2483) hash_a_service: creating tdb servicehash [2006/06/01 14:12:44, 10] param/loadparm.c:hash_a_service(2493) hash_a_service: hashing index 0 for service name homes doing parameter comment = Home Directories doing parameter valid users = %S doing parameter read only = No doing parameter browseable = No [2006/06/01 14:12:44, 4] param/loadparm.c:lp_load(4230) pm_process() returned Yes [2006/06/01 14:12:44, 8] param/loadparm.c:add_a_service(2446) add_a_service: Creating snum = 1 for IPC$ [2006/06/01 14:12:44, 10] param/loadparm.c:hash_a_service(2493) hash_a_service: hashing index 1 for service name IPC$ [2006/06/01 14:12:44, 3] param/loadparm.c:lp_add_ipc(2580) adding IPC service [2006/06/01 14:12:44, 8] param/loadparm.c:add_a_service(2446) add_a_service: Creating snum = 2 for ADMIN$ [2006/06/01 14:12:44, 10] param/loadparm.c:hash_a_service(2493) hash_a_service: hashing index 2 for service name ADMIN$ [2006/06/01 14:12:44, 3] param/loadparm.c:lp_add_ipc(2580) adding IPC service [2006/06/01 14:12:44, 10] param/loadparm.c:set_server_role(4163) set_server_role: role = ROLE_DOMAIN_MEMBER [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset UCS-2LE [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset UCS-2LE [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset UTF-16LE [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset UTF-16LE [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset UCS-2BE [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset UCS-2BE [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset UTF-16BE [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset UTF-16BE [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset UTF8 [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset UTF8 [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset UTF-8 [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset UTF-8 [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset ASCII [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset ASCII [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset 646 [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset 646 [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(103) Attempting to register new charset ISO-8859-1 [2006/06/01 14:12:44, 5] lib/iconv.c:smb_register_charset(111) Registered charset ISO
[Samba] password sync and ldap acls
Hello, I followed the "Linux Samba-OpenLDAP Howto" from IDEALX. My slapd.conf rootdn is cn=ldapmgr,ou=Managers,o=miage My smb.conf ldap admin dn is cn=sambamgr,ou=Managers,o=miage With the ACLs from section 5 (Security considerations) of the Howto when I change a user password from windows XP the userPassword attribute is not modified so my Unix and Windows passwords are not in sync. I found that adding the following ACL to my slapd.conf resoves the issue. access to * by dn="cn=sambamgr,ou=Managers,o=miage" read I did several tests but can't figure out what are the attributes that sambamgr needs to read in order to update the userPassword attribute ? Any help would be appreciated. Thierry. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Connecting XP SP2 to Samba 2.0.6
Hi! Please don't whack me too hard for even attempting this, but I need a definitve answer for a school network: can a smb share from a Samba 2.0.6 be accessed from a WinXP Prof with SP2 at all? Thanks a bunch in advance, Torsten -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Password policy problem
I'm looking to implement a global password policy in Samba 3.0.22 I noticed during testing that if I use a minimum password age of say 7 days and then create a user via User Manager with the option of "user must change password at first login" the user is requested to change the password but is then denied by the policy. Is there anyway to create a user and allow the policy to apply after the first password change? Thanks Dean -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba requires Restart every 2-3 months
Hi All, We have this issue where we are not able to login to Unix from windows. Our system admins inform us that this is an issue with Samba and it requires our unix box(Jepson) to be restarted. We have very little information on Samba. Any guidance on why it hangs every 2-3 months would be great. Is there any way to get a fix/upgrade for this. Thanks Zakki -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: administrator privileges
I experienced the following problem with an apparent permissions Catch-22 where there's no "root" user to bootstrap from with Samba-LDAP, and found several other people experienced it too. I eventually figured out why a few people are plagued by this problem while most have never seen it, and I solved it. For everyone else who experiences a similar problem, the explanation and solution are below. > Proxy2:/etc/samba# net join -U root > root's password: > [2005/07/22 16:02:01, 0] utils/net_ads.c:ads_startup(191) > ads_connect: Transport endpoint is not connected > [2005/07/22 16:02:01, 0] rpc_client/cli_netlogon.c:cli_nt_setup_creds(256) > cli_nt_setup_creds: request challenge failed > Creation of workstation account failed > User specified does not have administrator privileges > Unable to join domain DUCOR. [trying to fix a winbind problem] > supzli02pdc:/ # net rpc join -U administrator > Password: > Create of workstation account failed > User specified does not have administrator privileges > Unable to join domain SUPZ. > [EMAIL PROTECTED] root]# net join -I 192.168.0.20 -W PGNAPLIKACE -U kaminskiz > -n kaminskiz > kaminskiz password: > [2003/10/01 14:12:31, 1] utils/net_ads.c:ads_startup(176) > ads_connect: Connection refused > [2003/10/01 14:12:32, 0] rpc_client/cli_netlogon.c:cli_nt_setup_creds(249) > cli_nt_setup_creds: request challenge failed > [2003/10/01 14:12:32, 1] utils/net_rpc.c:run_rpc_command(154) > rpc command function failed! (NT_STATUS_NOT_SUPPORTED) > Create of workstation account failed > User specified does not have administrator privileges > Unable to join domain PGNMAIL1. > $net rpc user add admin -U root -S TOWER -W PIASKI > # net rpc join -U admin > Password: > Create of workstation account failed > User specified does not have administrator privileges > Unable to join domain PIASKI. > # net join -U samba (??? ? ? > ) > samba password: > Create of workstation account failed > User specified does not have administrator privileges > Unable to join domain DOM. > # net join -I -U > 's password: > [2005/04/08 10:46:06, 0] utils/net_ads.c:ads_startup(186) > ads_connect: No such file or directory > [2005/04/08 10:46:06, 0] rpc_client/cli_netlogon.c:cli_nt_setup_creds(256) > cli_nt_setup_creds: request challenge failed > Create of workstation account failed > User specified does not have administrator privileges > Unable to join domain . [trying to add a file server to an existing domain] > server1.example.com > [2004/09/30 23:36:35, 2] lib/interface.c:add_interface(79) > added interface ip=192.168.0.150 bcast=192.168.0.255 > nmask=255.255.255.0 > smbadmin's password: > [2004/09/30 23:36:37, 1] libads/ldap.c:ads_connect(251) > Failed to get ldap server info > [2004/09/30 23:36:37, 0] utils/net_ads.c:ads_startup(183) > ads_connect: No results returned > [2004/09/30 23:36:37, 1] utils/net_rpc.c:run_rpc_command(141) > rpc command function failed! (NT_STATUS_ACCESS_DENIED) > Create of workstation account failed > User specified does not have administrator privileges > Unable to join domain RHEL. > [2004/09/30 23:36:38, 2] utils/net.c:main(792) > return code = 1 The problem isn't really a Catch-22 despite appearances. Somehow --for reasons I don't fully understand-- this problem seldom arises either on older versions of Samba or on Sambas that don't use LDAP or even on new Samba-LDAP systems that have "migrated" from an older implementation. All the old advice about using something like `smbpasswd -a root` isn't relevant, both because smbpasswd is deprecated in Samba 3.x and because most Samba-LDAP systems are configured to look _only_ to LDAP for their "passdb backend" and so never see the information you tried to set up through `smbpasswd`. Some Samba operations use the _Windows_ privileges. They cannot be performed even by a Samba superuser if that user doesn't also have the right Windows privileges. Somewhere _inside_ Samba you need to define what will be the user you use for joining machines to the domain to include sambaSID -500 (S-1-5-21-...-500) and sambaPrimaryGroupSID -512 (S-1-5.21-...512). (These are _Windows_ rules, not something Samba has added or changed.) Also the user's uidNumber has to be 0 (*nix root equivalent). The rid's 500 (0x1F4: user Domain Administrator) and 512 (0x200: group Domain Administrators) are crucial. To repeat, the superuser needs to be created _inside_ the Samba-LDAP database. Nothing you do with smb.conf, Samba supporting commands, or *nix permissions will be relevent. It probably makes sense to make the _same_ user you use for LDAP access (which is probably already set up) also be the Network Administrator. Also within Samba there need to be three sambaGroupMapping entries for "Domain Admins" (-512), "Domain Users" (-513) and "Domain Guests" (-514). And these three entries have to include corresponsing *nix gidNumber values. (To minimize confu
[Samba] Request
I apologize if this is out of line or the incorrect venue to make my request. I have spent months, off and on, attempting to download a large iso file through my Linux desktop to my Linux-based server. It was frustrating and damn near impossible. I kept suffering failures when the file size hit 2Gig. I asked around in several newsgroups, I believe this mailing list, and some web forums to no avail. I finally sorted the matter out and was able to receive my iso image. The holdup was that SAMBA involves a 2 Gigabyte file size limit that no one ever mentioned. I finally stumbled onto the details and by simply adding "lfs" near the end of my fstab mount statements for my server's SAMBA shares. Once I had that piece of information, it took about 10 minutes to fix the statements and remount the shares. I understand there is also a way to mount SAMBA shares as cifs shares which does not appear to be as feature rich, but does overcome the 2Gb file size limit. We are operating in a day and age of broadband Internet service, DVD media, and downloadable software (like Linux distribution iso for example), that easily exceed 2Gb. I would like to request that the "lfs" command option and perhaps even the "cifs" option be better documented in the manpage. This assuming the archaic 2 Gb limit can not be overcome in subsequent versions of SAMBA. Thank you. -- Mark E. Adams http://adamslan.shyper.com Random Musing: Tom's hungry, time to eat lunch. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can anyone help?
Quick question pleaseA user logs into windowsXP and tries to create a folder/document and the ownership on the new file/folder defaults to nobody:nobody. I have the user set up in samba on the IRIX machine. All other users have no problem. Anyone have any suggestions? Thanks Rachel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba