similar to: Problem : same mangled name for different files

Hello samba-users, I have a problem with mangled-name-collision : I have 2 files with long filenames on a samba-server (V2.07, solaris). The filenames are xxxxx_APB.h and xxxxx_SEL.h For some reason the first part of the name has to be xxxxx_ The mangle name of both files is XXXXX_~5X.H (look at the fileproperties in explorer) That means to me, that the hash-algorithm, which generates the

Hello samba-list-reader, why is samba v2.0x worse than v1.9.18p10 with respect to NT-authentification with security=server ? I have exactly the same smb.conf on two servers, one running samba v2.04b and the other running samba v1.9.18p10 (Sun Solaris2.6). With v1.9.18p10 everything works fine since months. On the server running v2.0x in about 10% of all NT-authentification-tries (with net use

Hi Samba-gurus, I have a problem with samba 2.0.0beta4 on solaris 2.5.1 (samba 1.9.18p10 behaves the same) : 1. I have a ordinary text-file on a samba-share (foo.txt). NT4.0 sees the samba-share (\\sun100\tmp) as a netdrive with the letter K:. I've done a 'net use k: \\sun100\tmp'. 2. I can doubleclick in NT4.0-explorer on foo.txt and notepad comes up correctly. 3. I

Hi I just installed Samba 2.0.4 under Solaris 2.5.1 Now when someone trys to save a MS Word file to his home directory on the SUN he gets a "not enough permissions" msg. Looking on the unix side I see a file ~WRD1741.tmp with permissions of 000 . I upped the log level to 3 and found this .. call_nt_transact_set_security_desc: file = forNT/~WRD1741.tmp, sent 0x7 [1999/05/19

I''m having problems with filenames being mangled when uploaded - usually truncated either upto or after some problematic character. Here''s an example: Filename in filesystem: s+o~1@#%^&*()_-=[]{};:''".txt uploadedfile#original_filename: s+o~1@#%^&*()_-=[]{} Is this a rails/cgi.rb issue or a browser one? I note that gmail''s "attach file"

I''ve been going through the excellent tutorial in Agile Web Development With Rails, and hit a bit of a snag. After doing the ''pretty listings'' functionality for the Admin controller, attempting to click ''Show'' next to a product produces an error: ''Couldn''t find Product with ID=#<Product:0x276180c>'' Further, the URL of

I am using a recent version of Samba mounted through GVFS. If I configure with the option "mangled names" unspecified, I am able to access everything fine, but files with ':' or '?' get mangled to the point of unusability. If I specify "mangled names = no", I see everything fine with the reserved characters displayed properly, but I am unable to list or access

Hello, after upgrade Samba from 1.9.17p4 to 2.0.7. I have problems with name mangling. In one directory I have these files (only): 0011_BAR_ISSUEAGRES.CSV 0011_MIR_STKGEN.CSV 0011_OLO_ISSUEMPSPEC.CSV 0011_RET_ISSUEAGRES.CSV When I look at these files (DIR /X) from Windows95 or WindowsNT Workstation 4.0 clients I can see this: 0011_~%Y.CSV 0011_BAR_ISSUEAGRES.CSV 0011_~$%.CSV

Turns out we used a misaligned long instruction near the end, and the shader was getting killed after writing R, A components. This has gone unnoticed since the remaining G, B outputs aren't actually used. --- src/nv50_accel.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/nv50_accel.c b/src/nv50_accel.c index 5fa539c..1218e18 100644 --- a/src/nv50_accel.c

Hi All, I am doing some work to extend the target library information and ran across some function names in the old simplify-libcalls pass that are prefixed with \1. For example: \1__isoc99_scanf \1__isoc99_sscan \1fopen64 \1fseeko64 \1fstat64 \1fstatvfs64 Where do these \1 names come from? What target triples are they expected on? -- Meador Inge CodeSourcery / Mentor Embedded

On 19.01.2018 04:35, Adam Weinberger wrote: > Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. > It seems to be happening when I use vnd.dovecot.filter. When I comment > out the block, things come through fine. > > My filter block looks like this: > require "vnd.dovecot.filter"; > filter "bogofilter_filter"; > >

Hi all, while working with Netbench I've discovered that mangled directory names clash rather frequently with Samba 2.2.4: If I take an NT box, open the cmd prompt and make the following directories on a Samba share, client100 and client121, both mangle to CLIEN~GH. If I create directories client100 through client130 I see 11 clashes altogether: CLIEN~GH: client100 client121 CLIEN~MF:

Hi, I have a Samba 2.2.3a-6 server running on top of Debian Woody. There are two things I still have problems with. Number one is case mangling. I have set "mangle case = Yes" in [global] and left all other options related to case at their default and it works to some extent. But for example I cannot rename "whatever.txt" to "WhatEver.txt". The way it works is

Hello, In samba 2.x, I had no problem with DOS name mangling. For example, if a file named 0613abcdefg.txt, it will be mangled as 0613ab~1.txt. It is very easy to know which file it is. But now in Samba 3, the mangled name is very strange, "0AFADF~1.txt", I have no clue to know which file it is. But I didn't see any configuration parameters to deal with this problem, anyone can

Is there a different behaviour to mangled names in 3.0.x over 2.2.8a? When we double-click on the following reg file: m:\xpapps\hvcc\reg\visstud\hkcuvccomb.reg We get a registry editor error: Cannot import m:\xpapps\hvcc\reg\visstud\HSCNGB~G.REG: Error opening file. There may be a disk or file system error. when I set "mangled names = no" is behaves as expected. This behaviour is

We are currently using Samba V. 3.0.21b. My question is that we are running samba on our UNIX server (Solaris 9) where we have directories that look similar to the following: A.L. E.A. T.A. You can either view the directories as they are suppose to appear, except the users can't access the data. OR The directories appear as mangled names but the users have no idea which directory they

Greetings, all! We are having problems with file dates getting set incorrectly when we update a file from Windows. We are using Samba 3.0.2a on a Solaris 10 (0508 distribution) server, accessing from Windows XP SP2. When we edit a file on the automount from a Windows box, the file creation date, file modified date, and file accessed date all get set to the current time (as shown in the Windows

Hi, On Wed, Dec 10, 2014 at 11:10:36AM +0100, Markus Doits wrote: > I have a unix server (arch linux) with samba 4.1.14. The share has files > inside which where created directly on the server. Linux and OSX > (10.10.1) clients should access the share and store files. > > When I mount this samba share into the osx client (10.10.1), files > created directly on the server with

Hi Within a folder that forms one of my shares is a folder named "MCMXC_a.D.". At least, that is what I see when I run `ls` at the terminal, or even `ls -b` or `ls -q`. That is also what I see from another Linux machine using cifs to mount the share. However, from Windows clients this particular folder appears as "M6HK2P~F". This share is also mounted as external storage

I create a Bootdisk from Win98 with "sys a:" and the netsetup from the Microsoft FTP-server to have TCP/IP under DOS. I can map the shares from Samba to a drive with: "net use d: \\server\win98" The problem is that all long filenames are mangled, but not in the way DOS does it. The Folder "Program Files" does not become "Progra~1" but "Progr~4Z".