similar to: What setting determines filename character mapping?

Hi, I'm running samba 3.0.0-15 and have noticed that when users save some files the filenames get transposed. This is usually when they use special characters like the '?' (transposed to '#'). Looking at my smb.conf I found the following settings: # testparm -v | grep -e char -e code dos charset = CP850 unix charset = UTF-8 display charset = LOCALE

Unfortunately that didn?t work for me! I think there may be a bug somewhere although its possible that I have done something wrong somewhere. My reason for saying this is everything works perfectly when the windows machine is "uploading" the files but not when rsync is copying them. Regards Nic Colledge colledge@dsl.pipex.com n.j.colledge@bradford.ac.uk -----Original

Hello! I've got a Buffalo Linkstation HD-HLAN250. This is a consumer NAS device, which makes the built-in HD accessible via SMB and FTP. On that system, some sort of Linux with some sort of Samba is running. I'm now trying to create filenames with special characters (ie. non-ASCII chars) in it. For example "bl?der name" (means "stupid name"). To get access to the

I've just compiled Samba 3.0.0 on a Solaris 8 system (gcc, if it matters), and whenever I run anything from the samba suite, I get a series of error message about character set conversions: Conversion from UCS-2LE to CP850 not supported Conversion from UTF8 to CP850 not supported ... and about 10 more, all involving CP850 (the "standard" DOS codepage, presumably). Now,

Hello, we have some strange things with samba 3.0.2a, AIX5.1, ML03: 1. ./configure --prefix=/usr/samba : : checking for iconv in /usr... yes checking can we convert from CP850 to UCS2-LE?... no checking can we convert from IBM850 to UCS2-LE?... no checking can we convert from ASCII to UCS2-LE?... no checking can we convert from 646 to UCS2-LE?... no checking can we convert from UTF-8 to

Hallo, I know this problem is marked as solved, but here is another solution, a solution which makes it possible still to use smbfs. I have been working on a project connecting Skolelinux ltsp-server to a windows 2000 server in norwegian secondary school and came across the same problem ( that is one of the teachers and his students in my school did first). Searching the net I found the

I don't think there is anything that can be done but.... In our Unix shares, we have multiple (hundreds) of filenames that have "*" in their names, which really messes up W95 when I attempt to display the contents of those shares. Is SAMBA not passing the filenames correctly or W95 is just not reading them correctly? Any ideas? on either side. (except changing the filenames to not

I can't use a ? (forward tick, accent acute) in a filename on a samba share. Is this an error or intention? If i copy a file with ? to the samba share the result will be, the tick will be converted to a capital Z with back and forward tick on it and the rest of the filename is dropped. samba 3.01rc1 [global] dos charset = CP850 unix charset = ISO8859-15 display charset = LOCALE [raid2]

On Mon, 15 Feb 1999 23:47:50 -0500, Guy Dallaire wrote: ... >When I try to access a file or a subdirectory under the share, I get a message telling me "File not found", >or "this folder does not exist". > >I tried all sorts of upper/lower, preserve, case combinations in smb.conf, nothing seems to work. I tried >with debug level = 3 and I noticed a lot of

Hello all, I have a problem with the display of filenames > 80 chars when served by Samba-3.0.0 to Windows clients. System: GNU/Linux debian 3.0.1 upgraded to testing/unstable on ALPHA processor (XP-1000), Kernel: custom 2.4.22 + acl support (kernel pkg could only be compiled by downgrading binutils to 2.12.90 & using gcc-3.0) Samba: Samba-3.0.0.final.deb (testing/unstable) smb.conf:

Hello, I?m using samba version 3.0.1-Debian rsync version 2.6.0 protocol version 27 And mount version 2.12 With kernel 2.4.22 As far as in aware these are the latest versions in Debian unstable. The problem im having is when mirroring my mp3 collection file names with characters like ? ? ? etc. are not displayed in the linux filesystem and then when browsing to the directory through samba

Hello all. I have been given an assignment to mount a share automatically for each user using a given Linux machine (Mandrake 10 in this case). This is working fine, thanks to pam_mount, BUT: The mounted share contains national characters like this: ? ? ?. The problem I'm having is that when I mount these on Linux the '?' looks like 'o' but cannot be accessed like that. It

Seems to be working very nicely (and what a relief to see it actually working!), I've found only a few problems till now: a) Characters outside 0-0x7f seem to get encoded as CP850 or something, not Latin 1 (æøå keys on DK keyboard gives mu,degree,sigma). b) Infinite recursion crashed R. (I forget details, but it was something stupid like f<-function(x){if (x < 1) 1 else f(x)*(x-1)})

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

[sorry for my maybe newbie Qs and using this group for my busybox issue but though having visited some forums about this I'm getting nuts] I unslugged a Linksys NSLU2 device with V2.3R63-uNSLUng-6.8-beta as I plan to use it as a DC replacement for my W2k server at home. But I already got stuck before this. Following the unslinging I installed the Samba3 IPKGs for the NSLU guided by the hints

Hi, I am well aware that the charset problem has been discussed many times over. But after two days of googling and testing, I did not make any progress. I am mounting Windows XP Pro shares with french filenames on a Linux. The linux is a 2.4.27 kernel with the following settings: CONFIG_SMB_FS=y CONFIG_SMB_NLS_DEFAULT=y CONFIG_SMB_NLS_REMOTE="UTF8" CONFIG_SMB_NLS=y CONFIG_NLS=y

Hi @all... Following configuration i used before samba 3: character set = ISO8859-1 codepage = CP850 I could read an write files with umlauts from my Win2k Client. Doing an ls at the linux console showed a ? (question mark) instead the umlaut, but using mc (Midnight Commander) shows the right char. I was quite happy with this setup. Now, with samba 3.0.0final-1 (from Debian/sarge), I tried

Problem: We have a share defined using Samba 3.5.8 on AIX 6.1. Several people can map a Windows Network Drive to the share and it works fine. Several other people get Windows errors or system errors when trying to map a drive to the same share. Command line errors (from the net use command): System error 59 or System error 64 Windows Explorer error: The specified network name is no

Hi, I'm a french student from Ecole des Mines of Nantes. Students of my engineering school live in a residence with its own local network, access to sun workstation at school for working and a Internet access througth a firewall. In each room of the residence, we have a RJ25 plug. We just need a network card and a computer to go on this network. As you can expected, our network is a jungle

Running samba 1.9.16p11 on Digital Unix 3.2c. We currently access unix shares from W95 without problems but now since we had our network overhauled, 2 MSDOS harddriveless PC's need to be able to access the unix system for it's hard drive. They have Intel Express cards . How do I setup the MSDOS computer to map a drive to SAMBA. One question is these computers do not have IP addresses, how