Re: [Samba] W2k logon
Joseph M Carmon wrote: After setting a user up on W2k and the samba 2.2.7a PDC a profiles directory on the PDC is created with the proper perm, but windows reports that the profile cannot be loaded. The W2k machine is connected to the network and to the domain. My administrator account is allowed to log on however. The Log files do not show any errors. Any help is appreciated. Have a look to http://marc.theaimsgroup.com/?l=samba&m=106573980128294&w=2 Detlef -- -- -- (Q Q) ---o0o.-(_)-.o0o MATERNA GmbH Information & Communications Business Unit Information Business Center Government http://www.materna.de Detlef Lammermannmailto:[EMAIL PROTECTED] Wetterkreuz 3Voice: +49 9131 / 7723-60 D-91058 Erlangen Fax: +49 9131 / 7723-960 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File corruption
On Sun, Jun 13, 2004 at 10:00:23PM -0500, Warren Odom wrote: > Postscript to my last message: I was hoping you could tell me if there ware > a "Samba exerciser" program that would simulate this sort of file activity, > and would report any errors along with the valuable information of which > workstation caused the problem. One or two of the archived threads I saw > referred to some such software used by the Samba team--might this be > available for others to test with? Or would it not be applicable to a > database environment? There is smbtorture, but this is to determine protocol correctness, and can simulate netbench tests. It doesn't simulate a multi-user db environment (they're all different). All this software (smbtorture) ships with the Samba source code. It's just not built by default as it's not an end-user tool. Jeremy -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Antwort: Re: Antwort: Re: [Samba] requiresignorseal
I tested on two different Samba Servers with 3.0.3 installed before. With 3.0.3 I had no problems, but after upgrading to 3.0.4 or 3.0.5pre1 I had that problems. I also tested with new installed workstation systems, but also I had thar problems. I found systemlog entries on the workstation, wich said, that the domaincontroler does not support that sort of authentication, and that i should try to change that regvalue. "Gerald (Jerry) Carter" <[EMAIL PROTECTED]> An Gesendet von: [EMAIL PROTECTED] samba-bounces+ste Kopie fan.iven=voessing [EMAIL PROTECTED], Andrew [EMAIL PROTECTED] Bartlett <[EMAIL PROTECTED]> rg Thema Re: Antwort: Re: [Samba] requiresignorseal 09.06.2004 16:49 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: | | I also tested with 3.0.5pre1, and I also have to change | the regvalue, otherwise I get the error, that there is no | domain controller or the computer account is unknowen. I've not seen any other reports of this. Are you sure its not a local configuration error ? cheers, jerry - -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc "...a hundred billion castaways looking for a home." --- Sting -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAxyN7IR7qMdg1EfYRAt6aAJ9FEqLv59nxKDFj5+s85xfKGYq4ZwCeIVgX dfxMzPegBY2xUL/xrIFWl4c= =FCIr -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File corruption
Postscript to my last message: I was hoping you could tell me if there ware a "Samba exerciser" program that would simulate this sort of file activity, and would report any errors along with the valuable information of which workstation caused the problem. One or two of the archived threads I saw referred to some such software used by the Samba team--might this be available for others to test with? Or would it not be applicable to a database environment? -- Warren -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File corruption
Thanks for answering my message so quickly. > I don't know of any reproducible data corruption > bugs in the current versions of the code (naturally if I did I'd be working > full time on fixing them immediately :-). Yes, that's the impression I got after perusing old discussion threads, including some messages with your name on them. > Have you updated to the latest redirector hotfixes on all your clients ? Well, we have updated the "vredir" files, if that's what you mean, on Win 95/98 to the version level specified by the 3rd-party software vendor. But they required that for the Novell client too, not just the MS client. Other than that, we haven't updated all systems, and that hadn't occurred to me. (I've been kept busy researching Samba options, scratching my head, rebuilding files, and upgrading NICs, also with the latest drivers downloaded from 3Com). All the MS updates I remember seeing are security-related. But if you think this is a realistic possibility, I can run Windows Update and see about service packs or networking updates. Which brings up a point: Do you know of any reason Win 98 (2nd Edition) shouldn't work in this environment? Put another way, does your experience, or what you've heard, give you any reason to think that Win 2K might succeed with Samba where Win 98 fails? (The software vendor does list win 98 as a supported client.) > Does your vendor have test code to ensure server/client correctness against > a particular server ? What recommendations does the vendor make when using > their software in an all-Windows (no Novell) environment ? Do they recommend > any changes in server or client settings ? Yes, they have specific recommendations, and they have a program to be run on all client workstations that tells you if anything is wrong, and sets the registry entries they want. They do support Novell and Windows servers. The registry entries vary according to the network client and the O/S; for instance, on the Windows client they turn off oplocks on Win2K clients but not on Win 98 because I guess Win 98 doesn't support oplocks anyway. On Win 98 they turn off something, I think it's write-behind caching. I have run this program on all clients (on some, several times just to make sure I didn't miss them). They have recommendations for the a Windows server: Disable network redirector file caching (MS article 163401), disable oplocks, and disable RFCB open cache limits--but I presume all these are covered by the Samba options I have set. If you want to see all their recommendations, they are at http://managemore.com/faq/networking.htm#NT . -- Warren -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File corruption
On Sun, Jun 13, 2004 at 08:05:02PM -0500, Warren Odom wrote: > > Week before last we had 3 corruptions in 2 days. After the first two, > that's when I finally turned on #3 above, and then within a few hours had > the third corruption. The boss is really getting upset that I have to kick > everyone off the system to rebuild the problem file--some of these files are > > 300MB and take 2 hours or more to rebuild. He is saying another problem, > and Samba goes into the trash and we revert to the Novell server. Ok, the interesting thing here is that you've moved from using Novell client software on your Windows clients to depending on the Microsoft code shipped with Windows. The Microsoft code is noticeably poorer quality at doing things like multi-user database access than the Novell code. Note I'm not ruling out a bug in Samba, but I don't know of any reproducible data corruption bugs in the current versions of the code (naturally if I did I'd be working full time on fixing them immediately :-). Have you updated to the latest redirector hotfixes on all your clients ? Turning off oplocks and setting strict locking is the *minimum* you should to to attempt multi-user database access using the Windows client code. > 4. Does anyone know of some software I could run to actually test Samba for > problems? Something that would really exercise multi-user access.? Does your vendor have test code to ensure server/client correctness against a particular server ? What recommendations does the vendor make when using their software in an all-Windows (no Novell) environment ? Do they recommend any changes in server or client settings ? Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] File corruption
We have moved our 3rd-party multiuser billing system database files from Novell NetWare to Samba (first 2.2.8a, and now, just last Friday evening, upgraded to 3.0.2a) on Mandrake Linux 9.2 (kernel version 2.4). Now, about once every week or so, we get a file corruption, and last week (even after upgrading some NICs) seemed to be even worse, with 5 or 6 problems. Because we had no problems before changing servers, I think hardware errors are probably not to blame, even though I've seen them implicated in Samba discussions. And because it only occurs when multiple users are in a file (never otherwise, even after many, many index rebuilds and other file repair operations done by a single user), my guess is that it stems from some sort of locking or other synchronization problem. Also, so far there does not seem to be a pattern as to which workstations have errors, except generally the most-used ones. We have a mix of Win 98 and Win 2K clients (mostly the former). We used to have two Win 95 workstations, but upgraded them to 98 to try to solve the problems. No Unix programs access these files (except for nightly backups), only the billing software using Samba. The workstations still login to NetWare as the primary network login, then use the Windows networking to map the drive to Samba. Our Samba configuration file is very simple, with only one share. I've tried various combinations of these three settings: 1. I turned off all oplocks, and that didn't fix it. 2. I set sync always = yes and strict sync = yes, and that didn't fix it either. (I have turned these off & on several times to see if there's any effect.) 3. Most recently I have set strict locking = yes. Week before last we had 3 corruptions in 2 days. After the first two, that's when I finally turned on #3 above, and then within a few hours had the third corruption. The boss is really getting upset that I have to kick everyone off the system to rebuild the problem file--some of these files are > 300MB and take 2 hours or more to rebuild. He is saying another problem, and Samba goes into the trash and we revert to the Novell server. I know it's hard to track down things like this, but here are some specific questions: 1. Are there any other options anyone can suggest trying? Also, apart from a server crash, would you expect #2 to be actually relevant to the problem or not? 2. I know Samba is supposed to re-read the config file periodically, and I'm counting on that when I change the various options. But how can I really tell whether or not Samba has changed the option--and more to the point, changed its behavior? Do any of the above options have inherent delays before Samba can change? The way some of the corruptions have come shortly after I changed a setting which would be expected to make the files MORE safe, not less, have me wondering whether Samba is really changing the settings. I can use smbstatus to confirm there are no oplocks, but what about the other settings? In other words, must I stop & restart Samba after changes such as these (thereby temporarily kicking everyone off the system, a real hassle)? 3. What debugging level would be required for a developer to investigate this? Would it be preferable to be a combined log, or would separate logs for each workstation be usable? Is there a way to get Samba logs to contain only the most recent stuff leading up to a non-reproducible-on-demand incident like this, without filling them up with hours or days of clutter? 4. Does anyone know of some software I could run to actually test Samba for problems? Something that would really exercise multi-user access.? Any help would be MUCH appreciated. I'm running out of time. Thanks -- Warren -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba on Mac doesn't see "include" shares
I'm having an annoying problem. On my Linux Server (with Samba 3.0.3) I am using the samba option of 'include = /etc/samba/smb.%U.conf' so that users mostly only see shares that specifically belong to them. This approach works perfectly on Windows XP workstations. After a user logs onto the Linux server -- by simply clicking on a share that's accessible to all users -- the user then can see the shares that are only supposed to be visible to him or her. But under Mac OS X 10.3.3, I'm not having any success with this strategy. Users can see the shares that are accessible to everyone. However, even after logging into the server and viewing one of those shares, the Mac users can never see the shares that specifically belong to THEM. Does the "include" option not work in Macs? In my samba logs, I can see that the Mac users are logging in. But they can never see their own shares listed in the dropdown box of available shares. And even if the Mac users try to log in manually to those shares after connecting to a generally-available share (e.g., by going to the "Connect" dialog box and typing "smb://username:[EMAIL PROTECTED]/samba_share_name" the private shares can't be accessed. Is there a way around this problem? I have no issues on the Mac when I try to access shares that are accessible to all users in a particular group, for instance. Only when I try to access individual shares that use this "include" option. Hope somebody knows the answer. It's very important to me that "private shares" not be visible by users other than those to whom they belong. Andy Liebman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: kerberos problem
How did you fix it? Would you share it please? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
