similar to: not able to connect to windows machine

On 15/10/2019 13:56, ASW Global via samba wrote: > I've read the documentation that domain trusts should be fully supported with both Kerberos and NTLM authentication. I've created a new 2016 domain on a Windows box and created a Samba domain on a Linux box with a BIND9_DLZ backend. Both servers can resolve both DNS domains forwards and backwards and I am able to connect a Windows 10

Hi Gurus, I've been trying to compile SaMBa 3.6.0 for its SMB2 support on/off half time for about two weeks. I've built ealier versions of 3.x and most recently 3.4.2 following the same procedure but it no longer works for 3.6.0. I'm about ready to give up and hope that someone here might be able to give me a clue. I would grab a pre-built package but neither sunfreeware nor

On 17/04/15 12:29, ivenhov wrote: > Hi all > > I'm desperate now. > > On one of the sites I cannot connect Ubuntu to Windows AD 2003. > Error below. > On exactly the same setup but on a different network and also on VirtualBox > VMs everything works as expected. > Looks like something on the network then or mission parameter. > Error is about KDC but I can

I'm sorry for the very long debug pasted below but I'm afraid lower debug levels would not give enough useful information about the problem. I've been investigating it for over two weeks with no result. Maybe developers can tell me where to search for the cause - browsing source code is very hard... I have a Samba PDC with LDAP backend. Configuration works fine on 3.0.x version but

Marco Gaiarin via samba ha scritto il 25/08/20 alle 18:53: > [...] >> The only other thing I can think of at the moment is to remove >> 'winbind use default domain = yes' > > It was a try, i think in NT mode don't bother at all. on my samba server with 'winbind use default domain" set to yes dominioNT\ is removed from users and groups names... >

Hi all I'm desperate now. On one of the sites I cannot connect Ubuntu to Windows AD 2003. Error below. On exactly the same setup but on a different network and also on VirtualBox VMs everything works as expected. Looks like something on the network then or mission parameter. Error is about KDC but I can successfully do kinit and get ticket. I can also successfully run: sudo net ads info

On 10/03/15 20:14, Roman Dilken wrote: > On 10.03.2015 20:20, Rowland Penny wrote: > >> OK, the first will not work (well not yet), the second should, I >> take it you ran 'kinit Administrator at AD.DILKEN.EU' as root before >> the join ? >> >> You could try 'net ads join -U Administrator' and enter the >> password when prompted, I

On 10/03/15 20:29, Roman Dilken wrote: > Oh, I have a pair of samba-4.1.17-DC's, raspberry-pi and dc2 to which make the domain ad.dilken.eu on site Neuoetting. > > resolv.conf points to the two dc's: > > search ad.dilken.eu > nameserver 192.168.2.33 > nameserver 192.168.2.2 > > In the output I find some relations to dc2 resp. 192.168.2.2, but perhaps it

I am having problems implementing Samba using security=domain against a Windows 2008R2 server. I have been able to successfully join the domain via a net rpc join. Anytime I try to access a share through smbclient I get a NT_STATUS_TRUSTED_RELATIONSHIP_FAILURE but nothing in the logs (on either side) seems to be giving me any leads on where to look. The system is locked down to allow NTLv2

Oh, I have a pair of samba-4.1.17-DC's, raspberry-pi and dc2 to which make the domain ad.dilken.eu on site Neuoetting. resolv.conf points to the two dc's: search ad.dilken.eu nameserver 192.168.2.33 nameserver 192.168.2.2 In the output I find some relations to dc2 resp. 192.168.2.2, but perhaps it doesn't work as expected.. Greetings Am 10.03.2015 um 21:23 schrieb Rowland Penny:

On 10.03.2015 20:20, Rowland Penny wrote: > > OK, the first will not work (well not yet), the second should, I > take it you ran 'kinit Administrator at AD.DILKEN.EU' as root before > the join ? > > You could try 'net ads join -U Administrator' and enter the > password when prompted, I personally have never seen the point in > using kerberos during the

I've read the documentation that domain trusts should be fully supported with both Kerberos and NTLM authentication. I've created a new 2016 domain on a Windows box and created a Samba domain on a Linux box with a BIND9_DLZ backend. Both servers can resolve both DNS domains forwards and backwards and I am able to connect a Windows 10 client to the Samba domain without any issues. The

Hello! I see where this came up on the list a few months and never really ws resolved. Someone resolved it by linking libnss_winbind ... But that's not my problem... I'm getting " Failed to join domain: failed to set machine spn: Operations error" when I do a net ads join. I've used this user account (me) to join many Samba 3.5.6 servers to the domain. Config file and

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

On 10.03.2015 19:25, Rowland Penny wrote: > > Hi, what are you trying to join to? > > Remove this line 'idmap_ldp:use rfc2307 = yes' > > one) it should be 'idmap_ldb:use rfc2307 = yes' two) it is only > used on a DC. > > How are you trying to do the join ? > > Rowland > > Hi, I commented it out but it didn't change the behaviour.

Hi, After running configure, my /source3/include/autoconf/config.h is not showing these flags: #define HAVE_KRB5 1 #define HAVE_LDAP 1 How to fix config.log so that it will work: Please reply as sooon as possible: Nirmit Kansal .........................................

Hi, Actually I am working on a project in which we are migrating from 3.x to 4, so Please tell me the difference in versions and also give me information that how we can use active directory of 4.0 effectively as we are having CIFS and Kerberos feature in 3.x, And how this active directory can be helpful in our implementation. And I am also having a question as we are using 3.x so only because of

This is a design and an initial patch for kernel side for AER support in VFIO. 0. What happens now (PCIE AER only) Fatal errors cause a link reset. Non fatal errors don't. All errors stop the VM eventually, but not immediately because it's detected and reported asynchronously. Interrupts are forwarded as usual. Correctable errors are not reported to guest at all.

This is a design and an initial patch for kernel side for AER support in VFIO. 0. What happens now (PCIE AER only) Fatal errors cause a link reset. Non fatal errors don't. All errors stop the VM eventually, but not immediately because it's detected and reported asynchronously. Interrupts are forwarded as usual. Correctable errors are not reported to guest at all.

This is a design and an initial patch for kernel side for AER support in VFIO. 0. What happens now (PCIE AER only) Fatal errors cause a link reset. Non fatal errors don't. All errors stop the VM eventually, but not immediately because it's detected and reported asynchronously. Interrupts are forwarded as usual. Correctable errors are not reported to guest at all.