similar to: Winbind Dies Regularly

I have samba 3.0.28 installed on several servers and winbind dies every couple of days on all of them. The deaths appear to correlate with the following log messages: [2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655) PANIC (pid 13395): internal error [2009/01/25 04:02:09, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 14 stack frames: #0 winbindd(log_stack_trace+0x2d) [0x800ccc10] #1

I have samba 3.0.28 installed on several servers and winbind dies every couple of days on all of them. The deaths appear to correlate with the following log messages: [2009/01/25 04:02:09, 0] lib/util.c:smb_panic(1655) PANIC (pid 13395): internal error [2009/01/25 04:02:09, 0] lib/util.c:log_stack_trace(1759) BACKTRACE: 14 stack frames: #0 winbindd(log_stack_trace+0x2d) [0x800ccc10] #1

Greetings, I've got a samba server that has been serving a 100+ user network for over a year with no issues, except recently, one XP workstation throws a sharing violation when saving Excel files, but only intermittently. It's an older Samba version (3.0.29) - and yes, I know I have to upgrade. OS is Fedora 9 x64. The log shows the following when this occurs: [2009/12/18 09:42:25, 0]

Hi all, I install the Asterisk 1.4.1 in order to use the T.38 pass-through, but for the moment, I cannot even make call .... I have this WARNING: [Mar 7 11:32:09] WARNING[13395]: chan_sip.c:12290 handle_response: Remote host can't match request BYE to call '5759b80c119e1d51679dc66b519c6eac@194.148.41.50'. Giving up. Do you know what is this error and what can I do to

I'm trying to select a subset of a dataframe while dropping some factors. While the dataset gets smaller all Factor levels remain and I need to get rid of them. Strangely enough, I am almost certain that the same code on the same data worked OK earlier today - and it is not the first time that I'm not able to replicate earlier results with this command (I know, I might just be going

> I have multiple CentOS servers running a couple versions of Samba > serving various Windows versions and I've never once ever seen > this message. Glad to hear it. That's the kind of behavior I would normally expect. One thing that might be different between our environments is that my users are all in Remote Desktop sessions connected to a pair of Windows terminal servers.

When trying to create a file or folder on a samba 3.0.28-0.el4.9 share from a Windows 2003 R2 server, I continually receive an error message stating that the target filesystem does not support long filenames. I have another samba 3.0.28-0.el4.9 server where this does not happen. What causes this? Here's the smb.conf from the "bad" server. It's pretty much the same as the

When trying to create a file or folder on a samba share (3.0.28-0.el4.9) from a Windows 2003 R2 server, I occasionally receive an error message stating that the target filesystem does not support long filenames. This happens even if object name follows 8.3 naming conventions. It does not *always* happen. Also, I have another samba 3.0.28-0.el4.9 server where this does not happen at all. What

When trying to create a file or folder, or sometimes even rename a file, on a samba share (3.0.28-0.el4.9) from a Windows 2003 R2 server, I occasionally receive an error message stating that the target filesystem does not support long filenames. It does not always happen. Also, I have another samba 3.0.28-0.el4.9 server where this does not happen at all. What causes this? Here's the

I have two CentOS servers running samba3-3.0.34-37. When I connect to a samba share from my Windows 2003 R2 servers, and then try to copy a file to it, I often get the message "target filesystem does not support long filenames." Sometimes it works and sometimes it doesn't. I've been fighting this problem for 2 years. I've replaced my Windows servers, changed my Windows

I just read the Samba list rules and did not see anything against offering payment for expertise, so I'm letting the list know that I need Samba help and am willing to pay normal consulting rates. If you are interested, please respond by direct email. We have a number of CentOS 5.2 and 5.3 servers that work quite well and are AD-integrated using relative IDs to maintain UID/GID consistency

We have a lot of users on our AD domain, and the more we add the longer it takes to get a directory listing on my Linux servers. When I do 'ls -l' it might take 20 seconds before the listing starts. However, if I immediately do 'ls -l' again, it comes up quickly. I assume this is because samba/winbind is polling the AD domain controller on the first attempt. Is there any way to

We have three Windows domain controllers in our AD domain. They are DC01, DC02, and DC03. We have Linux (RHEL5 and 6) servers in the domain as well. The Linux servers are working fine with AD. However, they are currently configured in krb.conf and krb5.conf to use only DC01 for AD domain controller. if DC01 is down, Linux servers cannot authenticate. How do we configure the Linux servers to use

Does anyone know how I can tell which Kerberos libraries (MIT or Heimdal) my Samba was built with? -- Eric Robinson Disclaimer - November 13, 2008 This email and any files transmitted with it are confidential and intended solely for samba@lists.samba.org. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in

Our samba boxes are integrated with our Windows 2003 AD domain, with Windows servers acting as AD domain controllers. Everything is working fine, but in my krb.conf and krb5.conf files on my Linux boxes, I currently only have one Windows server specified as the AD logon server. If that server is down, I suspect that Linux users could not login. How to I specify more than one AD domain controller

There are three DCs in my Windows 2003 AD domain, but I have noticed that only one of them is referenced in my krb.conf and krb5.conf. Should there be a reference to one or two of the other domain controllers? If the DC goes down, how will my Samba/Winbind servers authenticate? -- Eric Robinson Disclaimer - February 27, 2011 This email and any files

======================================================== "Every once in a while, a new technology, an old problem, and a big idea turn into an innovation." Dean Kamen ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Major bug fixes include:

======================================================== "Every once in a while, a new technology, an old problem, and a big idea turn into an innovation." Dean Kamen ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Major bug fixes include:

========================================================= "Patience is bitter, but its fruit is sweet." Jean-Jacques Rousseau ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.7 release series. Changes since 4.7.7: -------------------- o Jeremy Allison <jra at

========================================================= "Patience is bitter, but its fruit is sweet." Jean-Jacques Rousseau ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.7 release series. Changes since 4.7.7: -------------------- o Jeremy Allison <jra at