similar to: Intermittently Get "Target filesystem does not supportlong file names" when copying file to Samba share

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 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

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

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

We have about 40 samba servers in our domain. The two newest ones are throwing an error we've never seen before. [root at vmhost06a samba]# net join Enter root's password: dos charset 'CP850' unavailable - using ASCII convert_string_talloc: Conversion not supported. Failed to join domain: failed to lookup DC info for domain 'MYCHARTS.MD' over rpc: Memory allocation error

Attempting to install a fully virtualized instance of Windows 2003 fails on CentOS 5.2 x86_64 with xen-3.0.3-64.el5. After issuing the command... # virt-install --hvm -s 70 -f /vm/ts05/ts05.dsk -n ts05 --cdrom /download/Win2003x64/disk1.iso --vnc -r 1024 The script just hangs at... Creating domain... In another terminal window, I can see that vnc-viewer has been started and is

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 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

Hi, I resolved the problem. I changed my smb.conf as follows: [global] netbios name = SAMBA server string = %h workgroup = DOMAIN.TLD security = user encrypt passwords = true ldap passwd sync = yes guest account = nobody passdb backend = ldapsam:ldap://zarafa.hasselt.be ldap admin dn = cn=root,ou=hasselt.be,o=hasselt,c=be ldap suffix = o=hasselt,c=be ldap group suffix = ou=groups ldap user

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

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 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

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

On Tue, 2018-05-15 at 13:04 -0500, Chris Adams wrote: > Once upon a time, Adam Tauno Williams <awilliam at whitemice.org> said: > > Rules load automatically via the /etc/sysconfig/network- > > scripts/rules- > > {interface} files.??Routes added to /etc/sysconfig/network- > > scripts/routes-{interface} are always added to the default policy. > What are you

I've been struggling for almost 2 weeks to get Samba working on two new servers. When I try to open a Samba share from a Windows 2003 computer, I always get a logon challenge. I always get the following lot message [2008/11/13 16:05:06, 3] lib/util_sid.c:string_to_sid(228) string_to_sid: Sid MYDOMAIN\mygroup does not start with 'S-'. [2008/11/13 16:05:06, 2]

Does anyone know how can I monitor files that was being open and access in the samba directory? If this was not possible, is there third party apps that can help me do what I want? -- Nelson Serafica http://nelsontux.blogspot.com

Am Donnerstag, 10. März 2016, 10:41:34 CET schrieb mathias dufresne: Hi, Mathias and all thank you for your answer. > Hi all, > > SPN = servicePrincipalName > > A simple search returning all servicePrincipalName declared in your AD: > ldbsearch -H $sam serviceprincipalname=* serviceprincipalname > For me: ldbsearch -H /var/lib/samba/private/sam.ldb serviceprincipalname=*