similar to: Strange SWAT 3.0 behavior with group names containing spaces

Hello all, I'm having an issue with Winbind and I'm not sure if it's occurring by design or not. My Samba server resides in a Windows NT domain and uses winbindd to authenticate to a mixed-mode 2003 domain over a trust relationship. Everything works the way it ought to. However, every so often my users experience delays of anywhere from 30 to 60 seconds when connecting to a share,

Thanks for the response, Jerry. Is there a way for me to verify this is happening? Winbindd has been running for a few days now, and I just did a netstat and the only connections to a DC are to the off-site one, the PDC. Thanks. Sven -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: Thursday, May 22, 2003 10:19 PM To: SRuth@LANDAM.com Cc:

Hello, I've been trying for a couple of weeks now to get Samba to authenticate via Winbind to an NT domain. I've scoured Google and the mailing lists to no avail. I've tried various configurations that I've found during my searches, but none of them have worked for me. I need to be able to authenticate users, that do not have an account on the Linux box, against the NT domain,

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

I'd imagine document will answer many prayers for stumped admins These are my notes to setup SuSE Linux Enterprise Server v9 and how to configure Samba v3.04-SuSE to work as a member server in a domain Also, this document contains FULL instructions on how to setup SSL Secured SWAT (Samba Web Administration Tool) This document is a step by step guide to installing SLES and Samba. Of course

Hello all, I'm having an issue with Winbind and I'm not sure if it's occurring by design or not. My Samba server resides in a Windows NT domain and uses winbindd to authenticate to a mixed-mode 2003 domain over a trust relationship. Everything works the way it ought to. However, every so often my users experience delays of anywhere from 30 to 60 seconds when connecting to a share,

Has anyone else had problems with SWAT borking your smb.conf file if you specify your smb.conf scripts section like idealx suggests? For example: add machine script = /usr/local/sbin/smbldap-useradd -w "%u" When I save that from SWAT, I lose the script parameters inside quotes. This caused me some aggrivation this morning when I thought everything else worked just fine but the

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

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

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.. 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

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

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

Hello, I am not able to access SWAT from any other host besides the one running the SWAT daemon. No firewall blocking access on either side. # netstat -lnt | grep 901 tcp 0 0 0.0.0.0:901 0.0.0.0:* LISTEN works fine connecting from localhost using: lynx localhost:901 Unavailable using public IP on a remote host.. i.e. going into Firefox and