Displaying 4 results from an estimated 4 matches for "sizreqbuf".
2000 Apr 05
1
How customize samba for large directory
...mes
and a buffer to 16387 octets.
Do you know a way to change this ?
I tryed without result,
max xmit = 60000
packet size= 60000
For dialog Window/Window I change on the server side the registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
SizReqBuf to 60000 and a NT (server file) become faster.
Have you information for smb.conf files .
Thanks a lot for your help.
Gilles Noyer.
2006 Jan 12
0
Max Buffer Size vs Max Raw Buffer question...1GB tuning questions
...ows xp workstation, I've added these registry keys and
rebooted:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"TcpWindowSize"=dword:3FFFF700
"Tcp1323Opts"=dword:3
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"SizReqBuf"=dword:0000FFFF
"TcpWindowSize"=dword:3FFFF700
Now, normal communications with the samba server work great... 8960 tcp/ip
frames instead of 1460, and I'm getting around an ack for every two of
those which is odd considering the Window Size I've got set, but I think
that has...
2003 Feb 19
2
Win2K/XP, oplocks, and readahead.
...rite of a single file?
4. Is there any way for samba to send unsolicited readahead data to the
Windows client when an oplock has been established?
5. Any samba tricks for debugging this?
In terms of registry keys I've already changed those for window sizes,
MTU, UseOpportunisticLocking, SizReqBuf (to 64K), EnablePMTUDiscovery,
MaxCmds.
Here's my samba configuration:
[global]
encrypt passwords = yes
log file = /var/log/samba.log
max log size = 100
local master = no
read size = 8192
# below socket sizes have been varied without effect
socket options = TCP_NODELAY IPTOS_LOW...
1997 Dec 06
1
OS/2, DOS LanMan, Amiga and Solaris 2.4 patch for Samba
...upported for by LANMAN2.1 and higher dialects. So I had to think of something else. I came up with using the "max xmit" setting. The SMB clients that are available (DOS, Windows, OS/2 etc.) seem to use distinctive default values for this maximum buffer size setting. In OS/2, the line
> sizreqbuf = 4096
> in the [peer] section of \IBMLAN\IBMLAN.INI sets this default. It corresponds with the 4356 that smbclient sees. Normally, you don't have any reason to change that parameter so that's why I thought Ii could use it to detect whether smbclient is communicating with Warp as a serve...