I mounted a samba volume on XP. XP and Ubuntu are connected over 100Mbps ethernet (router). I am writing a 4GB file from XP to Ubuntu and the transfer is extremely slow : only around 1-1.5 MB/s. This is not a network or disk issue since at the same time this transfer is gonig on, I can scp the same file from XP to Ubuntu at 3-4 times faster (around 6MB/s). What could be wrong? Even for this slow transfer, smbd seems to be taking quite a bit CPU (more than sshd for the transfer rate). Reading from Ubuntu on this Samba volume is not much faster. only above 3MB/s. It is pretty surprising. Please let me know if you need any more info about the problem. The only changes I made to smb.conf are for adding shares. I have latest Ubuntu Jaunty packages. FYI: netstat on the connection from XP on Ubuntu shows around 1K of data on receive buffer. Seems to indicate smbd is not processing fast enough. Thanks, Raghu. -- View this message in context: http://www.nabble.com/Very-slow-transfers-to-Samba-on-Ubuntu-tp24168452p24168452.html Sent from the Samba - General mailing list archive at Nabble.com.
Sample tcpdump for such a connection : Notice that there are only couple of 1KB chunks for each millisecond : 18:50:57.948157 IP 192.168.0.100.4366 > 192.168.0.104.445: P 2184:3276(1092) ack 103 win 64719 18:50:57.948374 IP 192.168.0.104.445 > 192.168.0.100.4366: P 103:154(51) ack 3276 win 65535 18:50:57.948897 IP 192.168.0.100.4366 > 192.168.0.104.445: P 3276:4368(1092) ack 154 win 64668 18:50:57.949074 IP 192.168.0.104.445 > 192.168.0.100.4366: P 154:205(51) ack 4368 win 65535 18:50:57.949615 IP 192.168.0.100.4366 > 192.168.0.104.445: P 4368:5460(1092) ack 205 win 64617 18:50:57.949831 IP 192.168.0.104.445 > 192.168.0.100.4366: P 205:256(51) ack 5460 win 65535 18:50:57.950437 IP 192.168.0.100.4366 > 192.168.0.104.445: P 5460:6552(1092) ack 256 win 64566 18:50:57.950649 IP 192.168.0.104.445 > 192.168.0.100.4366: P 256:307(51) ack 6552 win 65535 18:50:57.951152 IP 192.168.0.100.4366 > 192.168.0.104.445: P 6552:7644(1092) ack 307 win 64515 18:50:57.951389 IP 192.168.0.104.445 > 192.168.0.100.4366: P 307:358(51) ack 7644 win 65535 18:50:57.951911 IP 192.168.0.100.4366 > 192.168.0.104.445: P 7644:8736(1092) ack 358 win 64464 18:50:57.952090 IP 192.168.0.104.445 > 192.168.0.100.4366: P 358:409(51) ack 8736 win 65535 18:50:57.952608 IP 192.168.0.100.4366 > 192.168.0.104.445: P 8736:9828(1092) ack 409 win 64413 18:50:57.952801 IP 192.168.0.104.445 > 192.168.0.100.4366: P 409:460(51) ack 9828 win 65535 18:50:57.953299 IP 192.168.0.100.4366 > 192.168.0.104.445: P 9828:10920(1092) ack 460 win 64362 18:50:57.953489 IP 192.168.0.104.445 > 192.168.0.100.4366: P 460:511(51) ack 10920 win 65535 18:50:57.954038 IP 192.168.0.100.4366 > 192.168.0.104.445: P 10920:12012(1092) ack 511 win 64311 18:50:57.954286 IP 192.168.0.104.445 > 192.168.0.100.4366: P 511:562(51) ack 12012 win 65535 18:50:57.954794 IP 192.168.0.100.4366 > 192.168.0.104.445: P 12012:13104(1092) ack 562 win 65535 18:50:57.954982 IP 192.168.0.104.445 > 192.168.0.100.4366: P 562:613(51) ack 13104 win 65535 18:50:57.955531 IP 192.168.0.100.4366 > 192.168.0.104.445: P 13104:14196(1092) ack 613 win 65484 18:50:57.955702 IP 192.168.0.104.445 > 192.168.0.100.4366: P 613:664(51) ack 14196 win 65535 18:50:57.956207 IP 192.168.0.100.4366 > 192.168.0.104.445: P 14196:15288(1092) ack 664 win 65433 18:50:57.956497 IP 192.168.0.104.445 > 192.168.0.100.4366: P 664:715(51) ack 15288 win 65535 18:50:57.956984 IP 192.168.0.100.4366 > 192.168.0.104.445: P 15288:16380(1092) ack 715 win 65382 18:50:57.957213 IP 192.168.0.104.445 > 192.168.0.100.4366: P 715:766(51) ack 16380 win 65535 18:50:57.957765 IP 192.168.0.100.4366 > 192.168.0.104.445: P 16380:17472(1092) ack 766 win 65331 18:50:57.957963 IP 192.168.0.104.445 > 192.168.0.100.4366: P 766:817(51) ack 17472 win 65535 18:50:57.958462 IP 192.168.0.100.4366 > 192.168.0.104.445: P 17472:18564(1092) ack 817 win 65280 18:50:57.958658 IP 192.168.0.104.445 > 192.168.0.100.4366: P 817:868(51) ack 18564 win 65535 18:50:57.959198 IP 192.168.0.100.4366 > 192.168.0.104.445: P 18564:19656(1092) ack 868 win 65229 18:50:57.959367 IP 192.168.0.104.445 > 192.168.0.100.4366: P 868:919(51) ack 19656 win 65535 18:50:57.959880 IP 192.168.0.100.4366 > 192.168.0.104.445: P 19656:20748(1092) ack 919 win 65178 Raghu A wrote:> > I mounted a samba volume on XP. XP and Ubuntu are connected over 100Mbps > ethernet (router). > > I am writing a 4GB file from XP to Ubuntu and the transfer is extremely > slow : only around 1-1.5 MB/s. > > This is not a network or disk issue since at the same time this transfer > is gonig on, I can scp the same file from XP to Ubuntu at 3-4 times faster > (around 6MB/s). > > What could be wrong? Even for this slow transfer, smbd seems to be taking > quite a bit CPU (more than sshd for the transfer rate). > >-- View this message in context: http://www.nabble.com/Very-slow-transfers-to-Samba-on-Ubuntu-tp24168452p24178268.html Sent from the Samba - General mailing list archive at Nabble.com.
thanks! I found the setting I actually need is "map to guest = Bad
Password"...
i will try to evaluate about security issues involved by this global
setting.... any comment is appreciated.
Thanks again Dave
Da: Dale Schroeder [mailto:dale@BriannasSaladDressing.com]
Alessandro Tinivelli wrote:
Good day to all, we have a Samba 3.0.33 in ADS mode, and we have been
asked to enable "null session" on the share [prova] (my smb.conf is
below).
I have googled a bit and i have still many doubts: if we put in share
definition the "guest ok = yes", will the [prova] will be able to
accept
null sessions from an process running on a XP station? Will the process
be able to delete files?
Additionally, I think you will also need
[global]
map to guest = bad user
Of course, the posix permissions must also allow guest access. Details
below.
Otherwise, this should work, as long as you can deal with the security
risks involved with null sessions.
Bad news... i have been able to set up an anonymous share and any
windows client (inside and outside the domain) can connect without been
asked for any password.
But on a machine (win2003,present in hosts allow) runs a service
(running as local system account) which is not able to connect to the
share. In samba log i see the following error
"make_connection: connection to onanon denied due to security
descriptor."
is it possible to solve my issue? Or, maybe, i can try to make the
service run as another user? (i don't know if this is good for the
application using this process).
below my current samba.conf
-------------------------------------------------------------
[global]
workgroup = POL
realm = POL.DOM
server string = NAS03 (Samba %v)
security = ADS
map to guest = Bad Password
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY IPTOS_LOWDELAY
idmap uid = 10000-20000
idmap gid = 10000-20000
winbind cache time = 10
winbind use default domain = Yes
winbind nss info = rfc2307
[onanon]
comment = Condivisione anonima
path = /storage/samba/GCP/on
force group = gcp
read only = No
hosts allow = 10.101.37.23, 10.101.37.22, 10.101.37.24
guest ok = Yes
browseable = No
---------------------------------------------------------------
ith the security risks involved with null sessions.
The thing that I am wondering about is what is your network topology like. Are you running this as a stand alone file server or are you joining it to a active directory domain controller (ex. Win2k, Win2k3, Win 2k8 domain). If you are then you need to set up winbind as well. If not you are using the wrong security descriptor and you should be using user and not ads. -- W. Nick Pappin On Wed, Jul 1, 2009 at 12:21 AM, Alessandro Tinivelli < alessandro.tinivelli@monrif.net> wrote:> yes, i'm in security = ADS. > > > > The client computer interested in the problem is out of the domain, logged > with local administrator account. > > It's able to connect to che "onanon" share with a >net use * > \\10.10.40.3\onanon > > without givine user/pass. > > But a service running on it produces the error "make_connection: > connection to onanon denied due to security > descriptor." > > > > *Da:* Nick Pappin [mailto:npappin@latahfcu.org] > *Inviato:* marted? 30 giugno 2009 19.18 > *A:* Alessandro Tinivelli > *Oggetto:* Re: R: [Samba] enabling "null session" on a share > > > > Are you tying this into a active directory structure. > > -- > W. Nick Pappin > > On Fri, Jun 26, 2009 at 1:52 AM, Alessandro Tinivelli < > alessandro.tinivelli@monrif.net> wrote: > > Bad news... i have been able to set up an anonymous share and any > windows client (inside and outside the domain) can connect without been > asked for any password. > > > > But on a machine (win2003,present in hosts allow) runs a service > (running as local system account) which is not able to connect to the > share. In samba log i see the following error > > > > "make_connection: connection to onanon denied due to security > descriptor." > > > > is it possible to solve my issue? Or, maybe, i can try to make the > service run as another user? (i don't know if this is good for the > application using this process). > > > > below my current samba.conf > > > > ------------------------------------------------------------- > > [global] > > workgroup = POL > > realm = POL.DOM > > server string = NAS03 (Samba %v) > > security = ADS > > > map to guest = Bad Password > > log file = /var/log/samba/%m.log > > max log size = 50 > > socket options = TCP_NODELAY IPTOS_LOWDELAY > > idmap uid = 10000-20000 > > idmap gid = 10000-20000 > > winbind cache time = 10 > > winbind use default domain = Yes > > winbind nss info = rfc2307 > > > > [onanon] > > comment = Condivisione anonima > > path = /storage/samba/GCP/on > > force group = gcp > > read only = No > > hosts allow = 10.101.37.23, 10.101.37.22, 10.101.37.24 > > guest ok = Yes > > browseable = No > > --------------------------------------------------------------- > > > > > ith the security risks involved with null sessions. > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > > >