search for: 30124

...nutes later. I did notice this in the /var/log/asterisk/full log: [Oct 13 03:11:30] NOTICE[4243] chan_dahdi.c: Got event 17 (Polarity Reversal)... [Oct 13 03:11:38] WARNING[4243] chan_dahdi.c: CallerID returned with error on channel 'DAHDI/1-1' Normally, it says: [Oct 12 13:23:59] DEBUG[30124] chan_dahdi.c: Ignore switch to REVERSED Polarity on channel 1, state 4 [Oct 12 13:23:59] DEBUG[30124] chan_dahdi.c: Ignoring Polarity switch to IDLE on channel 1, state 4 [Oct 12 13:23:59] DEBUG[30124] chan_dahdi.c: Polarity Reversal event occured - DEBUG 2: channel 1, state 4, pol= 0, aonp= 0, ho...

So I made the primary group for the testuser account be smbgrp, and it's gidNumber is 30124. Still nothing. "getent passwd testuser" returns nothing unless testuser is in the local passwd file, and then it returns the attributes that are in the passwd file, not the AD system. Some time ago I put together a configuration that uses Linux SSSD to communicate with AD. That al...

On 09/10/15 22:22, Tovey, Mark wrote: > So I made the primary group for the testuser account be smbgrp, and it's gidNumber is 30124. Still nothing. "getent passwd testuser" returns nothing unless testuser is in the local passwd file, and then it returns the attributes that are in the passwd file, not the AD system. It always will if you have a local user with the same name as an AD user, remove the local user. On...

The only way it seems to work is if I do have both the local and AD user with the same name. But my goal here is to not require that, to have the AD account only. I have applied Unix attributes to the users. testuser uidNumber = 30089 and gidNumber = 100. However, when I try to query with wbinfo, I was unable to look that up: wbinfo -i "DEVELOPMENT\testuser" failed to call