samba - Mar 2004 - scandinavian letters or charset problem?

Hi!

This teamware mailclient (teamware.com) that we use at the office has 
problems adding files as attachments from our Samba 3.0.2a share. The 
attachment file browser sees the files but fails to add them as 
attachments (with an error message: "valid.stf - file not found" 
regardless of the file name in question). I tracked this thing down to 
scandinavian letters (if your mail client supports it you should see 
these ??????) in directory names.

example:
g:\some-directory\some-file.png        Works OK
g:\scandi???\some-file.png         Doesn't work.

Anywhere else in Windows XP samba directories work just fine with 
scandinavian letters. This is the only program that behaves like this 
and I haven't received any help from vendor or manufacturer and they are 
as amazed as I am.

Server is Samba 3.0.2a with winbind and the charsets are:
        dos charset = CP850
        unix charset = UTF-8

Clients are Windows XP/2k/NT and Teamware Office 5.3/6.0.

If you have experienced anything similar to this or could suggest a 
solution, please do so!

--
Pirkka

On Thu, 2004-03-18 at 06:20, Pirkka Luukkonen wrote:
> Hi!
> 
> This teamware mailclient (teamware.com) that we use at the office has 
> problems adding files as attachments from our Samba 3.0.2a share. The 
> attachment file browser sees the files but fails to add them as 
> attachments (with an error message: "valid.stf - file not found" 
> regardless of the file name in question). I tracked this thing down to 
> scandinavian letters (if your mail client supports it you should see 
> these ??????) in directory names.
> 
> example:
> g:\some-directory\some-file.png        Works OK
> g:\scandi???\some-file.png         Doesn't work.
> 
> Anywhere else in Windows XP samba directories work just fine with 
> scandinavian letters. This is the only program that behaves like this 
> and I haven't received any help from vendor or manufacturer and they
are
> as amazed as I am.
>
> Server is Samba 3.0.2a with winbind and the charsets are:
>         dos charset = CP850
>         unix charset = UTF-8
> 
> Clients are Windows XP/2k/NT and Teamware Office 5.3/6.0.
In the same way that Samba has had to deal with the move to unicode, so
have many windows applications.  In windows, the transition is to a new
collection of 'W' functions, for 'wide' character set.  This is
a lot of
work, and many applications instead convert back and forth to the old
ASCII or OEM code page.  If your user's profile/localle is incorrect,
then this might be part of the issue.  The correct solution may be for
your application to be at least partially recoded using these
functions...

How well does this work against a win2k server?  If it doesn't fail,
then we have something more fishy going on...

Andrew Bartlett

-- 
Andrew Bartlett                                 abartlet@pcug.org.au
Manager, Authentication Subsystems, Samba Team  abartlet@samba.org
Student Network Administrator, Hawker College   abartlet@hawkerc.net
http://samba.org     http://build.samba.org     http://hawkerc.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.samba.org/archive/samba/attachments/20040318/b4a7730c/attachment.bin