Samba server did not respond after 20000 milliseconds

wayno · 11-30-2007, 08:31 AM

I'm tearing my hair out here and need some help. I recently built a new Fedora 8 box on an old Dell that was previously running FC5. I have a second hard disk mounted under /mnt/store that holds all my pictures, music, videos, etc and I have an NFS mount point on /mnt/store that I connect to from 2 other Fedora boxes and also need to share Pictures, Music & Videos folders underneath /mnt/store for a couple of Windows boxes. This configuration was working fine in FC5. I made sure I punched a hole in the firewall but just for good measure I disabled iptables and selinux. Whenever I try to connect to the server (that is, either directly to a share or just to the server to list shares), I just get timeouts. On Linux when running:

Code:

smbclient -L <server>

the response I get is

Code:

Receiving SMB: Server stopped responding
session setup failed: Call timed out: server did not respond after 20000 milliseconds

Here is my (mostly default) config file:

Code:

[global]
        workgroup = mooreinn
        server string = Fedora Samba Server
        hosts allow = 192.168.2. 127.
        printcap name = /etc/printcap
        cups options = raw
        log file = /var/log/samba/%m.log
        max log size = 50
        security = user
         username map = /etc/samba/smbusers
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        domain master = yes
       preferred master = yes
        dns proxy = no
        username map = /etc/samba/smbusers
        oplocks = true
        kernel oplocks = true
        level2 oplocks = true
[homes]
        comment = Home Directories
        browseable = no
        writeable = yes
[Profiles]
        path = /home/profiles
        browseable = no
[printers]
        comment = All Printers
        path = /var/spool/samba
        browseable = yes
        printing = cups
        writeable = yes
        printable = yes
        use client driver = yes
[Pictures]
        comment = Our Pictures
        path = /mnt/store/Pictures
        writeable = yes
        browseable = yes
        valid users = user1,user2
[Music]
        comment = Our Music
        path = /mnt/store/Music
        writeable = yes
        browseable = yes
        valid users = user1,user2
[Videos]
        comment = Our Videos
        path = /mnt/store/Videos
        writeable = yes
        browseable = yes
        valid users = user1,user2
[Database]
        comment = Database Folder
        path = /mnt/store/Database
        writeable = yes
        browseable = yes
        valid users = user1,user2
[Backup]
        comment = PC Backup
        path = /mnt/store/backup
        writeable = yes
        browseable = yes
        valid users = user1,user2

I've searched and searched looking for an answer to this but all I've managed to find is people asking the same question. I'm using Fedora 8 (2.6.23.1-42.fc8) and Samba 3.0.27a-0.fc8. Client is either Samba 3.0.27a-0.fc8 or Windows XP SP2. The Samba logs tell me absolutely nothing other than when the service started. From the F8 machine I'm trying to use as a client, I can successfully connect to shares on the Windows boxes so I'm happy the client does actually work. I've created users and set passwords via system-config-samba and smbpasswd. I've tried the client with name and IP with the same result (I'm happy name resolution works in my network anyway). I have tried stopping NFS because I heard there can be conflicts but had the same result.

Any ideas? Am I missing something really obvious?

David1357 · 11-30-2007, 09:55 AM

Quote:

Originally Posted by wayno

Any ideas? Am I missing something really obvious?

Is the samba service started?

# chkconfig --list | grep smb

Slick666 · 11-30-2007, 10:42 AM

You shoudl try the command "testparm". This will check your samba configuration and hopefully provide some feedback as to possible errors. Also remember to restart the deamon after you've made changes.

kjuergen · 11-30-2007, 08:11 PM

Same problem here with Samba/FC8. Now I have a 90% useless server and I hope that there will be a solution I can follow.....

Juergen

wayno · 12-01-2007, 05:04 AM

Quote:

Originally Posted by David1357

Is the samba service started?

# chkconfig --list | grep smb

I know I said obvious but ......

Yes, the service is definitely running.

wayno · 12-01-2007, 05:07 AM

Quote:

Originally Posted by Slick666

You shoudl try the command "testparm". This will check your samba configuration and hopefully provide some feedback as to possible errors. Also remember to restart the deamon after you've made changes.

I've seen reference to this before but the command doesn't exist on my system. I installed Samba with the base F8 install and have since upgraded it with Yum.

wayno · 12-01-2007, 10:09 AM

Well apparently the problem is with encrypted passwords. I set

Code:

encrypt passwords = no

and it all sprang into life. I felt sure I had tried this previously but maybe I missed it.

David1357 · 12-01-2007, 12:50 PM

Quote:

Originally Posted by wayno

I know I said obvious but ......

Yes, the service is definitely running.

If it is running, then you should see some good messages in the output from dmesg. There should also be interesting messages in the log files in "/var/log". Files of interest are "messages" and "samba/smbd.log".

You can also stop the samba daemon and run it interactively with "-i" and with a debug level "-d". That is probably the easiest way to debug problems with a samba server.

David1357 · 12-01-2007, 12:53 PM

Quote:

Originally Posted by wayno

Well apparently the problem is with encrypted passwords. I set

Code:

encrypt passwords = no

and it all sprang into life. I felt sure I had tried this previously but maybe I missed it.

I am running samba on FC4 with "encrypt passwords" set to "yes". You may want to try the debugging suggestions I mentioned above before you give up on this option. Otherwise you are just masking the real problem by giving up a layer of security.

wayno · 12-02-2007, 12:26 AM

Quote:

Originally Posted by David1357

I am running samba on FC4 with "encrypt passwords" set to "yes". You may want to try the debugging suggestions I mentioned above before you give up on this option. Otherwise you are just masking the real problem by giving up a layer of security.

Thanks I will give that a go and see what I get.