[SOLVED] Samba stopped working

[starfleetcaptainrob]

So, I turned my server off this evening to kind of clean up some of the cables under my desk. Then I wired everything back up the same way I had it and suddenly I can't connect to my samba share from my Windows desktop. I'm not sure what's going on. All I did was turn off the server, unplug it for about an hour, and turn it back on. Has this happened to anyone else?

[starfleetcaptainrob]

If it will help, here's my config file. Although nothing has changed on it from when it was working fine before I shut it down to now...

[global]
   bind interfaces only = yes
   deadtime = 15
   default case = lower
   disable netbios = yes
   dns proxy = no
   domain master = yes
   encrypt passwords = true
   guest ok = yes
   guest only = yes
   hosts allow = 192.168.10.0/255.255.255.0 127.0.0.1
   hosts deny = all
   interfaces = em1
   invalid users = nobody root
   load printers = no
   max connections = 10
   netbios name = ironhide
   preferred master = yes
   preserve case = no
   printable = no
   security = share
   server string = Samba Share
   socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
   strict sync = no
   sync always = no
   syslog = 1
   syslog only = yes
   workgroup = WORKGROUP

[share1]
        create mask = 0400
        directory mask = 0700
        path = /home/fredbear/samba
        writeable = yes

[superprash2003]

is the windows pc able to ping the ubuntu?

[starfleetcaptainrob]

is the windows pc able to ping the ubuntu?

Yes, I'm also able to SSH into the machine via putty and view webpages from the apache server running on it.

[dmizer]

please post the output of:

sudo ifconfig

[starfleetcaptainrob]

please post the output of:

sudo ifconfig

Here it is:

eth0      Link encap:Ethernet  HWaddr 00:04:23:06:e8:99
          inet addr:192.168.10.10  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::204:23ff:fe06:e899/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:227011 errors:0 dropped:0 overruns:0 frame:0
          TX packets:132033 errors:0 dropped:0 overruns:0 carrier:0
          collisions:265 txqueuelen:1000
          RX bytes:25002560 (23.8 MB)  TX bytes:19500674 (18.5 MB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4462 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4462 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:392112 (382.9 KB)  TX bytes:392112 (382.9 KB)

It's just totally bizarre that it worked until I shut down the machine and nothing (that I'm aware of) changed. I guess something had to have changed...

[gnottage]

I'm wondering if samba is setup to automatically start. Perhaps trying the following will help:

sudo /etc/init.d/samba restart

[superprash2003]

reboot both the ubuntu and the windows machine and then try

[starfleetcaptainrob]

Ok, tried rebooting both the windows and linux servers and gave Samba a restart command. Neither worked. I let Vista try to diagnose the problem and it said that "ip address" is not set up to establish a connection on port "File and printer sharing (SMB)" with this computer. Could it be a closed port?

[dmizer]

okay ... i don't know why it was working before but:

• your ifconfig indicates that you're getting internet on eth0 with a local ip of 192.168.10.10.
• your smb.conf has these two lines:

bind interfaces only = yes
interfaces = em1

what this means is that smb.conf is set to only accept incomming samba connections from the em1 interface. but you do not have an ethernet connection on em1, your ethernet connection is eth0.

you could do two things to fix this.
1) simply remove those options.
2) change "interfaces = em1" to "interfaces = eth0"

then restart samba:

sudo /etc/init.d/samba restart