Displaying 20 results from an estimated 2000 matches similar to: "Question about DOS 8.3 mangling files name"
2004 May 06
0
SMBCLIENT: error on mounting
Dear all,
I use smbmount on a script. The package used is (SuSe 7.2):
"...
root@gprod:~ > which smbmount
/usr/bin/smbmount
root@gprod:~ > rpm -qf /usr/bin/smbmount
smbclnt-2.2.0-15
root@gprod:~ > ls -l /usr/bin/smbmount
-rwsr-sr-t 1 root root 497224 May 12 2001
/usr/bin/smbmount
root@gprod:~ >
..."
This script runs on crontab each 20 minutes.
It uses the
2004 Dec 29
1
smbpasswd
Dear all,
How can I convert the Linux users password (/etc/shadow) to Samba users
password (.../private/smbpasswd)?
Best Brazilian regards
--
Rodrigo Noroaldo de Castro Fernandes
r.fernandes@darumaorga.com.br
2004 Nov 02
2
Wierd 8.3 Name Mangling
I've installed Samba 3.0.7 (stock Debian package), but I'm having some
wierd problems with name mangling. The relevant lines in smb.conf are:
preserve case = yes
short preserve case = yes
mangled names = yes
mangle prefix = 5
mangling method = hash2
In a share, I did "touch test-file.GHO" to create a long filename. When
I do a "dir" under DOS,
2007 May 21
0
cups, firefox + acrobat (getting strange output)
I think this isn't plj output. Please take a look :
document printed from Foxit Reader(PDF), all works fine:
LINK: http://img526.imageshack.us/my.php?image=digitalizar10001rw2.jpg
error_log output using Foxit Reader:
D [18/May/2007:13:27:58 -0300] cupsdAcceptClient: 9 from localhost:631 (IPv4)
D [18/May/2007:13:27:58 -0300] cupsdReadClient: 9 POST /printers/teste_ HTTP/1.1
D
2013 Oct 03
2
name mangling makes 8.3 unreadable unlike Windows fileserver
Hi,
I'm cross-posting here from serverfault.com in case anyone can help. I
just found a similar question on askubuntu.com also without an answer.
Switched recently from W2K3 to Samba4.0.9/CentOS6.4 for our fileshare
for WinXP clients.
Have an ancient (1995!) piece of software that uses 8.3 filename format.
After the switch, long filenames became useless in the context of the
1998 Jan 26
0
DOS style 8.3 filename mangling issues??!
Okay, I've run through all of the tests in the DIAGNOSE, which my 1.9.18p1 SAMBA
server (and NT4SP3/W95 clients) pass with flying colours.
server box: Linux 2.0.33, gcc 2.7.2.2, libc 5.4.33, shadow, quota on (usr+grp),
and my smb.conf is summarised (by testparm output) below:
Problem is this: with respect to programs not long filename-aware/compliant,
users cannot "double-click" on
2013 Aug 05
3
Voicemail variables on email subject
Hi
I have a problem w/ voicemail, the subject message is corruption when used
voicemail variables, e.g. :
voicemail.conf
emailsubject=${VM_MAILBOX}|${VM_MSGNUM}|${VM_CALLERID}|${VM_DUR}
Return:
Subject: =?utf-8?Q?1504|12|=22Teste_-_Rafael=22_=3C1570=3E|0=3A16?=
Expected:
Subject: 1504|12|"Teste - Rafael" <1570>|16
Thank's
Att,
*Rafael dos Santos Saraiva*
Tel: (51)
2005 Sep 07
0
Dos Name mangling under 3.0.7
Hi,
I'm trying to get my samba to force 8.3 compliant names to lower case,
but they stay upper case.
I've tried adding mangle case = yes, but testparm reports unknown
parameter, while it is in the man page.
Was this a known issue? should I upgrade?
share definition
[sys]
path=/sys
writable=yes
force user = advantage
preserve case = yes
default case = lower
mangle case = yes
short
1999 Jul 26
0
8.3 name mangling options going wrong ?
I've just bumped into a name mangling issue with Samba which I'm sure
people have already found before me......
If you create 2 files called moss_burn.bmp & moss_bend.bmp on a Samba
share that has been mapped to a drive under windows then a 'dir' in a
DOS shell will show that the 8.3 filenames of these two files are
identical......MOSS_~UV.BMP... which is not good for legacy
2002 May 31
1
hash2 mangling alghorithm
I just want to warn people that want to use the new hashing algorithm
for mangled names.
And that note should also be put in the man page IMO.
You must understand that changing the hashing algorithm on a production
server may have unwanted side effects (this is why we maintain by
default hash and not hash2 and why it was not back ported to 2.2
initially).
Windows clients may save all around
2015 Jan 09
2
Name mangling problem
Hi all,
I run samba 3.6.6 from debian wheezy (version 3.6.6) and i am
experiencing some troubles with file name mangling.
If i try "dir /x" on a mapped folder it gives me unexpected mangled
names: the name mangling matches only the first character and not the
first 5 as i expect.
For example:
if the long file name is LONGFILENAME.TXT, i expect the mangled sholud
be something like
2007 Jun 21
0
ENC: Action Originate (Asterisk Manager) X Monitor()
Hi people! I need a help.
I connect with Asterisk Manager and execute an Originate Action that asks
for Asterisk to call for a number 09194**** and to transfer to peer 101.
This command enters in my dial plan extension that I made exclusively for
tests.
The problem is:
If I do the call through ORIGINATE Action, the Monitor() just makes the
record file, but this is empty, if I do
2020 Jul 06
1
Limit dirs/filenames to old 8.3 DOS convention
Hello all,
after endless searching for days you might be able to help.
In short: Is there a way to get Samba accept only 8.3 filenames and directory names on a share?
The problem: From a windows client a user should be able to save files on a destination (samba share) which aren't longer than the old 8.3 dos convention.
This is a requirement for a system behind it, which can only deal
2004 Feb 18
1
Samba 3.02 with dos filenames - still not working!
> m:\worksp~1, when I have this share on a windows machine, it works
> fine. Move it to my samba machine and it doesn't. This is what my
This is probably your problem. You override the default mangling method
in samba3 from hash2 to hash. hash2 behaves more like Windows mangling.
> mangling method = hash
Either take this line out or change it to hash2. You may need to
2011 Jan 06
2
Mapping characters for non-DOS names under UNIX
Hi All,
As known, samba can mapping non-DOS names under UNIX to DOS-compatible names
by using some HASH/HASH2 algorithm. But is there any way we can define a
character mapping tables by self, not using HASH? such as: (just a sample)
character mapping table:
Unix Windows
" <-------> a
* <-------> b
/ <-------> c
: <-------> d
<
2004 Dec 01
0
Problem with "mangling method=hash"
Hi,
I just tried changing a samba 3.0.9 server's config from
mangling method = hash2
to
mangling method = hash
and on a WinXP client I see a filename ".foo" change to it's mangled form
"FOO~00.___". Is this a bug?
--
Steve Bennett, Systems Support, Lancaster University
2002 Nov 07
0
Can't get 8.3 filenames to lower the case
Hi,
I seem to have some trouble on default lowering the case on 8.3
filenames. I use the following settings but sometimes I still get a
8.3-compliant file with uppercased chars in my unix filesystem.
default case = lower
case sensitive = no
preserve case = yes
short preserve case = no
mangle case = no
mangling method = hash2
Any thoughts?
BTW. using HP/UX 11.00
2003 Nov 03
2
upgrade 2.2.8a -> 3.0 Debian DOS long filename problem
Hi,
I tried to upgrade from Samba 2.2.8a to 3.0.
It worked generally speaking fine and speed went up tremendously,
BUT
since then the DOS conversion of long file names is freaking me out.
Using long file names produced a readable short version plus ~1 oder ~x.
where x stands for a number.
now long file names produce some cryptic 8 letter name plus extension.
listing in a DOS box
1998 Dec 18
1
Problem de mangling
Hi all !
I'm new on this mailing list...
We have just installed samba v1.9.18p4.
But we have problems with mangling of file names.
We would like to preserve the case of windows files > 8 char. when
copying files to the server. However, we want to keep 8.3 format files
in lower case.
The question is : how to configure all the
2005 Dec 20
1
File-name Mangling issue...
I want all the file-names to be stored on a samba share from my XP clients
to be automatically converted to 8.3 syntax, so that i do not have any
further problem while transporting those files over to other
networks/servers like netware.
As for now i am using these below mentioned lines to support file-name
mangling over my samba.
---------
#I do not want my filenames to be case sensitive,