similar to: NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC

Displaying 20 results from an estimated 10000 matches similar to: "NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC"

2017 Oct 16
2
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
On Mon, 16 Oct 2017 19:06:20 +0100 Richard Connon via samba <samba at lists.samba.org> wrote: > Hi, > > I provided the dump of all the conf files to Rowland by email but in > case anyone else is curious they are also here: > > http://www.irconan.co.uk/dc.tar http://www.irconan.co.uk/member.tar > I didn't get it, so I downloaded it ;-) Is the member server
2017 Oct 16
0
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
Hi, I provided the dump of all the conf files to Rowland by email but in case anyone else is curious they are also here: http://www.irconan.co.uk/dc.tar http://www.irconan.co.uk/member.tar I tried providing -S to the join command which didn't change the behaviour. It doesn't seem to have trouble finding the DC, only when connecting to the RPC server. Cheers, Richard On 16/10/2017
2017 Oct 17
1
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
On 17/10/2017 14:08, Richard Connon via samba wrote: > On 17/10/2017 13:56, Rowland Penny via samba wrote: > >> On Tue, 17 Oct 2017 13:18:46 +0100 >> Richard Connon via samba <samba at lists.samba.org> wrote: >> >>> >>> On 17/10/2017 09:54, Rowland Penny via samba wrote: >>>> On Tue, 17 Oct 2017 09:29:00 +0100 >>>> Richard
2017 Oct 17
3
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
On Tue, 17 Oct 2017 09:29:00 +0100 Richard Connon via samba <samba at lists.samba.org> wrote: > On 16/10/2017 19:30, Rowland Penny wrote: > > > > Is the member server using DHCP ? > Yes. Both test hosts are using DHCP with static leases for IP > addresses but not for DNS domains or nameservers. I wouldn't do this, I would give the DC a fixed ipaddress. > >
2017 Oct 17
2
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
On Tue, 17 Oct 2017 13:18:46 +0100 Richard Connon via samba <samba at lists.samba.org> wrote: > > > On 17/10/2017 09:54, Rowland Penny via samba wrote: > > On Tue, 17 Oct 2017 09:29:00 +0100 > > Richard Connon via samba <samba at lists.samba.org> wrote: > > > >> On 16/10/2017 19:30, Rowland Penny wrote: > >>> Is the member server using
2017 Oct 16
3
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
On Mon, 16 Oct 2017 17:01:29 +0100 Richard Connon via samba <samba at lists.samba.org> wrote: > To try and narrow down this issue I tried to setup a test environment > using two fresh install Debian 9.2 VMs, now running samba 4.5.12 > since it was updated in Debian. > > I provisioned a new domain using `samba-tool domain provision` on the > first VM, let it generate the
2017 Oct 17
0
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
On 16/10/2017 19:30, Rowland Penny wrote: > On Mon, 16 Oct 2017 19:06:20 +0100 > Richard Connon via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I provided the dump of all the conf files to Rowland by email but in >> case anyone else is curious they are also here: >> >> http://www.irconan.co.uk/dc.tar http://www.irconan.co.uk/member.tar
2017 Oct 04
2
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
Hi, I have a samba 4.5.8 AD DC (debian 9.1 package) which is having problems with RPC requests. This DC has been updated from the wheezy-backports package (4.1.17) via the jessie package (4.2.14) but I'm not sure if RPC worked immediately before the upgrade either since most of the time it only serves LDAP and krb5. Connecting using RSAT from windows gives "RPC Server
2017 Oct 17
0
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
On 17/10/2017 13:56, Rowland Penny via samba wrote: > On Tue, 17 Oct 2017 13:18:46 +0100 > Richard Connon via samba <samba at lists.samba.org> wrote: > >> >> On 17/10/2017 09:54, Rowland Penny via samba wrote: >>> On Tue, 17 Oct 2017 09:29:00 +0100 >>> Richard Connon via samba <samba at lists.samba.org> wrote: >>> >>>> On
2017 Oct 16
0
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
To try and narrow down this issue I tried to setup a test environment using two fresh install Debian 9.2 VMs, now running samba 4.5.12 since it was updated in Debian. I provisioned a new domain using `samba-tool domain provision` on the first VM, let it generate the smb.conf itself, and configured it using the BIND9_DLZ DNS backend. I tried to join the domain using a second Debian 9.2 VM
2017 Oct 16
0
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
Hi, I've attached tarballs with the requested files for each of my test DC and member. The domain was provisioned with the exact command: `samba-tool domain provision` selecting BIND9_DLZ and specifying the realm and workgroup as seen in the smb.conf files. Regards, Richard On 16/10/2017 17:26, Rowland Penny via samba wrote: > On Mon, 16 Oct 2017 17:01:29 +0100 > Richard Connon
2017 Oct 17
0
NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC
On 17/10/2017 09:54, Rowland Penny via samba wrote: > On Tue, 17 Oct 2017 09:29:00 +0100 > Richard Connon via samba <samba at lists.samba.org> wrote: > >> On 16/10/2017 19:30, Rowland Penny wrote: >>> Is the member server using DHCP ? >> Yes. Both test hosts are using DHCP with static leases for IP >> addresses but not for DNS domains or nameservers. >
2015 Mar 09
5
"failed to lookup DC info for domain over rpc" when joining samba4 domain
Hi, I have an existing samba4 domain with 2 domain controllers on different sites. Both domain controllers are running samba 4.1.17 Until recently the domain operated exactly as expected. I recently tried to join a new machine to the domain and received the error: Failed to join domain: failed to lookup DC info for domain 'ADS.CONNON.ME.UK' over rpc I'm not sure what has triggered
2015 Mar 09
2
"failed to lookup DC info for domain over rpc" when joining samba4 domain
On 09/03/2015 22:07, Rowland Penny wrote: > On 09/03/15 21:59, Richard Connon wrote: >> On 09/03/2015 21:59, Rowland Penny wrote: >>> How did you try to join the machine to the domain ? I think I know, >>> but it would like you to confirm my suspicions. >> >> Hi Rowland, >> >> This output was generated with `net ads join >>
2015 Mar 10
2
"failed to lookup DC info for domain over rpc" when joining samba4 domain
Hi Rowland, Please see comments inline. On 10/03/15 08:51, Rowland Penny wrote: > Your DC's must point to themselves for DNS and your domain clients must > point to the DC's, anything outside the domain the DC's will be obtain > from the forwarders set on them. This is contrary to what the wiki says. https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server This page
2017 Aug 09
3
cannot join windows 7 samba4-ad-dc fresh install, get NT_STATUS_INTERNAL_ERROR
hi, can you post a ipconfig /all from the windows pc also. a quick look at the server config looks ok to me. and does smbclient -L $(hostname -f) -U% -m smb2 work. greetz, Louis > Op 9 aug. 2017 om 17:23 heeft Vladimir Frelikh via samba <samba at lists.samba.org> het volgende geschreven: > > Sorry forgot to mention samba version and build options: > > samba -b >
2017 Aug 10
0
cannot join windows 7 samba4-ad-dc fresh install, get NT_STATUS_INTERNAL_ERROR
hi, here is the output from win 7 machine, cutted non-us local symbols are substituted by [cut]: Windows IP Configuration Host Name . . . . . . . . . . . . : testing Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter [cut]: Connection-specific DNS Suffix
2010 Jul 28
2
[Bug 1802] New: Ability to tunnel socket files for more flexible permissions
https://bugzilla.mindrot.org/show_bug.cgi?id=1802 Summary: Ability to tunnel socket files for more flexible permissions Product: Portable OpenSSH Version: 5.5p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Miscellaneous AssignedTo:
2015 Mar 09
4
"failed to lookup DC info for domain over rpc" when joining samba4 domain
On 09/03/2015 22:36, Rowland Penny wrote: > Hmm, everything looks ok and it shouldn't matter whether you use the > standard 3.6 from debian or 4.1.17 from backports except for the fact > that 3.6 isn't just old, it is EOL , so you may have to rely on debian > backporting any security updates themselves. > > I take it that the three nameservers in the clients
2015 Mar 10
0
"failed to lookup DC info for domain over rpc" when joining samba4 domain
On 10/03/15 14:11, Richard Connon wrote: > Hi Rowland, > > Please see comments inline. > > On 10/03/15 08:51, Rowland Penny wrote: >> Your DC's must point to themselves for DNS and your domain clients must >> point to the DC's, anything outside the domain the DC's will be obtain >> from the forwarders set on them. > > This is contrary to what the