Two servers, two SAMBA shares, one fast access one slow

English Network/Internet
1

I have two servers and here are the basic details:

Server#1:
opensuse 12.2 (I know it’s old - but lets skip that subject for now)
Samba version 3.6.7-48.28.1-3108-SUSE-SL12.2-x86_64

SMB.CONF


[global]
        workgroup = <name>
        passdb backend = tdbsam
        printing = cups
        printcap name = cups
        printcap cache time = 750
        cups options = raw
        map to guest = Bad User
        include = /etc/samba/dhcp.conf
        logon path = \\%L\profiles\.msprofile
        logon home = \\%L\%U\.9xprofile
        logon drive = P:
        usershare allow guests = No
        add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
        domain logons = No
        domain master = No
        security = domain
        wins server =
        wins support = No
[VOL1]
        inherit acls = Yes
        path = /home/VOL1
        read only = No
        force group = vol1

Server#2:
opensuse 13.1
Samba version 4.1.19-3.36.1-3442-SUSE-oS13.1-x86_64

SMB.CONF


[global]
        add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
        domain logons = No
        domain master = No
       # security = user
        security = domain
        usershare allow guests = No
       #workgroup = <namexxx>
        workgroup = <name>
        passdb backend = smbpasswd
        wins support = No
[DOCUMENTS]
        comment = documents
        inherit acls = Yes
        path = /DOCUMENTS
        read only = No
        create mask = 0775
        directory mask = 0775
        guest ok = No

Now I have windows machines that can access the share on each of these servers. Server#1 access is very quickly, Server#2 access is pretty slow, this server has LOTS of small docs in different sub-directories. The top of the share only has two directories, then the others under each of those two and there are literally thousands of directories (Directory A = 123228/Directory B=30691). It basically takes the almost two minute timeout to get the directory to come up in Windows File explorer. I am writing things to these shares and file creation on Server#2 is slow for users, basically taking 30 seconds to almost a minute to create a simple HTML document. I am not searching for a place to create the file, my application knows and paths exactly where it should put it. The difference in the SMB.CONF files here is the workgroup, and the workgroup of the machines connecting to them is the same as Server#1. I tried changing the workgroup of a station to <namexxx> and it was no faster, then I ultimately tried changing the share to be for workgroup matching Server#1, as well as changing the security type to match Server#1 as well. Also the firewalls on both machines have samba-server and samba-client setup, If I completely drop the firewall on Server#2 the access is much more like that of Server#1 with the firewall up…

Can anyone help with this problem? I know it is something that I am missing…
Thank you in advance.

2

You need to narrow down the possibilities…

Have you at least tried to determine if this is a network connection problem or an app or system configuration or resources problem?

Is this latency only on initial connection or <much> later?

Have you run something like wireshark to see if it might be a network connection problem?
Are you sure, for instance that you don’t have a name resolution or discovery issue?
Are there differences how the shares are mounted on the client differently?

Have you tried re-deploying share files on the other server and comparing?
Have you tried creating shares of smaller number of files?

Etc.
Those are just off the top of my head. Also, consider what versions of Windows your clients are (There is a big diff between WinXP and Win7 support for different versions of SMB for example) and each of your SAMBA servers are running different SAMBA versions.

TSU