Displaying 20 results from an estimated 2000 matches similar to: ""net rpc" commands don’t work on Samba AD DC"
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
On 02/06/2017 16:36, Rowland Penny via samba wrote:
> On Mon, 6 Feb 2017 16:16:28 +0200
> Alnis Morics via samba <samba at lists.samba.org> wrote:
>
>>
>>
>> On 02/06/2017 15:43, Rowland Penny via samba wrote:
>>> On Mon, 6 Feb 2017 14:47:21 +0200
>>> Alnis Morics via samba <samba at lists.samba.org> wrote:
>>>
>>>> I
2017 Feb 06
3
Regular users can't log in to Samba AD DC from Windows
On 02/06/2017 15:43, Rowland Penny via samba wrote:
> On Mon, 6 Feb 2017 14:47:21 +0200
> Alnis Morics via samba <samba at lists.samba.org> wrote:
>
>> I see. But I don't necessarily need homedirs and hence PAM configured
>> just to log in from Windows and access a file share from there, do I?
>> Or even just to log in on Windows to the domain.
>>
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
On 02/06/2017 13:36, Rowland Penny via samba wrote:
> On Mon, 6 Feb 2017 12:57:19 +0200
> Alnis Morics via samba <samba at lists.samba.org> wrote:
>
>>
>>
>> On 02/06/2017 11:48, Rowland Penny via samba wrote:
>>> On Mon, 6 Feb 2017 11:11:09 +0200
>>> Alnis Morics via samba <samba at lists.samba.org> wrote:
>>>
>>>>
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
On 02/06/2017 11:48, Rowland Penny via samba wrote:
> On Mon, 6 Feb 2017 11:11:09 +0200
> Alnis Morics via samba <samba at lists.samba.org> wrote:
>
>> Thank you, Rowland, for the reply.
>>
>
>> And the nss tests as per Wiki seem to pass:
>>
>
>>
>> # getent passwd Administrator
>>
2017 Jan 29
0
"net rpc" commands don’t work on Samba AD DC
Hello Alnis,
Am 29.01.2017 um 17:27 schrieb Alnis Morics via samba:
> But when I try to grant Domain Admins a SeDiskOperatorPrivilege, I get
> this:
>
> # net rpc rights grant "RW\Domain Admins" SeDiskOperatorPrivilege -U
> "RW\administrator"
> Enter RW\administrator's password:
> Could not connect to server 127.0.0.1
> Connection failed:
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
Thank you, Rowland, for the reply.
On 02/06/2017 10:44, Rowland Penny via samba wrote:
> On Mon, 6 Feb 2017 10:07:18 +0200
> Alnis Morics via samba <samba at lists.samba.org> wrote:
>
>> Hi,
>>
>> I continue setting up my FreeBSD 11.0 machine with Samba 4.4.9 built
>> from sources. (Actually, OS type and Samba version don't matter so
>> much, as I
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
Hi,
I continue setting up my FreeBSD 11.0 machine with Samba 4.4.9 built
from sources. (Actually, OS type and Samba version don't matter so much,
as I have the same problem with Debian Jessie and Samba 4.5.5)
I followed the Wiki very close. Some details from provisioning:
...
Realm [RW.LAN]:
Domain [RW]:
Server Role (dc, member, standalone) [dc]:
DNS backend (SAMBA_INTERNAL,
2017 Feb 10
2
FreeBSD-11 Samba44 DNS
On Thu, 9 Feb 2017 20:17:11 -0500
"James B. Byrne" <byrnejb at harte-lyne.ca> wrote:
>
> Does this mean that I have missed a step in provisioning? Or does it
> mean there is a defect in the packaging for FreeBSD?
>
I am wondering if you have actually fully provisioned. I have tried to
provision samba44 and, for some reason, it will not run the
provision command
2017 Mar 05
1
Samba-4.6.0rc4 on FreeBSD
Hi,
I just tried Samba-4.6.0rc4 on FreeBSD 11.0-RELEASE-p8 to see if there's
still a problem with "net rpc" commands but it crashed already at provision:
# samba-tool domain provision --use-rfc2307 --interactive
Realm [RW.LAN]:
Domain [RW]:
erver Role (dc, member, standalone) [dc]:
DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE)
[SAMBA_INTERNAL]:
DNS
2009 Jul 05
1
mbox sync failure2
Hello, list,
I'm new here and also new to Dovecot. On Friday evening (perhaps not the best
moment...) I sent the following question but it seems to have been lost
somehow:
Yesterday I had to reboot my server machine and I think there was an email
client connected from the LAN during the reboot which I did not notice then.
Now that mailbox is no longer accessible: as soon as I try to
2017 Feb 08
3
ntp and samba43 on FreeBSD-103.
On Tue, February 7, 2017 14:29, Alnis Morics wrote:
> May I ask an off-topic question?
>
> James, does saying "samba43" mean you installed this FreeBSD port or
> package? Which is known to crash during provisioning as DC. Did you
> find the solution to that issue?
>
Samba43 was installed on FreeBSD-10.3 as a binary package using the
pkg utility. Other than ignorance I
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello everyone,
when using samba 4.9.1 as a standalone filer, I need to start smbd and
nmbd, don't I?
I'm using:
/local/samba/sbin/smbd -s /local/samba-config/common/smb.conf
/local/samba/sbin/nmbd -s /local/samba-config/common/smb.conf
However smbd. Seems to ignore my lock directory:
(infra) [/local/samba-config/common] grep gencache_notrans.tdb log/smbd
Opening cache file at
2018 Oct 13
4
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello,
my smb.conf is:
[global]
workgroup = DIRECTORY
interfaces = 10.10.10.1
security = user
map to guest = Bad User
rndc command = /bin/true
[iso]
comment = ISO
browseable = No
public = Yes
guest only = Yes
writable = No
directory = /export/ISO
I'm using Debian 9.5 with samba version
2018 Jun 17
3
Connection problem due to tdb_lock failed
We are using Samba 4.6.15. We have users not being able to login. winbindd log shows this:
[2018/06/14 14:48:44.300203, 0, pid=3228] ../source3/rpc_client/cli_pipe.c:3292(cli_rpc_pipe_open_schannel_with_creds)
netlogon_creds_cli_get returned NT_STATUS_UNSUCCESSFUL
[2018/06/14 14:53:43.896350, 0, pid=3228] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)
2017 Feb 06
0
Regular users can't log in to Samba AD DC from Windows
On Mon, 6 Feb 2017 17:09:27 +0200
Alnis Morics via samba <samba at lists.samba.org> wrote:
>
> On 02/06/2017 16:36, Rowland Penny via samba wrote:
> > On Mon, 6 Feb 2017 16:16:28 +0200
> > Alnis Morics via samba <samba at lists.samba.org> wrote:
> >
> >>
> >>
> >> On 02/06/2017 15:43, Rowland Penny via samba wrote:
> >>>
2005 Mar 29
1
Problem with pdf printing
Hello,
I'm hoping someone can help me. I have several pdf printers set up and
when I print to them samba becomes unstable and several errors are
dumped to the log. These pdf printers were working when I was using
version 3.0.6. When I went to a newer version of samba the queue would
not clear on the windows side and no errors were logged. Yesterday I
upgraded to version 3.0.13-1 and the
2005 Mar 30
2
Problem with pdf printing (SOLVED)
Urs Rau wrote:
>>I start to wonder what "dammage" it would do to set lpq to
>>lpq command =/bin/true
>>for my pdf printer? ;-)
>
>
>
> Well, wonder no more sir!!!!!! I set my lpq command = /bin/true
and
> ALL QUEUES CLEAR AND ACT PROPERLY!!!!!!!!!!!! I could kiss you!
That was all I did, I can't believe it worked......thank you!!!!!!
>
2005 Jun 03
0
smbfs intermittent errors: tdb_lock failed, ERRDOS 71
Hi,
I recently upgraded an older box running as a file server for a small
company to Mandriva (Mandrake) 10.1. It's running Samba 3.0.10.1, the
default Mandrake package.
We have a custom script that mounts a Windows share using smbfs, backs
up specific directories, and unmounts when it's done. The problem is,
it's not mounting reliably.
There is an entry in /etc/fstab for the
2004 Jun 29
2
tdb lock failures
We've just gone live with a file & print server, and are having major
problems with Samba. When used out of hours, with all PCs switched on
and connected to the domain, everything works fine. However, during the
day, we have problems where users can't print to any samba-hosted
printer, Access database applications (where the database is held on the
server) won't work, or work
2005 Feb 28
1
tdb locking errors?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I was running a netbench performance test against Samba 3.0.11, and the test has
not been able to complete fully.
The samba logs contain lines such as this:
[2005/02/28 11:35:23, 1] smbd/service.c:make_connection_snum(645)
~ slave16 (192.168.133.116) connect to service netbench initially as user
BENCHLAB+slave16 (uid=10016, gid=10001) (pid