10 More Discussions You Might Find Interesting
1. Red Hat
Hi,
I have been trying to install SWAT on redhat 6 for samba4. The samba server was installed by another administrator but not swat. Please find output of yum install samba-swat in the attached file (2 Replies)
Discussion started by: p2bas
2 Replies
2. UNIX for Dummies Questions & Answers
I have made a complete botch of trying to install both ssh and samba, having followed numerous tutorials - all claiming to be easy to follow and stating that it is easy.
The last attempt @ ssh was going really well until the copy id stage
roy@roy-1011PX:~$ ssh-copy-id -i /home/roy/.ssh/id_dsa.pub... (8 Replies)
Discussion started by: Royalist
8 Replies
3. Solaris
Hi all, I'm trying to update my samba 3.5.10 to 3.6.5 due to security CVE issued with 3.5.
I downloaded and unzipped, did the make and make install and the ./configure.
I didn't use any changes to it and it said it installed correctly added it to my path and it looks like it's operating... (6 Replies)
Discussion started by: mattymatt79
6 Replies
4. AIX
I have created an LPAR and the next step is to get SAMBA installed, I have mounted our NIM server up and copied over the SAMBA binaries .bff files. How do i install these? i tried doing this through SMIT but had no luck..? Any help would be greatly appreciated. AIX OS 6.1 (2 Replies)
Discussion started by: audis$
2 Replies
5. Red Hat
Hi,
I have installed RHEL 5.2 for a specific reason.
Anyway I would really like to use SWAT to administer Samba. Samba is currently installed and working almost successfully however SWAT would make life a bit easier.
I have tried rpm -ivh samba-swat but it can't find the file. ... (1 Reply)
Discussion started by: drag0n
1 Replies
6. UNIX for Advanced & Expert Users
Hi I have an issue with a client. He was able to use his mounted Samba share for a long time. However, a couple of days ago, he wasn't able to access all of his files all of a sudden. He still see's the share and majority of the files, but not some that he needs.
I checked with Secure CRT on... (1 Reply)
Discussion started by: zixzix01
1 Replies
7. SCO
Hi all.
I'm having real trouble authenticating users against active directory for my SCO UnixWare 7.1.4 box running samba 3.0.24 (installed via Maintenance pack 4). I can list AD users/groups (after overcoming several hiccups) with wbinfo -g / wbinfo -u. I can use id to get a view an ad user ie:... (0 Replies)
Discussion started by: silk600
0 Replies
8. Red Hat
hi
Recently the above option has stopped working all together. On clicking on this option it appears as though the window will open as the outline of the box appears but nothing more.
On running this from a command prompt within the GUI , I get the following error:
The last line... (0 Replies)
Discussion started by: timcs
0 Replies
9. UNIX for Dummies Questions & Answers
solaris can't support pkill command:( (2 Replies)
Discussion started by: cloudsmell
2 Replies
10. UNIX for Dummies Questions & Answers
i am run SUSE 6.4 with apache that i built and maintain to serve my dads website, (www.farragutmarine.com for anyone who cares) anyway i am running samba and i have a huge problem, throughout the day, everything goes fine, but then my server will come to a grinding halt, if i try to telnet in or... (4 Replies)
Discussion started by: norsk hedensk
4 Replies
SWAT(8) SWAT(8)
NAME
swat - Samba Web Administration Tool
SYNOPSIS
swat [ -s <smb config file> ] [ -a ]
DESCRIPTION
This tool is part of the Samba suite.
swat allows a Samba administrator to configure the complex smb.conf(5) file via a Web browser. In addition, a swat configuration page has
help links to all the configurable options in the smb.conf file allowing an administrator to easily look up the effects of any change.
swat is run from inetd
OPTIONS
-s smb configuration file
The default configuration file path is determined at compile time. The file specified contains the configuration details required by
the smbd server. This is the file that swat will modify. The information in this file includes server-specific information such as
what printcap file to use, as well as descriptions of all the services that the server is to provide. See smb.conf for more infor-
mation.
-a This option disables authentication and puts swat in demo mode. In that mode anyone will be able to modify the smb.conf file.
Do NOT enable this option on a production server.
INSTALLATION
After you compile SWAT you need to run make install to install the swat binary and the various help files and images. A default install
would put these in:
o /usr/local/samba/bin/swat
o /usr/local/samba/swat/images/*
o /usr/local/samba/swat/help/*
INETD INSTALLATION
You need to edit your /etc/inetd.conf and /etc/services to enable SWAT to be launched via inetd.
In /etc/services you need to add a line like this:
swat 901/tcp
Note for NIS/YP users - you may need to rebuild the NIS service maps rather than alter your local /etc/services file.
the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024
presents an obscure security hole depending on the implementation details of your inetd daemon).
In /etc/inetd.conf you should add a line like this:
swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat
One you have edited /etc/services and /etc/inetd.conf you need to send a HUP signal to inetd. To do this use kill -1 PID where PID is the
process ID of the inetd daemon.
XINETD INSTALLATION
Newer Linux systems ship with a more secure implementation of the inetd meta-daemon. The xinetd daemon can read configuration inf9ormation
from a single file (i.e. /etc/xinetd.conf) or from a collection of service control files in the xinetd.d/ directory. These directions
assume the latter configuration.
The following file should be created as /etc/xientd.d/swat. It is then be neccessary cause the meta-daemon to reload its configuration
files. Refer to the xinetd man page for details on how to accomplish this.
## /etc/xinetd.d/swat
service swat
{
port = 901
socket_type = stream
wait = no
only_from = localhost
user = root
server = /usr/local/samba/bin/swat
log_on_failure += USERID
disable = No
}
LAUNCHING
To launch SWAT just run your favorite web browser and point it at "http://localhost:901/".
Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password
sniffing as passwords will be sent in the clear over the wire.
TROUBLESHOOTING
One of the common causes of difficulty when installing Samba and SWAT is the existsnece of some type of firewall or port filtering software
on the Samba server. Make sure that the appropriate ports outlined in this man page are available on the server and are not currently being
blocked by some type of security software such as iptables or "port sentry". For more troubleshooting information, refer to the additional
documentation included in the Samba distribution.
FILES
/etc/inetd.conf
This file must contain suitable startup information for the meta-daemon.
/etc/xinetd.d/swat
This file must contain suitable startup information for the xinetd meta-daemon.
/etc/services
This file must contain a mapping of service name (e.g., swat) to service port (e.g., 901) and protocol type (e.g., tcp).
/usr/local/samba/lib/smb.conf
This is the default location of the smb.conf(5) server configuration file that swat edits. Other common places that systems install
this file are /usr/samba/lib/smb.conf and /etc/smb.conf . This file describes all the services the server is to make available to
clients.
WARNINGS
swat will rewrite your smb.conf file. It will rearrange the entries and delete all comments, include= and copy=" options. If you have a
carefully crafted smb.conf then back it up or don't use swat!
VERSION
This man page is correct for version 2.2 of the Samba suite.
SEE ALSO
inetd(5), smbd(8) smb.conf(5) xinetd(8)
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
Source project similar to the way the Linux kernel is developed.
The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of
Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter
19 November 2002 SWAT(8)