I think I have a problem with samba trying to use ONLY IPV6, and refusing connections because of it. Read on.
Over the past few months I have had a "connection refused" problem between my client machines and my home server [Ubuntu 10.04]. I somehow managed to get it back running each time. At one point, I thought it was something weird with the samba.conf, and I was making tweaks. But now I think that it was shutting things down and turning them back on until it worked.
As a result of Hurricane Sandy, I powered everything down. On restoring power, the problem occurred. Since I had already tweaked the samba config, I went looking elsewhere and found this VERY odd (to me) result:
Code:
mark@ubuntu-server:~$ sudo netstat -apn | grep LISTEN | grep smb
[sudo] password for mark:
tcp6 0 0 fe80::20c:f1ff:fe7f:445 :::* LISTEN 1169/smbd
tcp6 0 0 fe80::20c:f1ff:fe7f:139 :::* LISTEN 1169/smbd
This didn't seem like it should be. Only tcp6? I stopped and restarted Samba. Same results.
Code:
mark@ubuntu-server:~$ sudo netstat -apn | grep LISTEN | grep smb
tcp6 0 0 fe80::20c:f1ff:fe7f:445 :::* LISTEN 1169/smbd
tcp6 0 0 fe80::20c:f1ff:fe7f:139 :::* LISTEN 1169/smbd
But, since the process # was the same, I think for some reason it did not properly stop and restart. IDK.
So I stopped and started the server.
Logged back in, and then restarted samba. This time, I got:
Code:
mark@ubuntu-server:~$ sudo netstat -apn | grep LISTEN | grep smb
tcp 0 0 172.16.0.104:445 0.0.0.0:* LISTEN 2456/smbd
tcp 0 0 172.16.0.104:139 0.0.0.0:* LISTEN 2456/smbd
tcp6 0 0 fe80::20c:f1ff:fe7f:445 :::* LISTEN 2456/smbd
tcp6 0 0 fe80::20c:f1ff:fe7f:139 :::* LISTEN 2456/smbd
That looked better, and it worked better. Now all the machines are connecting again.
What is going on with Samba? Why is it trying to use only IPV6 addresses? And what should I do to prevent this?
Bookmarks