samba - Feb 2003 - Speed/lockup problems with wireless client

Hi,
	I have samba running on a home LAN using a Linksys mixed wired (100 Mbit 
ethernet) & wireless access point, which also does NAT to a DSL modem.  The 
server is connected to this access point via an ethernet cable.  Clients can 
connect via wireless or wired network connection.
	I am using encrypted passwords, and have in smb.conf:
	socket options = TCP_NODELAY SO_RCVBUF=4096 SO_SNDBUF=4096
IPTOS_LOWDELAY
	When I connect to a share from the client, copying down from this share gets 
so slow it locks the client - in Windows, the instance of Windows Explorer 
locks, while in Linux under an xterm, 
# cp /mnt/share/test/somefile.dat /home/me/test/somefile.dat
results in:
cp: reading `/mnt/share/test/somefile.dat': Input/output error

	Copying up to server is no problem on either side, and copying up and down 
are no problem when the client is connected to the networked by wired 
connection.

When the share is public (i.e.:
   comment = Some Dir
   path = //somedir
   read only = no
   public = yes
   printable = no
)
the client can copy up and down without problems
>From what I was able to scour off of mailing lists (mainly this one),
problems
like this have something to do with timing differences between the client, 
the smb daemon, and the server network card, but I have no idea where to 
start fiddling to resolve this.

Can anyone give me ideas to help make copying up to the server not lock up 
clients but still preserve passwords on shares?

Many, many thanks for any ideas,

Eric

Here's the output of tcpdump and netstat during a copy attempt 
on Linux (which eventally failed):
# tcpdump -c 20
13:23:50.978082 192.168.1.10.ssh > 192.168.1.1.33122: P 
671020557:671020621(64) ack 3921394066 win 8576 <nop,nop,timestamp 612682735 
1520462> (DF) [tos 0x10]
13:23:50.978835 192.168.1.10.32798 > wdc.speakeasy.net.domain:  57812+ PTR? 
10.1.168.192.in-addr.arpa. (43) (DF)
13:23:50.981379 192.168.1.1.33122 > 192.168.1.10.ssh: . ack 64 win 63712 
<nop,nop,timestamp 1520462 612682735> (DF) [tos 0x10]
13:23:51.006595 wdc.speakeasy.net.domain > 192.168.1.10.32798:  57812 
NXDomain* 0/0/0 (43) (DF)
13:23:51.006858 192.168.1.10.32798 > wdc.speakeasy.net.domain:  57813+ PTR? 
1.1.168.192.in-addr.arpa. (42) (DF)
13:23:51.036112 wdc.speakeasy.net.domain > 192.168.1.10.32798:  57813 
NXDomain* 0/0/0 (42) (DF)
13:23:51.036286 192.168.1.10.32798 > wdc.speakeasy.net.domain:  57814+ PTR? 
2.159.92.66.in-addr.arpa. (42) (DF)
13:23:51.062309 wdc.speakeasy.net.domain > 192.168.1.10.32798:  57814 1/0/0 
PTR[|domain] (DF)
13:23:51.259724 192.168.1.10.netbios-ssn > 192.168.1.101.33126: P 
1203552341:1203553593(1252) ack 183206398 win 4665 <nop,nop,timestamp 
612682880 1520345>NBT Packet (DF)
13:23:51.259826 192.168.1.10.32798 > wdc.speakeasy.net.domain:  57815+ PTR? 
101.1.168.192.in-addr.arpa. (44) (DF)
13:23:51.267240 192.168.1.101.33126 > 192.168.1.10.netbios-ssn: P 1:145(144) 
ack 1252 win 11584 <nop,nop,timestamp 1520491 612682880>NBT Packet (DF)
13:23:51.267479 192.168.1.10.netbios-ssn > 192.168.1.101.33126: P 
1252:1338(86) ack 145 win 4665 <nop,nop,timestamp 612682883 1520491>NBT 
Packet (DF)
13:23:51.270688 192.168.1.101.33126 > 192.168.1.10.netbios-ssn: P 145:194(49)
ack 1338 win 11584 <nop,nop,timestamp 1520491 612682883>NBT Packet (DF)
13:23:51.270761 192.168.1.10.netbios-ssn > 192.168.1.101.33126: . 
1338:2786(1448) ack 194 win 4665 <nop,nop,timestamp 612682885 1520491>NBT 
Packet (DF)
13:23:51.270769 192.168.1.10.netbios-ssn > 192.168.1.101.33126: . 
2786:4234(1448) ack 194 win 4665 <nop,nop,timestamp 612682885 1520491>NBT 
Packet (DF)
13:23:51.281006 192.168.1.101.33126 > 192.168.1.10.netbios-ssn: . ack 4234
win
11584 <nop,nop,timestamp 1520492 612682885> (DF)
13:23:51.281016 192.168.1.10.netbios-ssn > 192.168.1.101.33126: P 
4234:5486(1252) ack 194 win 4665 <nop,nop,timestamp 612682890 1520492>NBT 
Packet (DF)
13:23:51.288257 wdc.speakeasy.net.domain > 192.168.1.10.32798:  57815 
NXDomain* 0/0/0 (44) (DF)
13:23:51.290590 192.168.1.101.33126 > 192.168.1.10.netbios-ssn: P 194:243(49)
ack 5486 win 11584 <nop,nop,timestamp 1520493 612682890>NBT Packet (DF)
13:23:51.290645 192.168.1.10.netbios-ssn > 192.168.1.101.33126: . 
5486:6934(1448) ack 243 win 4665 <nop,nop,timestamp 612682895 1520493>NBT 
Packet (DF)
------------------------------------------------------------------------------------------------------------------
# netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 192.168.1.1:netbios-ssn 192.168.1.101:33126     
ESTABLISHED
tcp        0    256 192.168.1.10:ssh        192.168.1.1:33122       
ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags       Type       State         I-Node Path
unix  7      [ ]         DGRAM                    988    /dev/log
unix  3      [ ]         STREAM     CONNECTED     202684
unix  3      [ ]         STREAM     CONNECTED     202683
unix  2      [ ]         DGRAM                    1775
unix  2      [ ]         DGRAM                    1683
unix  2      [ ]         DGRAM                    1273
unix  2      [ ]         DGRAM                    1065
unix  2      [ ]         DGRAM                    1001

On Thursday 06 February 2003 03:09 am, Kurt Weiss wrote:
> my old wireless ap hangs too, if the signal is not strong enough. ->
> this results, cause the PCMCIA card has not this strength as the ap has.
> on the notebook u see medium quality, but the signal does not recieve
> the ap...
> our new ap runs well (after flashing newest firmware...)
> which ap u use? 
Linksys' standard Wired/wireless AP, the one that's on the front page of
CompUsa, etc.  I can look up the model number if that's really key.
> which card u use? 
Orinico Silver, under RedHat 8.0
> are u using encryption on wlan?
Nope, not right now
> did u try to slow down (fix 5.5mbits/s)?
How do i do this?  I was under the impression that 802.11b transmitted at 
2.2Mbs...  Do I need to set it to this, or to 5.5Mbps?
>did u check "save transmit"
> (evtl. ap) when microwaves are in the near?
Would this be on the ap or the card?

Thanks,

Eric
> i hope it helps...
>
> Eric Ellsworth schrieb:
> > Hi,
> > 	I have samba running on a home LAN using a Linksys mixed wired (100
Mbit
> > ethernet) & wireless access point, which also does NAT to a DSL
modem.
> > The server is connected to this access point via an ethernet cable. 
> > Clients can connect via wireless or wired network connection.
> > 	I am using encrypted passwords, and have in smb.conf:
> > 	socket options = TCP_NODELAY SO_RCVBUF=4096 SO_SNDBUF=4096
> > IPTOS_LOWDELAY
> > 	When I connect to a share from the client, copying down from this
share
> > gets so slow it locks the client - in Windows, the instance of Windows
> > Explorer locks, while in Linux under an xterm,
> > # cp /mnt/share/test/somefile.dat /home/me/test/somefile.dat
> > results in:
> > cp: reading `/mnt/share/test/somefile.dat': Input/output error
> >
> > 	Copying up to server is no problem on either side, and copying up and
> > down are no problem when the client is connected to the networked by
> > wired connection.