Invalid packet length

[Dmitry Melekhov]

Jeremy Allison wrote:

Hello!

> Ok - if you too (and anyone else who has seen the "invalid packet"
> problem after turning on large read/writeX) could CVS checkout
> and test again, I think I have fixed the problem.
>

:( No file copy is still very slow. Yes, there is no such error, as
before.
Now I only see in log:

2001/05/25 08:40:13, 5] lib/util.c:show_msg(298)
  smb_tid=4
  smb_pid=65279
  smb_uid=101
  smb_mid=7617
  smt_wct=1
[2001/05/25 08:40:13, 5] lib/util.c:show_msg(303)
  smb_vwv[0]=0 (0x0)
[2001/05/25 08:40:13, 5] lib/util.c:show_msg(308)
  smb_bcc=0
[2001/05/25 08:40:13, 6] lib/util_sock.c:write_socket(560)
  write_socket(15,41)
[2001/05/25 08:40:13, 6] lib/util_sock.c:write_socket(563)
  write_socket(15,41) wrote 41
[2001/05/25 08:40:13, 10]
lib/util_sock.c:read_smb_length_return_keepalive(602)
  got smb length of 65584



>
> I've CVS committed code into HEAD and 2.2 that can cope with
> a full 64k of data in a writex packet, and this should now work.
>
> If you could transfer large files from UNIX -> NT and back again
> under a different name, and then do a checkum (sum) on the files
> to make sure they're ok, I'd appreciate it.
>

I'll send you full level 10 log.

--
Wire connection and Windows reinstallation senior engineer
Dmitry Melekhov
http://www.belkam.com/~dm
2:5050/11.23 at fidonet