"-rw-r--r-- 1 root root 0 Dec 29 21:57 tÃ¶rÃ¶
-rw-r--r-- 1 root root 0 Dec 29 21:57 törö "
It seems the server converts characters into utf-8 encoding. "törö" is the file name in local iso-encding and "tÃ¶rÃ¶" is what davfs2 got from the server. (utf-8 encoding of 'ö' is C3B6 which looks like "Ã¶" when interpreted as iso-encoded characters). The dir entry "törö" is probably served fromt he kernel-cache (using coda?). davfs2 removes this entry as soon as it notices that no file with this name exists on the server.
When törö shows up as "tÃ¶rÃ¶" on the FritzBox this shows that the file name is utf-8 encoded, as it should be for Windows. But most probably Samba does code conversion too, interpreting 'C3B6' as two iso-characters and sends the utf-codes for 'Ã' and '¶' instead.
How to proceed:
You need access to the FritzBox.
Turn of the use of property "displayname" (davfs2.conf option "use_displayname o"). This should not change anything but will avaoid possible confusion in the future.
As Samba seems to convert from local iso-encoding to utf-8, davfs2 will have to convert from server's utf-8-encoding to local iso-encoding. Set option "server_charset utf-8" in davfs2.conf.
If this does not help it would be useful to have:
- directory listing done on the FritzBox
- listing of the same directory from the Windows client
- captured HTTP-traffic between FritzBox and the server. A PROPFIND-request for this directory and the response from the server would be the best.
Looking at http://www.ip-phone-forum.de/showthr...179968&page=2:
FritzBox seems to use its very special way to configure davfs2. Have you got any documentation about this?