Earlier, I had setup samba using SWAT and, despite some early problems that were perhaps related to Windows, I finally got it working. Now I am motivated to add a share to support Microsoft FrontPage, which is the tool I will be using to setup my website. I do have Apache running on the server (http://www.hapgoods.com returns the Apache default page). Some relevant commands and such:
http://www.hapgoods.com:901
This will start the SWAT utility.
/etc/samba/smb.conf
Samba configuration file
smbclient -L localhost -U%
See the current public shares
testparm -v -s
See the value of all parameters
pdbedit -l
List all samba users
smbstatus
Check status of smb shares
I changed some parameters in an attempt to get the Windows clients (running WinXP Home with SP2) to detect config changes on the server more quickly:
preferred master = Yes
Was “Auto”
Os level = 65
Was 20
Domain master = Yes
Was “Auto”
These changes were recommended by Linux Home Networking (http://www.linuxhomenetworking.com/linux-hn/samba.htm).
Changed Web share to not be read-only.
Changed Global section to only allow connections from local network (192.168.1.0).
Changed attributes of /var/www/html (the Web share target) to be 777 -this is a BAD solution to the permissions issues of Apache that I will need to resolve.
01/05/2005 more samba
Today I am going to try to improve on the samba configuration. Particularly for Matt, this is the primary reason to have bought a server.
First, I got tired of the out-of-date documentation on www.linuxhomenetworking.com. There are also some frustrating typos (there is no such global parameter as domain, despite table 10-2). So I went to the source: www.samba.org. I found some excellent documentation.
First, I want to make sure that all users can access the samba shares. I was having problems using account pah1 to access samba -despite the fact that pah1 was a valid Linux user and had a share (using the homes section). The key: I forgot to use the smbpasswd command to create the samba user.
smbpasswd -a pah1
The samba.org website also gives lots of examples of using smbclient under Linux to do testing.
21/08/2005 swat
I had originally built a basic swat configuration that allowed maintenance from only one PC on my network. That worked well until this past weekend when I tried to figure out some other problems with samba. I had forgotten that I had limited swat access to only one PC. So today I began the quest for a smarter swat security configuration. Basically, I want to be able to administer samba remotely from ANY machine on my network. But I do not want anyone outside my network to be able to access it at all. Here is an appropriate configuration:
Screen clipping taken: 22/08/2005, 16:14
Don’t forget to reload the config files:
[root@ducati xinetd.d]# service xinetd restart
Also, I had to adjust the firewall settings with system-config-securitylevel to allow the swat protocol to get through.
