Samba shares crash Windows clients

GT_Onizuka · 06-30-2005, 11:10 AM

I have a Linux-machine, and my brother and I each have a Winbox, and they are all networked on a hub we have in our room. I have some Samba shares so my brother can grab my music and patches I download for the games we play, and it was working fine until now. All of a sudden, when he tries to access any of my shares, his computer locks up and crashes. Now, at first I thought it was just a problem with his machine, but when I try it with mine, it does a similar thing, however, it doesn't crash. My computer says Explorer has stopped responding, but if I wait a long time (I'm talking like, 5 minutes here) the share eventually gets accessed. But then, browsing within the share takes the same lengthy time to open any windows, or anything like that.

The only change I have recently made to my Linux machine is I switched over to Dropline Gnome. Before I was just using IceWM, but I decided, based on Slackware users recommendation, to give Dropline a try.

Any ideas?

EDIT: I forgot to mention, my machine can access the Windows machines shares perfectly making me believe it's definitely a configuration error on my part (on the Linbox), however, I'm at a loss as to where, since the shares were working perfectly not too long ago.

Half_Elf · 06-30-2005, 11:52 AM

Maybe dropline updated/changed something in your samba; you better give a look. Especially make sure "TCP_SOCKET" (or something like that) options is set corectly in your smb.conf (I don't remember what is "correctly" but the man page was quite clear about it if I remember right, like "dont set to ... if you have problem").

Kdr Kane · 06-30-2005, 11:58 AM

Interesting, but I would have the tendency to think it was the Windows machine's fault. What with all those security patches coming down every month.

BTW, what OS/Service Pack are the Windows machines?

GT_Onizuka · 06-30-2005, 12:06 PM

Quote:

Originally posted by Kdr Kane
Interesting, but I would have the tendency to think it was the Windows machine's fault. What with all those security patches coming down every month.

BTW, what OS/Service Pack are the Windows machines?

Both of them are XP with SP2, if I'm not mistaken (I'm not sure about my brothers computer). One thing I did notice, and didn't remember until now was, I'm pretty sure after installing Dropline, I had two startup scripts for Samba, I had a feeling perhaps Dropling updated Samba, or something like that, so I renamed them rc.samba and my older one, rc.samba.old and I made it no longer executable. Here are both of them:

/etc/rc.d/rc.samba

Code:

#!/bin/sh
#
# /etc/rc.d/rc.samba
#
# Start/stop/restart the Samba SMB file/print server.
#
# To make Samba start automatically at boot, make this
# file executable:  chmod 755 /etc/rc.d/rc.samba
#

SMBD_PIDS=`pidof smbd`
NMBD_PIDS=`pidof nmbd`

samba_start() {
  if [ -x /usr/sbin/smbd -a -x /usr/sbin/nmbd -a -r /etc/samba/smb.conf ]; then
        echo -en "Starting Samba: "
    if [ "x$SMBD_PIDS" == "x" ]; then
      echo -en "'/etc/sbin/smbd -D' "
      /usr/sbin/smbd -D
    fi

    if [ "x$NMBD_PIDS" == "x" ]; then
      echo -en "'/etc/sbin/nmbd -D' "
      /usr/sbin/nmbd -D
    fi

        echo ""
  fi
}

samba_stop() {
  echo -en "Stopping Samba: "
  if [ ! "x$SMBD_PIDS" == "x" ]; then
    echo -en "'killall smbd' "
        killall smbd
  fi
  
  if [ ! "x$NMBD_PIDS" == "x" ]; then
    echo -en "'killall nmbd' "
    killall nmbd
  fi

  echo ""
  SMBD_PIDS=
  NMBD_PIDS=
}

samba_restart() {
  samba_stop
  sleep 2
  samba_start
}

case "$1" in
'start')
  samba_start
  ;;
'stop')
  samba_stop
  ;;
'restart')
  samba_restart
  ;;
*)
  # DLG Addition of usage when no parameter passed via CLI
  echo "Usage: $0 [start|stop|restart]"
esac

/etc/rc.d/rc.samba.old

Code:

#!/bin/sh
#
# /etc/rc.d/rc.samba
#
# Start/stop/restart the Samba SMB file/print server.
#
# To make Samba start automatically at boot, make this
# file executable:  chmod 755 /etc/rc.d/rc.samba
#

samba_start() {
  if [ -x /usr/sbin/smbd -a -x /usr/sbin/nmbd -a -r /etc/samba/smb.conf ]; then
    echo "Starting Samba..."
    /usr/sbin/smbd -D
    /usr/sbin/nmbd -D
  fi
}

samba_stop() {
  killall smbd nmbd
}

samba_restart() {
  samba_stop
  sleep 2
  samba_start
}

case "$1" in
'start')
  samba_start
  ;;
'stop')
  samba_stop
  ;;
'restart')
  samba_restart
  ;;
*)
  # Default is "start", for backwards compatibility with previous
  # Slackware versions.  This may change to a 'usage' error someday.
  samba_start
esac

And here's my smb.conf

Code:

[global]
        encrypt passwords = yes
        guest account = smbguest
        netbios name = ONIZUKA
        security = share
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 IPTOS_LOWDELAY
        workgroup = MSHOME

server string = Slackware
wins support = no
[slackware]
        path = /media/share
        read only = no
        guest ok = yes
        guest only = yes

[lan]
        path = /lan
        read only = yes
        guest ok = yes
        guest only = yes

[mp3]
        path = /mp3
        read only = yes
        guest ok = yes
        guest only = yes

[psx]
        path = /media/psx_games
        read only = yes
        guest ok = yes
        guest only = yes

I have a feeling the startup scripts might be to blame, so I'm going to try going back to the older one and see if that fixes anything, although, it seems puzzling that that would be the problem.

Half_Elf · 06-30-2005, 02:01 PM

my guess would be that you problem is around the "socket options" in your smb.conf. i'm not on a Linux computer right now ( sadly) so I can't help right now, but maybe if you browse man you could find some hints. Or what if you comment this line and restart samba?

zborgerd · 07-01-2005, 11:02 AM

Old versions of Dropline (the 2.8.x series and previous versions) used to contain Samba updates. After we took the project over from the previous maintainer, we ultimately decided to exclude Samba from our package list in an effort to purge some of Slackware replacement libraries from our desktop distribution. The former maintainer included some of these things in order to keep Dropline compatible with multiple versions of Slackware. After we made the decision to only support one version of Slackware at a time (while keeping old releases available), it was possible to drop things like Samba from our package list.

If you are using Dropline GNOME 2.10.x (for Slackware 10.1), then there are no changes to Samba. If you are using Dropline 2.8.x (for older versions of Slackware), then it's likely that Samba could have been upgraded. If that's the case, then you may want to try using "upgradepkg" to reinstall Slackware's own Samba package.

A more ideal solution would be to upgrade to the latest stable version of Slackware (10.1) and install the much improved Dropline GNOME 2.10.x.

Judging by that script up there, it looks like it was written by the former Dropline Samba package maintainer for the 2.8.3 release. Replacing it with the Slackware original may be a good idea. I also seem to recall that there was some LDAP requirement in later Samba releases, and this caused Samba to flip out a bit.

Not sure if it's related:
http://www.dropline.net/forums/viewt...ght=samba+ldap

After I figure out which versions you have, I may be able to offer more insight.