In server args you have -s /tftpboot, but in your post you said the dir you're using is /tftpserver. The -s and path means the directory that you are using as the TFTP root directory. Change this to the path or the directory you want to use.
If /tftpboot doesn't exist you'll see an error in /var/log/messages and the daemon won't actually start.
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
On a CentOS 5.8 system I have (like the one you are using), it appears that the
smbandnmbservices are managed together through the/etc/init.d/smbfileWhereas on a CentOS 6.3 system they are managed as separate services. So your
will also have configured nmb.
I don't know why the page you reference says to use the separate services. The RHEL 5 deployment guide(21.2.1) says nmb is controlled by smb whereas the the RHEL 6 deployment guide (17.1.2.1) says they are separate services.