similar to: Virtual Users and Local Users Authentication

Hi Gurus, I have a simple failover cluster on two SLES 12 SP3 nodes with Samba/winbind for authenticating AD-user access to the shares. The shares are reached through a virtual hostname/IP which differs from the SLES-server itself. The servers uses SSSD for normal SSH-authentication, also against the same Active Domain. Here is the problem - if I get Samba/winbind to work with the virtual

Hi there, i hope someone can help me with this question. we successfully got Samba 4.11 up and running with Winbind on our SLES 15.2. the Linux server is a member of the Windows domain. Due to a user with identical name in AD as well as locally on the Linux server, we have the following problem. How can we make sure, that the "local user" (with the same name in ad) is accessed only via

Hi, I have been trying to use Winbindd in SLES 11 SP3 (Samba version 3.6.3-17.25.1) to fetch AD (Windows 2008 R2) identities into the Linux box and currently running into some problem w.r.t domain local groups and thought I could get some help here.. I have a two domain setup, in which DOMAIN1 is the parent domain and DOMAIN2 is the child domain. I have 2 users DOMAIN1\user1, DOMAIN2\user2 and

Hi Stefan, Am 20.06.23 um 13:33 schrieb Sabolowitsch, Stefan via samba: > Hi there, > i hope someone can help me with this question. > > we successfully got Samba 4.11 up and running with Winbind on our SLES 15.2. First thing 4.11 is far far out of service you should not use it in a production environment. Use 4.17 or better 4.18 > the Linux server is a member of the Windows

Hi list, I have set up a samba installation (SLES 11, Samba 3.2.7) and joined a domain. I've created local users (/etc/passwd) and can authenticate with this users against the domain controller. Now I want to add a local user (with smbpasswd) and authenticate with this user which does not exist in the domain. When I'm trying to log in with the user the log says: domain_client_validate:

I'm using ocfs2 and all modules from Suse (SLES9), no self compilations. Here are the details: * 32-bit machine (writing to ocfs2 partition/LUN and where the corruption was reported): Kernel: 2.6.5-7.257-bigsmp #1 SMP i686 i386 GNU/Linux OCFS2 rpms: ocfs2console-1.2.1-4.2 ocfs2-tools-1.2.1-4.2 o2cb_ctl -V: o2cb_ctl version 1.2.1 /etc/init.d/o2cb status: Module "configfs":

OK, further to my previous message I've configured BIND, but when I try to run samba_dnsupdate I get the following: Nov 18 16:19:23 sles-shire named[6112]: samba b9_putrr: unhandled record type 0 Nov 18 16:19:24 sles-shire named[6112]: samba_dlz: starting transaction on zone _msdcs.main.adlab.netdirect.ca Nov 18 16:19:24 sles-shire named[6112]: samba_dlz: disallowing update of

When I attempt to migrate a VM from one host to another (sles-xen-2 -> sles-xen-1) I get the error message: > sles-xen-2:~ # xm migrate --live SLES-11-SP2-1 192.168.1.3 > Error: can''t connect: [Errno 111] Connection refused > ... What might be the problem? FWIW: I''ve already verified that iptables rules have been cleared and that xend does not have any ports open

I''ve installed facter-1.6.0 and puppet-2.7.3 on a number of SLES 10 hardware nodes (HP DL580) running the Virtuozzo hosting software. Well, facter correctly identifies such a machine as a hardware node ("virtual => openvzhn") but somehow concludes that the hardware node is in fact virtual. ("is_virtual => true") This breaks some rather important logic. If

The "sles" distribution string in libguestfs represents both SLES and SLED, so map the osinfo descriptions of "sled" distributions as "sles". --- src/osinfo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/osinfo.c b/src/osinfo.c index 907580e..7fdaf1c 100644 --- a/src/osinfo.c +++ b/src/osinfo.c @@ -625,7 +625,7 @@ parse_distro (guestfs_h

On Fri, Nov 23, 2018 at 11:53:05AM +0000, Richard W.M. Jones wrote: >On Fri, Nov 23, 2018 at 12:39:44PM +0100, Martin Kletzander wrote: >> There's a standardized libosinfo namespace for libvirt domain metadata. For now >> it supports the id of the OS only. However that is still a very helpful feature >> that is already supported in gnome-boxes and virt-manager (at

Hi Has anyone successfully integrated SLES 9.1 into Active Directory using Samba 3 , such that the AD users log onto the directory and gain access to resources on the SLES server as if it were just another Windows server. I am a total newbie but with the help of the fantastic Linux community managed to get myself to the point where the SLES box is in AD but if I want AD users to gain access to

We've joined an RODC to the domain (Windows 2008R2 running a W2003 FFL/DFL AD) but are getting these errors on first startup. It was joined with: samba-tool domain join main.adlab.netdirect.ca RODC --realm=main.adlab.netdirect.ca --username=administrator at main.adlab.netdirect.ca --dns-backend=BIND9_DLZ but we get these errors right after startup: Nov 28 12:35:27 sles-bree samba[3939]:

openSUSE Leap 15 has "opensuse-leap" as ID in os-release, so add it both in the detection code of the RPM handler, and in test-harder.sh. --- src/ph_rpm.ml | 2 +- tests/test-harder.sh | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/ph_rpm.ml b/src/ph_rpm.ml index b0a5eb2..3caa38e 100644 --- a/src/ph_rpm.ml +++ b/src/ph_rpm.ml @@ -40,7 +40,7 @@ let

Hello, Whenever copying files using ssh (scp) from SLES 8 (openssh 3.4p1-263) to another box (e.g SLES 8, Solaris 8, Windows XP), the memory of the initial SLES 8 box gets depleted. To make sure this is true I use the free command whilst copying and see that the used memory reaches 90 / 100%. After the copying is finished this memory is never released. No memory tool can tell me what happened

I was hoping this would be simpler. I'd like to prepopulate an RODC with all users accounts that are permitted. But I can only pre-populate one at a time: samba-tool rodc preload (<SID>|<DN>|<accountname>) sles-shire:~ # samba-tool group listmembers 'Allowed RODC Password Replication Group - Shire' Allowed RODC Password Replication Group - Global WIN7-SHIRE$ bilbo

Everyone, I have configured a new SLES 10 server exactly the same as I had previously configured a SLES 9 server. The only difference is the version of samba. On the SLES 10 server, I am running the 3.0.23c level, the SLES 9 server is behind a little. My problem is with connecting to other AD domains. Only my default domain has a valid sequence number. All the other domains are

On Wednesday 09 September 2015 15:54:10 Olaf Hering wrote: > Just poked around in my =libguestfs folder... > > On Wed, Sep 09, Pino Toscano wrote: > > > + if (STRPREFIX (line, "ID=")) { > > This is not handled: > > NAME="SLES" > VERSION="12" > VERSION_ID="12" > PRETTY_NAME="SUSE Linux Enterprise Server

Hi all, Just curious, Quite a while a go, i was checking for supported SW-platform. AFAIR, it was RHES and SLES Now it's only RHES-4 and FC-3 or FC-4. Not a single syllable about CentOS or SLES-9 or SLES-10 It probably just runs fine, but any chance of getting support for their *-enterprise version? (just in case of, if one needs it) Hans -- pgp-id: 926EBB12 pgp-fingerprint: BE97 1CBF

It seems that all the newer versions of openSUSE have an 'opensuse-' prefix in their distro ID; hence, check for that prefix at once, keeping compatibility for the old "opensuse" ID. Followup of commit 0668b2d64abef0724219480a3d7fc16b8dd1e68f. --- src/ph_rpm.ml | 3 ++- tests/test-harder.sh | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git