similar to: Samba Web Administration Tool (SWAT)

Displaying 20 results from an estimated 10000 matches similar to: "Samba Web Administration Tool (SWAT)"

2019 Oct 30
2
Samba Web Administration Tool (SWAT)
On 29/10/2019 17:48, Steve Litt via samba wrote: > On Thu, 11 Jul 2019 11:59:20 +0000 > Gerard Seibert via samba <samba at lists.samba.org> wrote: > >> I know that this has probably been asked before. As a long time user >> of Samba, I remember using SWAT to configure Samba. It did seem, at >> least to me, to simplify things. At the very least, it did prevent me,
2019 Oct 31
0
Samba Web Administration Tool (SWAT)
On Wed, 30 Oct 2019 08:45:47 +0000 Rowland penny via samba <samba at lists.samba.org> wrote: > On 29/10/2019 17:48, Steve Litt via samba wrote: > > On Thu, 11 Jul 2019 11:59:20 +0000 > > Gerard Seibert via samba <samba at lists.samba.org> wrote: > > > >> I know that this has probably been asked before. As a long time > >> user of Samba, I
2019 Oct 31
1
Samba Web Administration Tool (SWAT)
If you're looking for a web admin tool Webmin has a pretty decent module that works well. Thanks, Rich ----- On Oct 31, 2019, at 1:04 AM, samba samba at lists.samba.org wrote: > On Wed, 30 Oct 2019 08:45:47 +0000 > Rowland penny via samba <samba at lists.samba.org> wrote: > >> On 29/10/2019 17:48, Steve Litt via samba wrote: >> > On Thu, 11 Jul 2019 11:59:20
2019 Oct 29
0
Samba Web Administration Tool (SWAT)
On Thu, 11 Jul 2019 11:59:20 +0000 Gerard Seibert via samba <samba at lists.samba.org> wrote: > I know that this has probably been asked before. As a long time user > of Samba, I remember using SWAT to configure Samba. It did seem, at > least to me, to simplify things. At the very least, it did prevent me, > and possibly other users, from creating simple syntax errors. Hi
2006 Aug 09
10
Dovecot as LDA with Postfix
I have been attempting to replace Procmail with Dovecot as the LDA for my Postfix mail server, but without success. Below is a truncated output from the /var/log/maillog. Aug 9 11:56:20 scorpio postfix/local[4338]: 88C3FC3D1: to=<gerard at localhost.seibercom.net>, orig_to=<gerard at localhost>, relay=local, delay=1119, delays=1118/0.71/0/0.11, dsn=4.3.0, status=deferred (temporary
2011 Oct 07
0
centos 64bit Samba Web Administration Tool (SWAT)
Hello, I have installed SWAT (Samba Web Administration Tool) using http://localhost.901/ able to log in and configure the settings. So far I have configured workgroup, netbios name and set up a shared folder. This is all done on centos64bit box. Now using Windows I am able to see the shared folder and able to log in to it using the user name/password. However I am NOT able to create any files or
2019 Oct 14
2
Detect version of smb being employed
On Mon, 14 Oct 2019 13:47:34 +0100, Rowland penny via samba stated: >On 14/10/2019 13:27, Gerard Seibert via samba wrote: >> FreeBSD 12 >> Samba 4.8.12 >> >> Samba is not showing up on my Win 10 PRO machine. I can access the >> shares if I use the machines hostname or IP, though. How can I >> determine what version of ?smb? is being used? I have set ?client
2018 Dec 20
3
Problem with quota
Samba version 4.8.7, running on a FreeBSD 12.0-RELEASE amd64 system with a ZFS file system. I have a Windows 10 machine configured to do automatic backups to my FreeBSD machine on a daily basis. Since updating FreeBSD, the following errors are displayed when the backup begins. This is a truncated list. Dec 19 06:29:01 scorpio smbd[56795]: [2018/12/19 06:29:01.413635, 0]
2005 Jul 05
3
Files missing when using windows XP and samba
Hi, I am using Fedora Core 3 as a server for both Unix (Solaris and HPUX) and Windows Xp clients. The Unix clients view the files through an NFS v3 share, and windows client use samba (3.0.8-0.pre1.3). When looking at a directory from the server, or from a Unix client, I can see 132 files. However, from the Windows client, I can only see 65 files. There appear to be nothing special about the
2019 Oct 14
1
Detect version of smb being employed
On 10/14/19 12:00 PM, Roy Eastwood via samba wrote: >> -----Original Message----- >> From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Gerard Seibert via samba >> Sent: 14 October 2019 17:09 >> To: samba at lists.samba.org >> Cc: Gerard Seibert >> Subject: Re: [Samba] Detect version of smb being employed >> >> On Mon, 14 Oct 2019
2019 Oct 14
3
Detect version of smb being employed
FreeBSD 12 Samba 4.8.12 Samba is not showing up on my Win 10 PRO machine. I can access the shares if I use the machines hostname or IP, though. How can I determine what version of ?smb? is being used? I have set ?client max protocol = SMB3? in the config file; however, I am not sure if it is being used. Thanks! -- Gerard -------------- next part -------------- A non-text attachment was
2018 Dec 21
1
Problem with quota
On Thu, 20 Dec 2018 16:59:54 -0800, Jeremy Allison stated: >On Thu, Dec 20, 2018 at 12:08:02PM +0000, Gerard Seibert via samba wrote: >> Samba version 4.8.7, running on a FreeBSD 12.0-RELEASE amd64 system with a >> ZFS file system. >> >> I have a Windows 10 machine configured to do automatic backups to my >> FreeBSD machine on a daily basis. Since updating
1999 Oct 28
1
Root privilege for users in swat
Hi, I have been searching the mailing list, but i couldn't found the aswer for this one : How do i give root privilege for other users in swat, so that other users can create shares, and change other configs using swat ? Thanks in advance. Alexandre.
2019 Mar 19
2
Samba warning message
Samba 4.8.9 FreeBSD 12.0-RELEASE-p3 / amd64 Since updating both FreeBSD and Samba, I have been getting the following screen pop-ups incessantly. They are always the same except for the time. IP 102.168.0.102 is a Win10 PRO / amd64 machine. I never received any warnings before updating. <quot> Mar 19 08:23:58 scorpio nmbd[11202]: [2019/03/19 08:23:58.049153, 0]
2006 Oct 02
3
Dovecot as LDA
FreeBSD 6.1-RELEASE-p8 postfix-current-2.4.20060903,3 dovecot-1.0.r7 I am experiencing a problem with dovecot as an LDA. It will not deliver mail unless the mail directory is chmod'd to 1777. Below is an example of the log file output. The dovecot.log file had over a hundred entries similar to this: deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1123.cd38cd4d82e1368f)
2019 Mar 19
1
Samba warning message
On Tue, 19 Mar 2019 13:02:40 +0000, Rowland Penny via samba stated: >On Tue, 19 Mar 2019 12:37:08 +0000 >Gerard Seibert via samba <samba at lists.samba.org> wrote: > >> Samba 4.8.9 >> FreeBSD 12.0-RELEASE-p3 / amd64 >> >> Since updating both FreeBSD and Samba, I have been getting the >> following screen pop-ups incessantly. They are always the same
2019 Jan 18
1
Samba, ZFS and FreeBSD 12
On Fri, 18 Jan 2019 12:14:47 +0000, Rowland Penny via samba stated: >On Fri, 18 Jan 2019 11:15:38 +0000 >Gerard Seibert via samba <samba at lists.samba.org> wrote: > >> FreeBSD 12.0-RELEASE-p2 GENERIC amd64 >> samba48-4.8.7 >> >> Ever since updating from FreeBSD 11 to FreeBSD 12, I have experienced >> a problem with samba. While still on FreeBSD 11,
2019 Jan 18
2
Samba, ZFS and FreeBSD 12
FreeBSD 12.0-RELEASE-p2 GENERIC amd64 samba48-4.8.7 Ever since updating from FreeBSD 11 to FreeBSD 12, I have experienced a problem with samba. While still on FreeBSD 11, I configured a Windows 10 machine to write backups of selected directories to my FreeBSD machine. That worked perfectly. No problems were detected and everything was backed up correctly. However, after updating to FreeBSD 12 a
2006 Jan 03
1
smbclient not displaying shares
I have just recently installed Samba. I have two WinXP Pro machines networked to a FreeBSD 5.4 computer. The Printer is connected to one of the WinXP machines currently. This is the output of the 'smbclient' command. smbclient -U user-name -L winxp Password: Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment ---------
2006 Feb 04
1
Usernames & Passwords
I thought I had posted this previously, but I cannot seem to find any record of it. I am using Samba in a mixed network (WinXP and FreeBSD 5.4). There is no domain involved. Using the following command, I can access a share on one of the WinXP machines: smbclient //SERVER/SHARE -u NAME%PASSWORD I now find that I can also access the share using an incorrect 'NAME' or 'PASSWORD'