1 Dec 2006 01:03
Re: Samba 3 socket status after [RST, ACK]
Alison Winters <alisonw <at> sgi.com>
2006-12-01 00:03:32 GMT
2006-12-01 00:03:32 GMT
FWIW we're currently working around this by only running Samba on port 139 (smb ports config option). Running only on 445 makes browsing break. I'd be very interested to see performance figures of running Samba only on 139 vs both ports. I'm guessing the connect will be faster because 445 will be dropped by the kernel straight away, but perhaps there is significant transport overhead in NBT vs raw TCP? I'm not sure there is a clever programmatic solution to this. Perhaps if you had a decent packet filter you could do something really evil like blocking 139 requests that weren't browse requests iff a 445 wasn't coming from the same client too? Ick. Alison Petr Sumbera wrote: > Hi All, > > I would like ask you for your opinion on the following issue with Samba > 3 (tested with 3.0.21b on Solaris and 3.0.20 on Linux). > > When running samba against Windows (WinXP) client, there appears at some > point some strange TCP communication (ending with [RST,ACK]): > > No. Time Src Dst Pro. Info > ================================ > 67 .430902 WinXP Samba TCP 2321 > netbios-ssn [SYN] Seq=0 Len=0 MSS=1460 > 68 .431162 Samba WinXP TCP netbios-ssn > 2321 [SYN, ACK] Seq=0 Ack=1 > Win=5840 > Len=0 MSS=1460(Continue reading)
RSS Feed