Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I got a DNS313 and have seemingly set it up. I created a group, a user, added the user to the group and gave read right permissions on Volume_1 to the user. If I try to transfer a folder from Windows over samba it will go fine, but if I try to transfer the same folder from osx (Leopard) I get an error message like this:
Actually it seems I get this error from almost any files I try to transfer, but some do go through. I have not found any logical explanation on what is causing this.
Note: before posting this message I did search on the forums, and found mentions that OSX users might have problems with filenames. I did not look at the file names very much, it's possible there where some with äö charecters in the name.
Anyone have a clue on what's going on?
edit: FTP works fine, it's just quite a bit slower (6MB/s vs. 9MB/s on samba)
Last edited by dropadrop (2007-11-14 09:43:24)
Offline
Ok, I'm back home and did a bit more debugging. The name of the file does not affect this issue. I have two files, both have the exact same rights (they are in the same folder). I can move one of them, but not the other. I tried changing the name of the one I can not move to be exactly the same as the working one, but it did not help.
Originally the permissions are:
-rw-r--r--
I changed them so everyone can read and write, no difference. In my log I get the following every time I get the error:
smbfs_composeacl: smbfs_setattr 13, ignored
edit:
I tested moving a file that I can't move with a windows virtual. Then I used osx to copy the file to my desktop, delete it from the share and copy the new file back... But I get the same error message.
Also ääöö letters work fine.
Last edited by dropadrop (2007-11-14 17:15:39)
Offline
Apparently D-Link found a problem too, they sent me a beta-firmware for testing. Unfortunately I already returned the device to the store I bought it from.
Offline
You probably want to apply the latests update for Leopard. SMB fixes in it....
Offline
dropadrop what was the newer version number of the firmware they sent you?
Offline
frodo wrote:
You probably want to apply the latests update for Leopard. SMB fixes in it....
I did, no effect. On later testing I was unable to move any files to the 313. One reason I was probably confused before was that the error would come at the end of the transfer. Hence all smaller files would give a direct failure message, larger ones would seem like they go through (I manually cancelled due to impatience).
Offline
dropadrop wrote:
frodo wrote:
You probably want to apply the latests update for Leopard. SMB fixes in it....
I did, no effect. On later testing I was unable to move any files to the 313. One reason I was probably confused before was that the error would come at the end of the transfer. Hence all smaller files would give a direct failure message, larger ones would seem like they go through (I manually cancelled due to impatience).
You tried with 10.5.1? It was released on the 15th...
Offline
gareth wrote:
dropadrop what was the newer version number of the firmware they sent you?
1.01B4
ftp://dlinkTEMP:dlink@194.117.170.198/DNS-313_1.01b4/
Last edited by dropadrop (2007-11-18 13:54:13)
Offline
frodo wrote:
dropadrop wrote:
frodo wrote:
You probably want to apply the latests update for Leopard. SMB fixes in it....
I did, no effect. On later testing I was unable to move any files to the 313. One reason I was probably confused before was that the error would come at the end of the transfer. Hence all smaller files would give a direct failure message, larger ones would seem like they go through (I manually cancelled due to impatience).
You tried with 10.5.1? It was released on the 15th...
Yes, it was released on Friday and I installed the update right away. It did not make any difference. After I found it did not make a difference I returned the device... Once I got back home from the shop I had an email with the beta-firmware waiting for me in my inbox. The problem is also present with Tiger (I only have a mac with Tiger and another with Leopard so can't try anything else). Aparently D-Link also found the problem since they where able to send me a beta-firmware with the problem (aparently) fixed. Note, that I have not tested the beta-bios.
I'm still not impressed by D-Link, I don't understand how the DNS-313 has been added in the "compatible with macs" document when:
- You can't initialize it without the application on the cd (windows only)
- Nobody had apparently tested samba connections with a mac that had an operating system released within the last 3 years.
Last edited by dropadrop (2007-11-18 13:59:30)
Offline
I still have this problem with 1.01B4 on my 313 and Mac OS 10.5.1. 1.01B fixed it for my wife's Mac running 10.4.10, however.
Offline
I've updated with the newest availeble FW from Dlink (1.01b6 today) - still the same problem. What I have seen is when doing copying using terminal and the cp command there is no problem writing to the Dlink. Is it a Leopard bug and not Dlink ?
Offline
fossaaen wrote:
I've updated with the newest availeble FW from Dlink (1.01b6 today) - still the same problem. What I have seen is when doing copying using terminal and the cp command there is no problem writing to the Dlink. Is it a Leopard bug and not Dlink ?
Probably it is a Leopard issue. More precisely, the issue is probably that Dlink does not have a mac with Leopard for testing
I think the fact that this device was on dlinks "compatible with mac" even when it did not work with with Tiger or Leopard tell's me a lot. My leopard machine works fine with Linux and Apple samba shares at work, and with Samba on the Qnap I bought to replace the DNS-323.
Offline
Seems that new b6 firmware is damaged for me for some reason, can´t open the archive
Anyway, is there a changes file inside ?
I´m curious if this fixes the power management issue
Edit:sorry. the tgz file is the firmware. its v 1.01 and got it updated.
No help for the power management
Last edited by pta (2008-01-12 13:14:21)
Offline
fossaaen wrote:
I've updated with the newest availeble FW from Dlink (1.01b6 today) - still the same problem. What I have seen is when doing copying using terminal and the cp command there is no problem writing to the Dlink. Is it a Leopard bug and not Dlink ?
Hi, do you have any other bad or good experience with this firmware please? Better transfer speed, built-in bittorent client?
Thanks.
Offline
Don't notice any differance from the earlier versions except telnet is removed from this release and I think day have changed the selectable time for Power Off Hard Drive (now 10,20,30mins and 1 and 2 hours. Seems to me that this is still not working anyway. Still slow, not working on OSX and no torrent download.
Offline