That matches what I have been thinking. However the IPv6 is up, and isn't
that the same interface? There is only one mac address device, the NIC.
If this is the case, then how do I delay the smb start up? I've been using
linux for decades, but only infrequently, soI have to relearn these things
every couple of years. I know it's somewhere in the init.d scripts for run
level 3 and 5
Thanks.
-Scott
On Sun, Oct 13, 2013 at 12:05 AM, Gregory Sloop gr...@sloop.net wrote:
[I may be completely wrong, but I'm too lazy to look it up, but
perhaps it's a place to start...]
I seem to recall that if the interface isn't up and ready, Samba, when
it comes up, won't listen on that interface unless it's explicitly
defined.
Is there a chance that the IPv4 interface isn't up when the Samba
loads, but IPv6 is? [Or perhaps IPv6 gets treated differently...]
Something to investigate - but remember, I'm not claiming to be right.
:)
-Greg
SW I am running SUSE 12.0 I have had this problem on another machine
months
SW ago, but never solved it. I have done many searches, but have come up
empty.
SW When booted, port 139 is not open on IPv4. There os no 0.0.0.0:139
listening.
SW HOWEVER: :::139 is listening. SO I know it is open on IPv6.
SW When I try to gain remote access through a share, the machine is not
found.
SW When I try to telnet to port 139, the connection is refused.
SW To solve it, I have to manually restart smb. So this is some kind of
SW 'first bootup' problem. All the searches I came up with all describe a
SW problem that it just isn't working at all. This is just that it
doesn't
SW work until I restart the daemon.
SW It's annoying to work around, especially when I'm using a VM and
SW starting/stopping the machine often.
SW Can anyone advise on what this problem is, or how to fix it?
SW -Scott
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
