I'm writing this from the samba server's perspective.
If you don't have access to a gui or prefer to do things in the command line you can replace step 5 with:
First, work out which ports samba is listening on. This can be done with this command:
netstat -tulpn | egrep "samba|smbd|nmbd|winbind"
You'll see something like this:
tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd
tcp 0 0 10.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd
tcp 0 0 10.0.0.1:88 0.0.0.0:* LISTEN 43273/samba
tcp 0 0 127.0.0.1:88 0.0.0.0:* LISTEN 43273/samba
tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd
tcp 0 0 10.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd
The above example shows, that the services are listening on localhost (127.0.0.1) and the interface with IP 10.0.0.1 - each on the listed ports (139, 88, 445, and so on). Further information about samba port usage can be found here: https://wiki.samba.org/index.php/Samba_port_usage
Make a note of port and associated tcp/udp, then add lines that open these ports and protocols in /etc/sysconfig/iptables (it's probably a good plan to back up iptables before editing).
If we take the top line of output from the example above, we'd want to open TCP port 139 in iptables. This can be done by adding the following line of text to /etc/sysconfig/iptables:
-A INPUT -m state --state NEW -m tcp -p tcp --dport 139 -j ACCEPT
Say if you wanted to open UDP port 137 you could do it by adding the following line of text to /etc/sysconfig/iptables
-A INPUT -m state --state NEW -m udp -p ucp --dport 137 -j ACCEPT
You'd need to keep adding lines for any other ports that you need to have open.
Then save your changes, and restart IPtables (service iptables restart).
Hope that helps.
Best Answer
rpm -i
that source RPM on centos7spec
file, which can be used as a guide to building samba3.But we need to both agree that a samba4 problem on centos7 is not going to be accurate replicated or confirmed by building a different version of the software and smelling whether that works.
I recommend opening a new issue - here, samba.org, or with Red Hat - and letting us know what issue you're seeing so we can address the issue. Using us like marionettes for a bit of lifting to help explore a corner case miles away from your problem means we're unable to spot and help you overcome issues that you may not be aware you have.