Displaying 20 results from an estimated 800 matches similar to: "Domain member server: user access"
2017 Sep 25
1
Domain member server: user access
Am 2017-09-25 um 16:29 schrieb Rowland Penny via samba:
>> DC # samba-tool user create kamleitnerl Le26xxx
>> --nis-domain=arbeitsgruppe --unix-home=/home/kamleitnerl
>> --uid-number=10070 --login-shell=/bin/false --gid-number=100
>>
> 
> Where did you get the GID '100' from ?
> Is this the gidNumber for Domain Users ?
I think so:
# wbinfo --gid-info=100
2017 Sep 25
0
Domain member server: user access
Hai Stefan, 
Can you try the following. 
Reboot the server, then reboot the pc, then login with the not working user. 
When/If that works, then login and login with the other users try then.
And, i bet you checked it, but must ask, time in sync? 
Greetz, 
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Stefan G. Weichinger
2017 Sep 25
2
Domain member server: user access
Arg.. 
wbinfo --gid-info=100 
DC:  Confirmed, DOMAIN\Domain Users
Member: Fail. 
failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
Could not get info for gid 100 
But both server show the same with  : 
wbinfo -n "NTDOM\domain users" 
So imho, report bug if Rowland can confirm this with a samba from source. 
Greetz, 
Louis
> -----Oorspronkelijk bericht-----
> Van: samba
2018 Jan 16
3
Failed to finalize nt token
I am googling around for an issue and can't figure it out so far.
Status:
2 Debian 9.3 ADCs with samba-4.6.12 each.
1 Gentoo Samba Domain Member server "main",
Samba version 4.5.15 (we downgraded because of another issue a month ago
or so).
*one* AD user is able to log into his Windows10 PC, but doesn't get a
network share connected.
If I test that from the DM server or the
2017 Sep 25
0
Domain member server: user access
100 is debian default for users
And as far i remember stefhan uses debian. 
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Rowland Penny via samba
> Verzonden: maandag 25 september 2017 16:29
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Domain member server: user access
> 
> On Mon, 25 Sep 2017 16:01:59
2017 Sep 25
2
Domain member server: user access
Am 2017-09-25 um 17:18 schrieb Stefan G. Weichinger via samba:
> as mentioned in the other reply
> 
> DC: 100
> DM: 10513
> 
> - and using "id" as Louis did:
> 
> DC # id kamleitnerl
> uid=10072(ARBEITSGRUPPE\kamleitnerl) gid=100(users)
> Gruppen=100(users),3000001(BUILTIN\users)
> 
> DM # id kamleitnerl
> uid=10072(kamleitnerl) gid=10513(domain
2018 Jan 16
0
Failed to finalize nt token
Hi Stefan,
> I am googling around for an issue and can't figure it out so far.
>
> Status:
>
> 2 Debian 9.3 ADCs with samba-4.6.12 each.
>
> 1 Gentoo Samba Domain Member server "main",
> Samba version 4.5.15 (we downgraded because of another issue a month ago
> or so).
>
> *one* AD user is able to log into his Windows10 PC, but doesn't get a
>
2017 Sep 25
2
Domain member server: user access
On Mon, 25 Sep 2017 17:01:09 +0200
"Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:
> Am 2017-09-25 um 16:49 schrieb Rowland Penny via samba:
> > On Mon, 25 Sep 2017 16:35:52 +0200
> > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote:
> > 
> >> 100 is debian default for users
> >> And as far i
2019 Feb 22
4
Debian 9.8 and vanbelle-repos
Hai, 
That bond0 interface, you might want to change that the interface name to bond1
Depending on the bonding settings, you might have hit a reserved name. 
I lots my docu on that but i know i configured a bond1 because bond0 didn work right.
And then check these. 
wbinfo -pPt  ( or wbinfo -p && wbinfo -P && wbinfo -t ) 
wbinfo --sids-to-unix-ids S-1-22-2-10513
wbinfo -D
2019 Feb 21
2
Debian 9.8 and vanbelle-repos
# Global parameters
[global]
	interfaces = bond0
	log file = /var/log/samba/%m.log
	log level = 5 auth:5 winbind:8
	printcap name = /dev/null
	realm = SOMEDOM.AT
	security = ADS
	username map = /etc/samba/user.map
	winbind refresh tickets = Yes
	winbind use default domain = Yes
	workgroup = ARBEITSGRUPPE
	idmap config arbeitsgruppe:unix_nss_info = yes
	idmap config arbeitsgruppe:range =
2019 Feb 22
3
Debian 9.8 and vanbelle-repos
Am 22.02.19 um 12:16 schrieb L.P.H. van Belle via samba:
> Hai, 
> 
> Well, i did some extra checking, gone throug more logs. 
> ... Nothing. No errors. Sorry, i cant find anything.. 
> 
> Almost all my server run unattended updates, execpt the DC's. 
> 
> I had a few that where waiting for a reboot tomorrow night, all now rebooted, 
> and no problems before and
2017 Jan 01
5
ADS domain member: winbind fails [SOLVED]
On Sun, 1 Jan 2017 13:45:11 +0100
"Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:
> Am 2017-01-01 um 13:29 schrieb Rowland Penny via samba:
> 
> > Try checking in AD, as you have classicupgraded, your users should
> > have uidNumber attributes. Find the lowest and the highest, do the
> > same for groups and if you change to the
2019 Feb 22
2
Debian 9.8 and vanbelle-repos
Am 22.02.19 um 15:16 schrieb Rowland Penny via samba:
> On Fri, 22 Feb 2019 15:03:37 +0100
> "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote:
> 
>> Hai, 
>>
>> That bond0 interface, you might want to change that the interface
>> name to bond1 Depending on the bonding settings, you might have hit a
>> reserved name. I lots my docu
2019 Feb 22
1
Debian 9.8 and vanbelle-repos
Hai Stefan, 
Hmm is time in sync.  Did that server have these 3 settings in smb.conf? 
Yes/no/which ones ? 
    kerberos method = secrets and keytab
    dedicated keytab file = /etc/krb5.keytab
    # renew the kerberos ticket
    winbind refresh tickets = yes
Especialy the refresh ticket.. 
I see this is a RID setup? Not AD. 
Because if thats so, i run only in AD backend on the members. 
Can
2016 Dec 30
2
ADS domain member: winbind fails
On Fri, 30 Dec 2016 18:53:22 +0100
Volker Lendecke via samba <samba at lists.samba.org> wrote:
> On Fri, Dec 30, 2016 at 05:55:58PM +0100, Stefan G. Weichinger via
> samba wrote:
> > Am 2016-12-30 um 17:42 schrieb Rowland Penny via samba:
> > 
> > >OK, try this, open a terminal, type 'winbindd -i'
> > >This should directly run winbind in the
2016 Dec 30
3
ADS domain member: winbind fails
I am trying to set up winbind on a ADS domain member server.
The join works OK, but winbind simply fails to start.
see config and logs below, I am scratching my head.
Why does it "contact" a domain called "MAIN" ? that is the hostname of 
that server, not the domain name!
would be nice to get a quick reply, I am at the customer and this should 
work asap ....
Thanks!
2016 Dec 30
3
ADS domain member: winbind fails
On Fri, 30 Dec 2016 14:26:01 +0100
"Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:
> Am 2016-12-30 um 14:07 schrieb Rowland Penny via samba:
> > Is this the smb.conf you got when you ran the classicupgrade ?
> > I don't think it is, can I suggest you remove any and all lines you
> > have added and restart samba
> 
> that was the
2019 Feb 19
5
Debian 9.8 and vanbelle-repos
Hi Stefan, 
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Stefan G. Weichinger via samba
> Verzonden: dinsdag 19 februari 2019 10:43
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Debian 9.8 and vanbelle-repos
> 
> Am 18.02.19 um 08:38 schrieb L.P.H. van Belle via samba:
> > Goood morning Stefan, ( and
2017 Sep 25
2
Domain member server: user access
On Mon, 25 Sep 2017 16:54:24 +0200
"Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:
> Am 2017-09-25 um 16:48 schrieb L.P.H. van Belle via samba:
> > Arg.. 
> > 
> > wbinfo --gid-info=100 
> > DC:  Confirmed, DOMAIN\Domain Users
> > 
> > Member: Fail. 
> > failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
> >
2017 Jan 01
1
ADS domain member: winbind fails [SOLVED]
Am 2017-01-01 um 16:04 schrieb Rowland Penny via samba:
> So it looks like you only have 77 users, but cannot have any local Unix
> users because your Unix users start at 1000. How do feel about changing
> the uidNumbers ? 
feels scary and I'd like to avoid that :-)
> if so, the easiest way will be to open the AD database
> with ldbedit:
> 
> ldbedit -e nano -H