similar to: SWAT : use on an include file

Hi.. I'm running Samba 2.0.7 on a RH 6.0 box... Now, this box is using NIS for authentication, such that I have no entry in the passwd file, but show up with a `ypcat passwd`. I have made a group called 'swat' and have added myself to it, such that doing a `groups wkim` lists swat as one of my groups. I then `chgrp swat smb.conf` and `chmod 664 smb.conf`. Yet, if I try to access

Hello, I have recently installed RedHat9 on my local server. It is meant to be a HTTP production server for my company. In RH9, SWAT doesn't come as standard. I therefore tried to install the RPM package found on the red hat nerwork : - samba-swat-2.2.7a-7.9.0.rpm and samba-swat-2.2.7a-8.9.0.rpm I would like to report that both failed at installation. A dialog box opened saying : reading

I have recently compiled and install samba 2.0.7 on a Alpha server running Tru64 5.1 . I do have SWAT install ed as well and i have modified both /etc/services and /etc/inetd.conf to include the configs for swat. I then point the browser at localhost:901 and it prompts for a login. I login in as root, and give the correct password, but it will not authenticate me. I can (via command line) add

Hi I have a PDC with an LDAP backend that i want to use SWAT to give users the option to change their password via the web interface. I cant seem to be able to get SWAT to authenticate any users it always gives me an authorization error. Is swat with an LDAP backend supported? Cheers. David.

Okay, here's what you need to do. You have to configure apache. This won't be too hard. You will need to edit the httpd.conf located in /etc/httpd/conf directory. Look through the httpd.conf file until you find this line: #Servername localhost It may or may not have the # in front of it. You need to edit this line and make it say: Servername yourservernamegoeshere For example,

I've been trying to find someone who can solve this problem. Unfortunately without any luck. Maybe someone on this site can help, here goes. I'm running TRU64 UNIX version 5.0a on my Alphaserver with Samba 2.07. When i try to access SWAT i am unable to login with the ROOT account. If i login with my own privileged account I am successful, but i only receive the basis 4 options for

On Mon, 5 May 2003, Anthony Watters wrote: > Since I have Samba working already, is there a way to install just SWAT? ie; > *.tar.gz file? No need if you have already installed the SWAT RPM. > > I did also try and re-install the RPM file samba-swat-2.2.7a.9.0.i386.rpm > using the rpm manager. it seemed to take 5 seconds, so I am not sure what > really occurred other than SWAT

I have a Red Hat 9 file server and I have been unable to use swat to configure the smb.conf file. I have samba-swat installed and the following in /etc/xintetd: ================================================================= # default: off # description: SWAT is the Samba Web Admin Tool. Use swat \ # to configure your Samba server. To use SWAT, \ # connect to port

Dear samba-ers, I have installed SWAT so that my samba users can change their passwords easily and remotely as they do not have login access to the samba server. Broadly speaking my problem is that when registered as a user, it seems that swat cannot access the file /var/lib/samba/private/secrets.tdb Version info: Linux platform: CentOS 6.5 Linux Kernel: 2.6.32-431 Samba: 3.6.9-167.el6_5

Having a little trouble with SWAT in Samba 3.0.3. When an option in smb.conf contains quotes, for example: add group script = /path/to/addgroupscript "%g" SWAT will, upon parsing smb.conf, display add group script = /path/to/addgroupscript and committing it causes the quoted portion to be dropped in smb.conf. Note that anything in double quotes (or, rather, after the first double

Hi all, OS: suse 9 samba ver: 3.0.2 linux:/etc/xinetd.d # cat swat service swat { port = 901 socket_type = stream wait = no only_from = localhost 10.1.1.10 user = root server = /usr/sbin/swat log_on_failure += USERID # disable = yes linux:/etc # cat inetd.conf swat stream tcp nowait.400 root /usr/sbin/swat swat linux:/etc # cat services | grep 901 swat

hola, habla usted ingles? bueno, revise bien que 'xinetd' este instalado y corriedo como servicio: ps -ae | grep xinetd si resulta que si, entonces revise el documento de configuracion de swat (/etc/xinetd.d/swat): # default: off # description: SWAT is the Samba Web Admin Tool. Use swat \ # to configure your Samba server. To use SWAT, \ # connect to port 901

G'day.... Simple solution... Uninstall samba/swat packages... Reinstall... test. swat should work "right out of the box" ... All the best... Mike --- Michael S. E. Kraus Administration Capital Holdings Group (NSW) Pty Ltd mkraus@capitalholdings.com.au phone (02) 9955 8000 fax (02) 9955 8144 "Mike Stewart" <mike@powys-training.co.uk> 21/11/2002 08:15 PM Please

Hello everyone, I've noticed something odd with SWAT version 3.0 and above. Specifically, for fields such as "read list" and "write list", any spaces in group names are replaced with a comma and a space when changes are committed via SWAT. For all previous versions of SWAT I've been able to use group names with spaces without this mangling from SWAT. At first I

I have downloaded, build and installed samba-4.0.9 from source on two separate boxes running RHEL6.4. My problem is that despite having identical configurations, swat is running on one server and not on the other. Here is my xinetd conf service swat { port = 901 socket_type = stream wait = no only_from = 192.168.1.0/24 user = root server =

Hello, I'm using Suse Linux v 7.0 Professional. I successfuly compiled Samba v 2.2.2 with the command : ./configure \ --with-pam --with-tdbsam --with-winbind \ --with-acl-support --with-smbwrapper All works except SWAT ! However, I checked if the line "swat 901/tcp" is in the file /etc/services and it's in order My file /etc/inetd.conf contains the line : swat stream tcp

Hi, Is there anybody who succesfully compiled 2.0.4b INCLUDING LDAP support "--with-ldap"? And on Solaris 2.6 (2.x)? I first had configure run with also the NISPLUS option, but didn't want that after all. I had a lot of problems trying to get Samba accepting connections anyway. That compiled oke: there's a little bug? in the SAMBA source somewhere however, because I always get

So John, are you the "SWAT guru" for Samba? I like the idea of having an expert for each area of Samba. Just a thought - if you are looking for further feedback regarding SWAT, you may want to post a message to the Samba forum on tek-tips website. (goto www.tek-tips.com and search for forum called "Andrew Tridgell : Samba") There are currently over 800 members of the

I'm looking at having my general Samba users change their own passwords on my Linux server using SWAT. Is there a way that I can have them have access to the password changing view and not be able to see the configuration and status information. Is there an easy way for those "button" to not appear on the web page? Roy Costa roycosta at us.ibm.com

What's the deal with SWAT authentication? I have a Freebsd 4-Stable box running SWAT from the Samba 2.0.7 port and I can log into SWAT as a regular user (ie, not root but has a smbpasswd entry) and make any changes I want to the smb.conf file -- which is 0644 root.wheel. I'm presuming this is because my inetd.conf entry for SWAT has it running as root as per the example. Is this how