Bug 2756 - Performance Across VPN (OS X 10.3.9 / samaba 3.0.10 / Win2K clients)
Performance Across VPN (OS X 10.3.9 / samaba 3.0.10 / Win2K clients)
Status: RESOLVED WONTFIX
Product: Samba 3.0
Classification: Unclassified
Component: File Services
3.0.10
PPC Mac OS X
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-31 12:41 UTC by Dan Tappin
Modified: 2006-10-13 00:05 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Tappin 2005-05-31 12:41:45 UTC
We have a small LAN (192.168.0.0) of 50+ PC users (Win98, Win2K, WinXP) accessing a G5 Xserve 
running OS X Server 10.3.9 w/ Samba 3.0.10.  We added a VPN over a 3Mb/s ISP connenction via 2 
sonicwall firewall / VPN devices.  The LAN on the otherside of the VPN (192.168.2.0) has severe 
performance issues accessing the Xserve via SMB.  The browsing of files is decent (after some smb.conf 
tweaking) but selecting, opening, saving and copying files is extremly slow (i.e. 2-3 minutes to open a 
10 kb PDF etc).

To compare we have our old Dell fileserver with Samba 2.0.x which does not exhibit the same speed 
issues nor does normal native Windows shares on desktop systems.  Also I duplicated the performance 
issues on my OS 10.4.1 based Powerbook also running Samba 3.0.10.  The previous build of Samba on 
this server on OS 10.3.7 was 3.0.4 and it had the same performance issues.

I've contacted Apple techsupport and they are at a loss as to what the issue could be.  We built a new 
smb.conf file from scratch and I've played with the socket values with no help at all.  I've also posted 
this to the samba and the OS X Server admin lists with no success.

Thanks,

Dan Tappin

smb.conf (global) below

-----

[global]
	getwd cache = yes
	workgroup = OROURKE
	display charset = UTF-8-MAC
	print command = /usr/sbin/PrintServiceAccess printps %p %s
	lprm command = /usr/sbin/PrintServiceAccess remove %p %j
	security = user
	guest account = unknown
	enhanced browsing = yes
	encrypt passwords = yes
	printing = BSD
	allow trusted domains = no
	preferred master = no
	lppause command = /usr/sbin/PrintServiceAccess hold %p %j
	netbios name = fileserver
	wins support = no
	max smbd processes = 0
	printcap =  
	server string = Mac OS X Server
	lpresume command = /usr/sbin/PrintServiceAccess release %p %j
	domain logons = no
	lpq command = /usr/sbin/PrintServiceAccess jobs %p
	passdb backend = opendirectorysam guest
	dos charset = CP437
	unix charset = UTF-8-MAC
	socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8576 
SO_SNDBUF=8576
	auth methods = guest opendirectory
	local master = yes
	use spnego = no
	map to guest = Never
	domain master = no
	printer admin = @admin, @staff, unknown
	log level = 2
Comment 1 Gerald (Jerry) Carter 2006-04-20 08:03:34 UTC
severity should be determined by the developers and not the reporter.
Comment 2 James Peach 2006-10-13 00:05:33 UTC
I'm sorry, Samba 3.0.10 is just too old for us to be fixing. I think that
your best bet is to take a packet trace back to Apple tech support and
hopefully that will help them resolve this.

That said, you might try bumping the SO_RCVBUF and SO_SNDBUF up to something
like 262144 :)