similar to: Loosing connection to samba shares

Hi. I have some trouble with my samba domain controller. Every time I try to logout my windows workstation, I get an error that the share is no longer availible. I estimate that this happens around the time when windows tries to copy my user profile back to the server. (because when I change profile type to local the error no longer occurs) on the samba side the following error is logged.

Hi All, I had been doing some testing with the Debian 3.0.4-x versions of samba. On two sepearte systems, running different configs, I've found that smbd panics unless the [printers] section is removed from smb.conf. Errors generated as follows... (System #1) Server role: ROLE_DOMAIN_MEMBER Smb.conf... [Global] security = DOMAIN printcap name = cups printing = cups [printers]

Hi, Am running SAMBA 3.0.4 on RHEL 3.0 ( 2.4.21-9.ELsmp ) It was running fine till today when i restarted my server and started getting this nmbd log!! I might have overlooked, but if anyone could point me to any previous post with answers or any other link please mail me or if there is something new or anything more you want to help me solve this, please let me know. Any help is greatly

I have moved a Samba installation from an old samba 2.2.8a (on a 2.4.21 kernel) to a new server running Samba 3.0.10 on a SuSE 9.2 (kernel 2.6.8) and I now have a problem using the (same) shares from client W2K machines. When I open "My Computer" window on a client, the drives are marked by a red cross, as if they were disconnected, and the disksize is zero. I can decend into the

Hi, Having reset-up a print server from installation disks today, I did something stupid and blindly copied the contents of /etc/samba from the previous installation into the new installation. Now smbd refuses to start (nmbd starts OK). I am currently using a blank smb.conf file and the smb.conf file from the old installation. testparm doesn't report any errors in the smb.conf from the old

Hello, I'm trying to add a user to big list of Samba groups, 74 groups to be precise. The problem is that when the user reaches around 65 to 70 groups, it starts giving errors in User Manager for Domains, and causes a panic in Samba. Is there a limit for how many groups a user may belong? I'm using Samba-3.0.10 with openldap. This is what I get in the logs. [2005/02/07 13:22:42, 0]

Hi! Seems winbind has a build-in :) error. It repeats twice a day. What other/debug info I must send ? [2005/09/14 14:40:08, 0] lib/fault.c:fault_report(36) =============================================================== [2005/09/14 14:40:08, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 8384 (3.0.20) Please read the appendix Bugs of the Samba HOWTO collection

hi, iam using samba winbind with ntlm_auth for squid authentication. i have 200 ntlm_auth clients activated in squid.conf, don't know really how many i need. I have about 200 internet users. my winbind crashed and i have the following in my winbind log .. [2006/08/25 11:39:13, 0] nsswitch/winbindd.c:process_loop(822) winbindd: Exceeding 200 client connections, no idle connection found

guys need help my samba was working fine for about 1 month then it stoped working and now i get this error log [2004/07/29 13:36:53, 5] lib/charcnv.c:charset_name(74) Substituting charset 'ISO-8859-1' for LOCALE [2004/07/29 13:36:53, 5] lib/charcnv.c:charset_name(74) Substituting charset 'ISO-8859-1' for LOCALE [2004/07/29 13:36:53, 5] lib/charcnv.c:charset_name(74)

Hi, i have got a Samba server ( currently 3.0.5 ) together with CUPS 1.1.9. running as a print server for a load of Windows 2000 / XP clients. This setup worked well for several months until about three weeks ago ( Samba 3.0.4 at that time ). Now all of a sudden i'm getting Samba crashes for those clients that try to access the 'printers and faxes' on the Samba server. In Windows

After running several days in the same configuration, my 3.0.6 nmbd crashed with the above error (see log below). Maybe there is a connection to this message some seconds before: register_name_response: server at IP 192.168.0.4 rejected our name registration of AK<1d> IP 192.168.0.12 with error code 6. The ip .4 machine is a win2k server, which works (or should work) as an ordinary

Wlcome in the club :-) I wrote a topic "Limit of group membership for a user?" with the same problem, and I don't have any answer by the samba team. I have the most recent Samba 3.0.21b, OpenLDAP 2.2.28 and Glibc 2.3.6 version on a Gentoo (kernel 2.6.15) and I have the same problem. I check the NGROUP_MAX (65535) and the NSS_BUFLEN_GROUP (2048) value of the glibc. For the AMD64

Hi, O Wise Ones, I have a number of machines running samba on Fedora 3 as member servers of a windows domain. They authenticate with Active Directory on the Windows PDC (Windows Server 2003 as part of Small Business Server 2003) and provide file and print sharing services. All has been working perfectly for months. When I applied SP1 for Windows Server 2003, authentication stopped working.

Hello, I have samba-3.0.10-1.4E.6 bundled with CentOS 4.3 x86_64 and I can't browse it with Win98. I have a very simple setup, Share type, with access to everyone. If I double-click on the server name from Win98, I have this message: "\\server is not accessible. This device does not exist on the network." If I type the whole path to the share(ex: \\server\transfer), in Win98, it

Hi All, I hope someone can help me with this problem. I recently moved my Windows Print server to Linux (Red Hat 9.0, Samba 3.0.2) due to stability problems, however since i had a constant smbd panics I reverted back to my Windows 2000 server much to the disappointment of my manager and director. Having posted to this list someone suggested an upgrade to 3.0.3pre2 which solved their issues, I

Getting this on a FreeBSD 5.2.1-RELEASE #0: Sat Aug 28 11:56:25 CDT 2004 system when trying to start the smbd process after an upgrade to the newest release. Didn't see anything helpful in the referenced appendix bugs of the Samba HOWTO collection. An attempted smbd -d10 yielded a core dump but no futher info. -------------------------------log

If i do a.... bash~#smbpasswd -a -m uos-staff i get a.... Segmendation Fault if u use the idealx scripts this appears in log.smbd (in using samba 3.0.7 with ldap support) Help!! =============================================================== [2004/11/09 11:51:07, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 2018 (3.0.7) Please read the appendix Bugs of the Samba HOWTO

Hi folks, I have updated samba to 3.0.20, on SLES9. I had a configuration earlier, where SLES9 was a domain member 2003 Server (samba 3.0.14a), everything used to work well earlier. After updating.. I rejoined it to AD there was no errors. However, Clients from windows were unable to access the shares. #>getent passwd [2005/08/22 15:41:41, 0] lib/fault.c:fault_report(36)

Hi, first i?ve installed SuSE 9.1 with the default rpms (heimdal 0.9.1rc3, samba 3.0.2a with winbind). I?ve configured the system with winbind to the user accounts from my Win2003 Server. All this works always max. 1 day. After this day I can?t connect to my shares on the samba server. After this I upgraded to 3.0.11 with the RPMs from de.samba.org for SuSE. I installed this rpms but Winbind

Hello, last friday I switched my users from an old server running 2.2.12 to a new one running 3.0.10 (that I've been testing myself and with smbtorture). After a while I had to switch back to the old server because some users were having serious problems. This is one of the logs (the others are very similar): [2005/03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725)