Dear all,
How to protect our Samba-PDC,
with _only_one_user_ at _the_sametime_ at _different_workstation_
can login into PDC.
so only one user can login into DC at the one time.
thanks.
bs
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.
This is error that im getting:
Error: You were not connected because a duplicate name exist on the
network. Go to system in Control Panel and change the computer name and
try again.
The thing is that only one computer is on the network and I already
changed the name several times
Hi All,
Im going nuts trying to get a mixed environment going. I have a couple
of problems, one related to logons and passwords which I think is a
pam.d/gdm config error on my part and one where I cant get write acccess
from the Ubuntu clients to the domain member server share. This is the
most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bork wrote:
> Sorry for the puzzle. Found this in the log:
>
> [2005/08/07 21:19:13, 0] smbd/server.c:main(802)
> smbd version 3.0.20rc1 started.
> Copyright Andrew Tridgell and the Samba Team 1992-2004
> [2005/08/07 21:19:19, 0] lib/fault
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bork wrote:
> And a message to set 'enable privileges = yes' in smb.conf
I've added code to smbd to not enumerate any thing with
privilege support is not enabled and will log a level 0
error as well.
> After setting 'enable privileges = yes'
Thomas Bork schrieb:
vmeis # net rpc rights list accounts
Password:
BUILTIN\Print Operators
No privileges assigned
BUILTIN\Account Operators
No privileges assigned
BUILTIN\Backup Operators
No privileges assigned
VMEIS\tb
[2005/08/07 21:20:58, 0] rpc_client/cli_pipe.c:rpc_api_pipe(438)
cli_p
Thomas Bork schrieb:
After setting 'enable privileges = yes' in smb.conf:
vmeis # net rpc rights grant "tb" SePrintOperatorPrivilege
Password:
Successfully granted rights.
vmeis # net rpc rights list accounts
Password:
VMEIS\tb
<- no output
Gerald (Jerry) Carter wrote:
vmeis # net rpc rights grant "tb" SePrintOperatorPrivilege
Password:
Failed to grant privileges for tb (NT_STATUS_NO_SUCH_PRIVILEGE)
Do you have 'enable privileges = yes' in smb.conf ? I should probably
prevent smbd from returning any list when the feature has been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug VanLeuven wrote:
> Gerald (Jerry) Carter wrote:
>
>> This is a release candidate of the 3.0.20 code base and
>> is provided for testing purposes only. While close to the
>
> make check
> StrCaseCmp FAIL
> AssertionError: comparison failed:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fa. Spezifikum wrote:
> BTW this unexpected behaviour seems still to exist in
> 3.0.20rc1. It is not a show stopper for me any more. I just
> thought I should mention this.
>
> With kind regards,
> Malte
>
> P.S.: I forgot to set CFLAGS to -O this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Freitas wrote:
> Please, What's this? Please, please, how to resolve ?
>
> tdb(unnamed): tdb_open_ex: /var/cache/samba/unexpected.tdb
> (835,457947) is already open in this process
Ignore it. We tried to open a tdb that was already open.
No harm d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NIGGEMYER Brant wrote:
>
> FYI updated kerberos libs from krb5-libs-1.4-3 to krb5-libs-1.4-5;
> problem still existed.
>
> ==26396== Invalid free() / delete / delete[]
> ==26396==at 0x1B909743: free (vg_replace_malloc.c:152)
> ==26396==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Effenberger wrote:
> Hi there,
>
> my CUPS server runs fine, I can print from within Windows and Linux.
> However, if I stop the printer in CUPS or some other error occurs,
> Windows clients never get notified, neither via IPP nor via SMB
> pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nigel Rantor wrote:
> Okay, and here comes some stuff that might provoke
> some reaction so I'll climb into my flame-suit.
>
> IANAL but AFAIK ETC ETC
I really doubt we have any lawyers here :-)
> The GPL only prohibits the distribution of modifie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bork wrote:
> Gerald (Jerry) Carter wrote:
>
>> This is a release candidate of the 3.0.20 code base and
>
> vmeis # net rpc rights list
> Password:
> SeMachineAccountPrivilege Add machines to domain
> SeTakeOwnershipPrivilege Take
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I read in samba-howto-collection :
"To remedy the first security issue, the ldap ssl |smb.conf| parameter
defaults to require an encrypted session (ldap ssl = on) using the
default port of |636| when contacting the directory server. When using
an
Hi,
I'm building up a new server to replace an old one running Samba2. The new
server is running Samba 3 and I'm having a problem getting it to recognise my
groups in /etc/groups.
I'm using the old smbpasswd backend, not the new tbdsam database.
I've copied my smb.conf, and the files from /usr/l
17 matches
Mail list logo
