G
Guest
Hello,
I need a clarification regarding the CAP_LARGE_READX
capability. According to CIFS spec(2002),
CAP_LARGE_READX/CAP_LARGE_WRITEX is upto 64K bytes.
What I understood from this is the SMB server can support
read requests of 64K data.
So I read a 1MB file using notepad application from client.
Colleced the ethereal traces for the following Client/Server
combinations.
1) W2K - WNT
2) W2K - W2K
But from the traces I could see that the maximum request
size was 32768 bytes. But in the negotiate SMB response
from SMB server, I saw that it announces the support of
CAP_LARGE_READX. But still client sends maximum of 32768
bytes. So is CAP_LARGE_READX is depending on any other
registry parameter either from client/server side? or
on any other factor?
Could anybody clarify whether my understanding is correct.
Do I am missing something here?
Thanks and regards,
Sundar Keshava
I need a clarification regarding the CAP_LARGE_READX
capability. According to CIFS spec(2002),
CAP_LARGE_READX/CAP_LARGE_WRITEX is upto 64K bytes.
What I understood from this is the SMB server can support
read requests of 64K data.
So I read a 1MB file using notepad application from client.
Colleced the ethereal traces for the following Client/Server
combinations.
1) W2K - WNT
2) W2K - W2K
But from the traces I could see that the maximum request
size was 32768 bytes. But in the negotiate SMB response
from SMB server, I saw that it announces the support of
CAP_LARGE_READX. But still client sends maximum of 32768
bytes. So is CAP_LARGE_READX is depending on any other
registry parameter either from client/server side? or
on any other factor?
Could anybody clarify whether my understanding is correct.
Do I am missing something here?
Thanks and regards,
Sundar Keshava