Find the answer to your Linux question:
Results 1 to 9 of 9
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    Slow response time for Samba


    Ok, I have a rather annoying problem that seems to be very popular on google groups and several other message boards but I still haven't found a solution to the problem. After my samba server has been sitting idle for about 30 minutes or so and a Windows client tries to access a share, it takes a full 1.5-2 minutes for the server to respond to the Windows client. As soon as the share refreshes, every thing is nice and quick again.

    Here is my smb.conf file. I don't know where to start and I'm starting to get an ear full from the engineers using the server so I could really use some help.

    Code:
    [global]
    	workgroup = WORKGROUP
    	realm = REALM.COM
    	server string = Dozer engineering file server
    	security = ADS
    	obey pam restrictions = Yes
    	password server = XXX.XXX.XXX.XXX
    	log file = /var/log/samba/%m.log
    	max log size = 50
    	max xmit = 65535
    	unix extensions = No
    	socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 IPTOS_LOWDELAY
    	preferred master = No
    	local master = No
    	domain master = No
    	dns proxy = No
    	wins server = XXX.XXX.XXX.XXX
    	ldap ssl = no
    	idmap uid = 10000-20000
    	idmap gid = 10000-20000
    	template primary group = users
    	template homedir = /home/shares/bu_onen1/bu/users8/%u
    	template shell = /bin/bash
    	winbind separator = +
    	winbind cache time = 10
    	winbind enable local accounts = Yes
    	winbind use default domain = Yes
    	hide special files = Yes
    	follow symlinks = No
    
    [homes]
    	comment = Home directory for %U
    	valid users = %S, %D+%S
    	read only = No
    	browseable = No
    
    [public]
    	comment = public dump
    	path = /home/shares/public
    	read only = No
    	guest ok = Yes
    
    [bu_onen1]
    	path = /home/shares/bu_onen1
    	write list = vj928, vk594
    	read only = No
    
    [ptc]
    	path = /home/shares/ptc

  2. #2
    Come on, someone has got to know how to fix this. I'm obviously not the only person with this problem and it's causing me a lot of trouble right now

  3. #3
    which version of samba are you using?

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Newbie ihayhurst's Avatar
    Join Date
    Jun 2005
    Location
    UK
    Posts
    138
    OK I'm no expert, just some thoughts on how I might attack the problem,

    check the samba daemons on the server (smbd & nmbd) I find the get 'stuck ' sometimes,

    can the client resolve the host by netbios (from the windows box do nbtstat -a serverhostname
    nbtstat -A serverIP

    fireup ethereal and examine the traffic

    Like I said there must be some samba experts about but that's my starting point anyway
    Cheers Ian
    Registerd Linux user #119296

  6. #5
    Linux Newbie ihayhurst's Avatar
    Join Date
    Jun 2005
    Location
    UK
    Posts
    138
    Oh another thought I notice you are using ADS,
    I just moved to theis from NT workgroups, I find the server is only contactable by the A name DNS entry , everyone always used a c name alias, and it doesnt work ....but spends a long time trying

    Cheers Ian
    Registerd Linux user #119296

  7. #6
    which version of samba are you using?
    I'm using samba 3.0.10 on Fedora Core 3.

    check the samba daemons on the server (smbd & nmbd) I find the get 'stuck ' sometimes,
    Both appear to be running ok.

    can the client resolve the host by netbios (from the windows box do nbtstat -a serverhostname
    nbtstat -A serverIP
    According to my Windows box....'nbstat' is not recognized as an internal or external command, operable program or batch file.

    I just moved to theis from NT workgroups, I find the server is only contactable by the A name DNS entry , everyone always used a c name alias, and it doesnt work ....but spends a long time trying
    I'm not really sure what you mean by an A name DNS entry versus a c name alias. Keep in mind that I'm a mechanical engineer and not a administrator so I'm lucking to have gotten this far with this server.

  8. #7
    Ok, now I have another problem. Now my Windows clients won't see the Samba machine until I manually restart the winbind daemon. After that the clients will see the Samba box for about 2 minutes before it disappears again.

    I really need to get this fixed ASAP...my boss is getting pissed and threatening to have our IT guy put Windows 2003 on this machine.

  9. #8
    Linux Newbie ihayhurst's Avatar
    Join Date
    Jun 2005
    Location
    UK
    Posts
    138
    typo sorry, nbtstat
    Registerd Linux user #119296

  10. #9
    The clients can find the computer via nbtstat just fine.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •