On 01/02/15 06:43, Tom H wrote:
> On Thu, Jan 1, 2015 at 4:01 PM, Bob Goodwin <[log in to unmask]> wrote:
>> I ran a system update on an SL-7 server and that seems to have messed up
>> samba. I can ssh into the system but can't mount it as a samba share.
>>
>> [root@box10 bobg]# mount //192.168.1.48/myshare   /mnt/box48/
>> Password for [log in to unmask]:  ********
>> Unable to find suitable address.
>>
>> This has worked without a problem until now. Any thoughts on what might be
>> my problem appreciated.
> Which packages were updated?
Perhaps 100 items ending with:

Dec 12 04:01:19 Installed: samba-4.1.1-37.el7_0.x86_64
Dec 12 04:02:25 Installed: alacarte-3.7.90-8.el7.noarch
Dec 12 12:13:50 Installed: system-config-users-docs-1.0.9-6.el7.noarch
Dec 12 12:13:51 Installed: system-config-users-1.3.5-2.el7.noarch

Which makes Samba suspect.

I also tried booting to the previous kernel. That made no difference.
>
> Did you change your samba config?
No and it appears not to have been changed:

[root@box48 bobg]# ll  /etc/samba/smb.conf* -t
-rw-r--r--. 1 root root 12175 Dec 22 12:16 /etc/samba/smb.conf
-rw-r--r--. 1 root root 12130 Dec 22 11:48 /etc/samba/smb.conf~
-rw-r--r--. 1 root root 11702 Dec 15 10:24 /etc/samba/smb.conf.works
-rw-r--r--. 1 root root 11630 Dec 12 09:03 /etc/samba/smb.conf.default

It looks like it still has the entries I made last time.
>
> Did you change your iptables config?
No, and stopping firewalld had no effect, I also tried setenforce 0.
>
> Did you reboot after the updates?
Yes, a number of times now.
>
> Do the client or server logs give you more info?
The server:

[root@box48 bobg]# journalctl --since -60m
......  snip  ..
Jan 02 10:01:01 box48 CROND[22259]: (root) CMD (run-parts /etc/cron.hourly)
Jan 02 10:01:01 box48 run-parts(/etc/cron.hourly)[22262]: starting 0anacron
Jan 02 10:01:01 box48 run-parts(/etc/cron.hourly)[22269]: finished 0anacron
Jan 02 10:01:01 box48 run-parts(/etc/cron.hourly)[22271]: starting 
0yum-hourly.cron
Jan 02 10:10:01 box48 systemd[1]: Starting Session 210 of user root.
Jan 02 10:10:01 box48 systemd[1]: Started Session 210 of user root.
Jan 02 10:10:01 box48 CROND[22370]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jan 02 10:20:01 box48 systemd[1]: Starting Session 211 of user root.
Jan 02 10:20:01 box48 systemd[1]: Started Session 211 of user root.
Jan 02 10:20:01 box48 CROND[22494]: (root) CMD (/usr/lib64/sa/sa1 1 1)

While the client box shows:

Jan 02 10:18:12 box10 kernel: CIFS VFS: Error connecting to socket. 
Aborting operation.
Jan 02 10:18:12 box10 kernel: CIFS VFS: cifs_mount failed w/return code 
= -113

I'm curious about the difference in time. I normally block WAN in the 
router for the servers, I also have a separate NFS box.
>
> Does "smbclient -L ..." list the share(s)?
[root@box48 bobg]# smbclient -L myshare/
Enter bobg's password:
Connection to myshare failed (Error NT_STATUS_UNSUCCESSFUL)

I even tried resetting the smb password.

Thanks to all for responding,

Bob

-- 
http://www.qrz.com/db/W2BOD
box10  Fedora-21/64bit Linux/XFCE