win2kp + iTunes -> samba share (Invalid packet length)

[kamui]

Hello to all at WL500g Forum & and thanks for all the helpful posts so far!

I have experienced the following problem using iTunes on a win2kp client trying to convert some music cd´s to my share on a USB2 HDD (Western Digital WDXB1600JBRNE) which mostly result in an interruption of the transfer. The filesystem on the HDD is ext3 and I am using olegs 1.9.2.7-6b: smb.log:

...
[2005/07/11 00:33:41, 0] lib/util_sock.c:receive_smb(659)
Invalid packet length! (65600 bytes).
[2005/07/11 00:33:41, 0] lib/util_sock.c:receive_smb(659)
Invalid packet length! (65600 bytes).
[2005/07/11 00:33:41, 0] lib/util_sock.c:receive_smb(659)
Invalid packet length! (65600 bytes)
...

This is the only problem I have experienced using samba on the 500gx so far, normal file transfer to the share, copying files and folders from the client to the share and vice versa works fine even large files (tried up to 2G so far).

At first I suspected windows CAP_LARGE_READX and CAP_LARGE_WRITEX, but I´m not so sure anymore.

The only useful hint google revealed to me is the following link, concerning an old samba problem back in 2001:

http://lists.samba.org/archive/samba...ay/014199.html

My smb.conf right now is default except the share is "writable = yes", but I already tried some tuning of the smb.conf my self, various "socket options", max xmit ...etcetera without success.

I hope someone here can shed a little light on the problem.

Regards,
Kamui

[Oleg]

hm... yes, this appears to be bug. I will try to locate and back port a fix...

[kamui]

That would be most appreciated. Thank you.

Regards,
Kamui

[wolf777]

I am experiencing the same "invalid packet length" problem. I have WinXP Pro SP2 and Asus WL-500b with the latest Oleg's firmware (1.9.2.7-6b).

When I try to copy the data on samba shared disk, I get error in windows tray saying the data was lost, possibly due to hardware failure and blah blah :-) The files would get corrupted (nulls are written sometimes instead of data).

This problem occurs only in 6b firmware, I don't get it in 6a. Also, the problem doesn't occur neither in 6b firmware if the size of the file copied is lesser than 1 MB (I am not sure if that 1 MB threshold is precisely 1024^2 bytes, but it must be very close).

[Oleg]

Fixed already. Wait for -6c.

[Biko]

Fixed already. Wait for -6c.

When would the -6c version become available?

[new23]

I have the same problem. How can i fix it without new firmware? possible or not?