similar to: DOS style 8.3 filename mangling issues??!

Dear all, I have used the Samba 2.2.8a server. mangle method = hash or hash2 But when i make a "dir" command on the MS-DOS prompt, the file name aren't the same from a disk on DOS local partition and Samba Server partition. :-( File name on the Windows view: ESTE_DE_NOME_BEM_GRANDE.TXT DOS prompt on the Samba Serve Partition: TESTE~65.TXT DOS prompt on the DOS local Partition

Iztok Polanic <iztok@hakl-hakl.si> carved some runes like this: > > 1. I have just installed samba on my computer. It works great and > > I can mount all Windows computers, except NT. When I try > > "smbmount //192.168.1.4/C /mnt/test" I get this error: > > > > Password: > > smb_get_length: Invalid NBT packet > >

Does anyone know how to tweak or disable filename mangling in Samba so windows clients don't read paths and folder names in 8.3? I have a few backup VBscripts that used to work by passing the name and path of a directory (on a Samba share) as an argument to be read by the script. Currently, on some windows 2k boxes, the full path and folder name are displayed correctly and named correctly

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

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

Here's an interesting thing I notice between NTSP3 and Linux 2.0.33+ w/samba 1.9.18p8 [TCP_NODELAY, read prediction on, SND and RCV buffers to 64k, though I've tried 16k, 32K, 64k, max size 2k, 4k, 8k, 16k, no difference] When I copy a file from any share to my NT's HD, I get perhaps 280KB/sec. When I copy from NT HD to Samba share, I get almost 1MB/sec. Doesn't matter where

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,

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

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

I am having a bit of a problem getting AMD to work on a new server. On my regular office server it works like a charm. I am running Asterisk 1.4.13, Zaptel 1.4.5.1 on both machines. Both servers run CentOS 5 and I am using a SIP trunk to send out calls (the same one on both servers). Here is the output of a call on my office server: -- Attempting call on Local/0445540881644 at CC2 for

Hi all Please CC me any replies. I am currently running samba 2.2.8a under Slackware 8.1 (kernel 2.4.18) to provide fileserver services to a number of windows 2000 boxes via a single "resources" share. One of the things stored in this share is a collection of Protel libraries used in electronic circuit design. The problem is that protel implements its own access control mechanism for

If i use AMD() or the code below, now the problem is the fax machine/modem detection and answer machine detection get detected as the same. If i need to seperate the two how do i do that? For example, if i use AMD() to detect an answer machine by saying any greeting exceeding 2.5 seconds is a machine, how do i distinguish between a fax/modem and a long greeting? ---- dave cantera

Hi everyone: I use the protel CAD software. In early versions this work well, but in this version i got a little problem Whe execute in terminal appear this into the screen, no other message no fixme, no warning only this fixme:int:WIN87_WinEm87Info (0x7e285aee,12), stub ! But the things that must appear at the botom of window have a extremly big bottom border. so big that i cant see the

> This problem was occurring on 19p8 so I moved to samba 2.0.0 yesterday in > hopes it was a bug > that had been solved... All the information I am supplying relates to > version 2.0.0. The only change > I made to my global.conf file between the two versions was to remove the > socket option IPTOS_THROUGHPUT. > > We have a large number of zip files named

Hi, I'm configuring samba-3.0.2a-Debian. I have it configured with LDAP. I get samba decline access for a W98 clinet when using user authentication (NT domain), and the following entries get into /var/log/smb/machine.log: -------------------------------------------------------------------- [2004/05/07 13:46:07, 3] smbd/sesssetup.c:reply_sesssetup_and_X(772) Domain=[WORKGROUP]

I'm not sure if this is a samba problem or just a problem with the app. I'm unable to an application from a shared drive "\\ucd01\protel\". I've mapped the network drive "k:\protel\"and the apps ini file points to it but gives me an error message suggesting it can't see the drive. XP can however and I can browse it in explorer. A strange thing is that when I

Sorry about the direct post.... >Date: Thu, 06 Apr 2006 08:38:39 -0500 >To: "Chris Boyd" <Chris.Boyd@usit.ie> >From: Eric Hines <eehines@comcast.net> >Subject: RE: [Samba] Not able to join domain > >At 04/06/06 08:13, you wrote: >>I've tried that and now I get "Access denied" instead "cannot find >>user". Also I'm

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

I have a SIP line that is working fine when I make calls from IP phones. I can send and receive calls. The problem is that if I try to dial from the CLI using the originate command or use an AMI connection to originate a call I get the following error: originate SIP/protel-out/0445540881644 application playback tt-monkeys WARNING[12950]: chan_sip.c:20437 handle_response_invite: Received

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