Re: [Samba] Is Samba made for trash ?!?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 20 Feb 2003, Michael Paarmann wrote: > logon script = %U.bat > logon path = \\server_office01\%U\profileNT > logon home = \\server_office01\%U > hide dot files = yes > domain logons = YES > domain master = YES do not join a Samba box to a Windows domain and enable the previous two parameters. You just asking for problems. > >You are dealing with a different network protocol and different network > >clients. > > No, i'm only working with TCP/IP now. And yes, the clients work with W98 > or W2K. I meant CIFS/SMB vs. Netware. Not IPX vs TCP/IP. > That's right. Spool32.exe or spoolss.exe die very often. I can see a > read or a write socket error in the log list nearly at the same time. Ahh...did you initialize the printer drivers installed on the Samba server? If you are not supporting driver download to windows clients, you might want to set "disable spoolss = yes" > Hmm, do you really think that this can solve some of my problems? The > update from 2.2.3a to 2.2.5 wasn't very effective. Samba is different from other projects such as apache. Because we are constantly learning new things about how windows servers operate, it is hightly recommended to use the latest stable release. > > But is there a possibility to set Samba in a kind of "Compatibility Mode", > so that i can be sure the source of the problems isn't Samba ? Samba constantly runs in "compatibility" mode as compared to a Windows server. At least that is the intent. We don't always get it right. cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+WuSeIR7qMdg1EfYRAt3LAJwKOUn0yOKYf4LekMZqQp6efL1YnACfQGxO 7Wa7MCrJMxpvL/TiuT/m0u4= =6IMn -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Is Samba made for trash?!? Newp.
> -Original Message- > From: Jean-Paul ARGUDO [mailto:[EMAIL PROTECTED] > Many times a day, clients here when oppening a MS Word 97 > document have > it in "READ ONLY" mode, but seems no reason fort that!! Make very, very sure that you have no network problems. I had a very similar problem with AutoCAD that turned out to be a user who was on an overloaded hub that was dropping lots of packets. Apparently AutoCAD would lock the files when he opened them, but the packet releasing the lock would sometimes get lost in transit when he closed them again. Also, if you're doing tricky things with permissions you can run into problems. When Word saves a file, it saves a new copy and deletes the old one. That means if your create mask has very restrictive permissions, the file may not be read/write by other users anymore. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Is Samba made for trash?!? Newp.
> By then, we discovered that if we disabled all oplocks, we got no more corruption. I posted here weeks ago problems regarding Excel 97 file corruption. I finally disabled oplocks then. But day passing, I had new problems with Word 97 :-/ (new posts here, mainly not answered but a tip on how to get clients at same time that servers... -NET command usage...): Many times a day, clients here when oppening a MS Word 97 document have it in "READ ONLY" mode, but seems no reason fort that!! I recently put oplocks *back* ON *but* with veto-ing excel files... I hope this change could solve de pb.. Waiting for changes, I read again docs about oplocks (Samba HOWTO Collection -R-O-X-, O'Reilly and SAM'S books too) Again and again but as Jeremy says thereafter, seems a problem *in* Word 97 ... Maybe I'll have to patch it (it's original version, just patched with Euro Font Fix, nothing more, maybe the source of the problems? -Idem with Excel) That Samba file server has been incredibly stable, serving terabytes of data to almost 100 clients. We've seen no file corruption since that day. You'll find many admins who agree with me - Samba rocks! Same opinion here. Samba works like a charm. We got 2.2.3a Debian woody stable release (damm when will they upgrade at debian?? ;-)). -- Jean-Paul ARGUDO -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Is Samba made for trash?!? Newp.
On Thu, Feb 20, 2003 at 08:40:18AM -0800, Chris de Vidal wrote: > To answer the root question (people have been > answering your symptoms), no, Samba is not trash. > > Like you, we needed to migrate from NetWare. We had a > serious problem with an undocumented oplock issue > (search marc.theaimsgroup.com, for "How samba let us > down"): oplocks corrupt very large flat database files > which are being accessed by multiple clients. We > almost dropped Samba for good and went to NT but > couldn't get the replacement NT server up in time. By > then, we discovered that if we disabled all oplocks, > we got no more corruption. It's a good thing we got > it working in Samba, because apparently this is also a > problem in NT. Indeed. Samba behaves identically to a Windows server w.r.t. oplocks. People migrating from NetWare to Samba get irritated by this, but often don't realise it's because of issues with the Windows SMB *client*, not the SMB server. The Windows NetWare client apparently was rather better written. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Is Samba made for trash ?!?
Hi Jerry ! Do you have "security = domain"? Did you join teh Samba box to the domain using smbpasswd? Please supply a copy of your smb.conf. Send it to me off list if you want. Ok, here it is: [global] workgroup = Office os level = 128 server string = File- and Printserver encrypt passwords = Yes guest account = Nobody map to guest = Bad User security = DOMAIN printing = LPRNG printcap name = /etc/printcap load printers = Yes socket options = TCP_NODELAY passwd program = /usr/bin/passwd %u passwd chat = *New*password* %n\n *Re-enter*new*password* %n\n *Password*changed* unix password sync = yes local master = YES character set = ISO8859-15 client code page = 850 mangle case = no case sensitive = no short preserve case = yes preserve case = yes time server = yes admin users = domadmin log file = /var/log/samba/samba_log.%U@%m max log size = 500 log level = 0 logon script = %U.bat logon path = \\server_office01\%U\profileNT logon home = \\server_office01\%U hide dot files = yes domain logons = YES domain master = YES preferred master = True local master = Yes wins support = Yes hosts allow = 192.168.0. hosts deny = ALL EXCEPT 192.168.0. kernel oplocks = NO level2 oplocks = NO [homes] comment = Home Directories read only = No create mask = 0770 directory mask = 0770 browseable = No oplocks = no [netlogon] comment = Network Logon Service path = /home/samba/netlogon [printers] comment = Alle Drucker path = /tmp create mask = 0600 printable = Yes browseable = No printer admin = @ma oplocks = no [profiles] comment = Network Profiles Service path = /home/%U/profileNT writeable = yes create mode = 0770 directory mode = 0770 browseable = No oplocks = NO [interna] path = /daten/interna create mode = 0770 directory mode = 0770 force group = ma valid users = @ma comment = Interna write list = @ma oplocks = NO and so on... I've disabled all oplocks. With them the clients crashed much more often than without. But Samba is a lot slower. You are dealing with a different network protocol and different network clients. No, i'm only working with TCP/IP now. And yes, the clients work with W98 or W2K. It is possible that a misformatted response could cause client crashes (like explorer.exe or spoolss.exe), but you are going to have to be more specific here. That's right. Spool32.exe or spoolss.exe die very often. I can see a read or a write socket error in the log list nearly at the same time. I will say that there are no known issues of clients crashing due to the Samba release. > Or are 35 workstations and 15 printers too much for one Samba server ? No. Samba on apprpriate hardware can handle much more than that :-) Ok. Upgrade to 2.2.7a. You are running an older release. Hmm, do you really think that this can solve some of my problems? The update from 2.2.3a to 2.2.5 wasn't very effective. But is there a possibility to set Samba in a kind of "Compatibility Mode", so that i can be sure the source of the problems isn't Samba ? Thanks in advance. Michel cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+VPZDIR7qMdg1EfYRAt+AAKDDQwSXQQoUeK+O1wxGnlDCen5K+QCgpkAl OA37r8xHJJE89qdjX9ZR2w8= =9NZO -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] Is Samba made for trash ?!?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 20 Feb 2003, Michael Paarmann wrote: > Yes. And that's what confuse me. Everyone from a Win98 or W2K > workstation can log in and gets the login script and so on - but Samba > generates this error message. Can i ignore this ? If yes, it's ok, but > this messages fill up my logs. Do you have "security = domain"? Did you join teh Samba box to the domain using smbpasswd? Please supply a copy of your smb.conf. Send it to me off list if you want. > In this case:Yes. And the clients crash much more often than before i > replace the old server based on novell with Samba. The intenstion of > replacing novell was to stabilize the network. I've checked the hardware > once again and it's ok. But this messages appears whether the client > dies or not! You are dealing with a different network protocol and different network clients. It is possible that a misformatted response could cause client crashes (like explorer.exe or spoolss.exe), but you are going to have to be more specific here. I will say that there are no known issues of clients crashing due to the Samba release. > Or are 35 workstations and 15 printers too much for one Samba server ? No. Samba on apprpriate hardware can handle much more than that :-) > > > > smbd[30829]: [2003/02/11 14:02:15, 0] > > > rpc_server/srv_netlog.c:api_net_sam_logon(206) > > > smbd[30829]: api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON. > > > >Please see the ml archives on this one. 99% chance you can ignore it. > > Can i disable this warning ? Upgrade to 2.2.7a. You are running and older release. cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc "You can never go home again, Oatman, but I guess you can shop there." --John Cusack - "Grosse Point Blank" (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+VPZDIR7qMdg1EfYRAt+AAKDDQwSXQQoUeK+O1wxGnlDCen5K+QCgpkAl OA37r8xHJJE89qdjX9ZR2w8= =9NZO -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Is Samba made for trash ?!?
Hi! At 21:25 19.02.2003 -0600, you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 19 Feb 2003, Michael Paarmann wrote: > smbd[7809]: [2003/02/11 18:26:45, 0] > smbd/password.c:domain_client_validate(1517) > smbd[7809]: domain_client_validate: could not fetch trust account > password for domain OFFICE Is office you domain? Did you successfully join the domain? Yes. And that's what confuse me. Everyone from a Win98 or W2K workstation can log in and gets the login script and so on - but Samba generates this error message. Can i ignore this ? If yes, it's ok, but this messages fill up my logs. > > smbd[4902]: [2003/02/11 18:32:32, 0] lib/util_sock.c:read_data(436) > smbd[4902]: read_data: read failure for 4. Error = Connection reset by peer The client dropped the socket. Not Samba. > > smbd[3535]: [2003/02/11 18:33:28, 0] lib/util_sock.c:read_data(436) > smbd[3535]: read_data: read failure for 4. Error = No route to host Did the client crash? In this case:Yes. And the clients crash much more often than before i replace the old server based on novell with Samba. The intenstion of replacing novell was to stabilize the network. I've checked the hardware once again and it's ok. But this messages appears whether the client dies or not! Or are 35 workstations and 15 printers too much for one Samba server ? > smbd[30829]: [2003/02/11 14:02:15, 0] > rpc_server/srv_netlog.c:api_net_sam_logon(206) > smbd[30829]: api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON. Please see the ml archives on this one. 99% chance you can ignore it. Can i disable this warning ? > > smbd[30829]: [2003/02/11 14:02:15, 0] rpc_server/srv_pipe.c:api_rpcTNP(1200) > smbd[30829]: api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed. > > smbd[3777]: [2002/12/23 12:03:43, 0] lib/util_sock.c:write_socket_data(500) > smbd[3777]: write_socket_data: write failure. Error = Broken pipe > cheers, jerry thankx. Michel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Is Samba made for trash ?!?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 19 Feb 2003, Michael Paarmann wrote: > smbd[7809]: [2003/02/11 18:26:45, 0] > smbd/password.c:domain_client_validate(1517) > smbd[7809]: domain_client_validate: could not fetch trust account > password for domain OFFICE Is office you domain? Did you successfully join the domain? > > smbd[4902]: [2003/02/11 18:32:32, 0] lib/util_sock.c:read_data(436) > smbd[4902]: read_data: read failure for 4. Error = Connection reset by peer The client dropped the socket. Not Samba. > > smbd[3535]: [2003/02/11 18:33:28, 0] lib/util_sock.c:read_data(436) > smbd[3535]: read_data: read failure for 4. Error = No route to host Did the client crash? > smbd[30829]: [2003/02/11 14:02:15, 0] > rpc_server/srv_netlog.c:api_net_sam_logon(206) > smbd[30829]: api_net_sam_logon: Failed to marshall NET_R_SAM_LOGON. Please see the ml archives on this one. 99% chance you can ignore it. > > smbd[30829]: [2003/02/11 14:02:15, 0] rpc_server/srv_pipe.c:api_rpcTNP(1200) > smbd[30829]: api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed. > > smbd[3777]: [2002/12/23 12:03:43, 0] lib/util_sock.c:write_socket_data(500) > smbd[3777]: write_socket_data: write failure. Error = Broken pipe > cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+VErDIR7qMdg1EfYRAna5AJ9X4GbcJMqcOkFxs5jmSZtSP4bjQgCfeBUF wwxLX6oR8y6/uckYYDLsEiY= =nyo3 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
