search for: my_realm

Hi, I'm having trouble realizing a krb5auth with pam_winbind with trusted domain users (external trust) on our clients. The client is joined to a local domain, which has a "external trust" to a global domain. The following things are working for all users (local and trusted domain): "wbinfo -i" "wbinfo --pam-logon" "wbinfo -a" "kinit"

...ed to understand it from reading the threat, but i cant figure that out. > On my debian ( samba 4.6.3 ), i use kerberos and nfsv4 almost everywhere. > And i do reuse my client tickets. > > klist > Ticket cache: FILE:/tmp/krb5cc_10002_Ki1hjqMDNM > Default principal: username at MY_REALM > > Valid starting Expires Service principal > 05/12/2017 09:53:19 05/12/2017 18:06:28 krbtgt/MY_REALM at MY_REALM > renew until 05/19/2017 08:06:28 > 05/12/2017 10:30:32 05/12/2017 18:06:28 nfs/member1.internal.domain.tld@ > renew until 05/...

...rove below ) ( from my debian jessie servers, the stretch servers dont have the idmap changes anymore. ) [General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs # set your own domain here, if id differs from FQDN minus hostname # Domain = localdomain Domain = internal.domain.tld Local-Realm = MY_REALM [Mapping] Nobody-User = nobody Nobody-Group = nogroup [Translation] Method = static,nsswitch GSS-Methods = static,nsswitch [Static] RTD-WEB1$@MY_REALM = root host/rtd-web1.internal.domain.tld at MY_REALM = root nfs/rtd-web1.internal.domain.tld at MY_REALM = root nfs/rtd-web1.internal.domain.tld...

...y, but there is no message delivered to the client. Am I approaching this the wrong way? sip.conf: [general] context=public ; Default context for incoming calls. Defaults to 'default' allowoverlap=no ; Disable overlap dialing support. (Default is yes) realm=my_realm ; Realm for digest authentication udpbindaddr=0.0.0.0 ; IP address to bind UDP listen socket to (0.0.0.0 binds to all) tcpenable=no ; Enable server for incoming TCP connections (default is no) tcpbindaddr=0.0.0.0 ; IP address for TCP serve...

...for vdmpp2$@AD.FVG.LNF.IT while getting keytab entry > for 'vdmpp2$@AD.FVG.LNF.IT' ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ? No key table table entry?? Hmm.. Check this with : klist -ke | grep "vdmpp2\\$" My servers output to compair with : 2 HOSTNAME1$@MY_REALM (des-cbc-crc) 2 HOSTNAME1$@MY_REALM (des-cbc-md5) 2 HOSTNAME1$@MY_REALM (arcfour-hmac) 2 HOSTNAME1$@MY_REALM (aes128-cts-hmac-sha1-96) 2 HOSTNAME1$@MY_REALM (aes256-cts-hmac-sha1-96) Just to be sure its there. > Oct 25 11:53:18 vdmpp2 rpc.gssd[13790]: No key table entry > fou...

On Mon, Sep 21, 2015 at 9:45 AM, D'Arcy J.M. Cain <darcy at vex.net> wrote: > On Mon, 21 Sep 2015 06:48:52 +0000 > Emil Ohlsson <emo at svep.se> wrote: >> [sip-im] >> exten _X!, 1, NoOp(Got message) >> exten _X!, n, Answer() >> exten _X!, n, Agi(agi://localhost/messagehandler.agi?...) >> exten _X!, n, SendText(Message received) > > I am not

Hello, I am searching for a solution that I thought should be kind of standard, but until now I was not successful finding anything. Here is the problem: At our site we offer windows and linux, most servers (eg file, samba, web) are linux based. User data is stored on NFS file servers. Windows systems are part of a Windows domain with an ADS domain controller. At the moment the linux samba

...that preauthentication failed. Joining a PC to a domain also works quite well. And the services are also working fine. I want to use the Machine-Account, to verfiy a GSSAPI-Login against an Openldap-Server with the PADL nss_ldap-Gateway and SASL login. My Samba-Konfiguration: [global] REALM = MY_REALM.NET security = ads use kerberos keytab = true I also inserted the following to my heimdal configuration file: default_keytab_name = FILE:/etc/krb5.keytab Can please someone help me, if I'm making a configuration mistake or something else? I tested everything on a SuSE-Linux Professional 9...

...security = ads hosts allow = 192.168. 172.21. 127. load printers = yes ; printcap name = /etc/printcap ; printcap name = lpstat ; printing = cups ; guest account = pcguest log file = /var/log/samba/s.%m max log size = 100 ; password server = <NT-Server-Name> ; realm = MY_REALM ; passdb backend = tdbsam ; include = /usr/local/samba/lib/smb.conf.%m socket options = TCP_NODELAY ; interfaces = 192.168.12.2/24 192.168.13.2/24 ; local master = no ; os level = 33 domain master = no preferred master = yes domain logons = no ; logon script = %m.bat ; logon...

...ou can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ; security = domain ; passdb backend = tdbsam ; realm = MY_REALM ; password server = <NT-Server-Name> # ----------------------- Domain Controller Options ------------------------ # # Security must be set to user for domain controllers # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is ava...

...tc/samba/smb.conf]: [global] workgroup = ppsi-austin netbios name = fdesk server string = Front Desk security = user cups options = raw ; guest account = pcguest log file = /var/log/samba/%m.log max log size = 50 ; password server = <NT-Server-Name> ; realm = MY_REALM ; passdb backend = tdbsam ; include = /usr/local/samba/lib/smb.conf.%m ; interfaces = lo eth0 local master = yes os level = 99 domain master = yes preferred master = yes domain logons = yes encrypt passwords = yes ; logon script = %m.bat ; logon script = %U.bat...

Good morning Marco and others. > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Gaiarin via samba > Verzonden: dinsdag 23 oktober 2018 18:58 > Aan: samba at lists.samba.org > Onderwerp: [Samba] Again NFSv4 and Kerberos at the 'samba way'... > > > Sorry, i come back to this topic in a different thread,

...ou can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ; security = domain ; passdb backend = tdbsam ; realm = MY_REALM ; password server = <NT-Server-Name> # ----------------------- Domain Controller Options ------------------------ # # Security must be set to user for domain controllers # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is ava...

...you can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * security = domain ; passdb backend = tdbsam ; realm = MY_REALM password server = dc1-x4200-f.beilux.eib.org dc2-x4200-f.beilux.eib.org * # ----------------------- Domain Controller Options ------------------------ # # Security must be set to user for domain controllers # # Backend to store user information in. New installations should # use either td...

...curity = server or if you can't > # use the DNS to locate Domain Controllers > # The argument list may include: > # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] > # or to auto-locate the domain controller/s > # password server = * > > > ; realm = MY_REALM > > ; password server = <NT-Server-Name> > > # ----------------------- Domain Controller Options > ------------------------ > # > # Security must be set to user for domain controllers > # > # Backend to store user information in. New installations should > #...

...nt list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * password server = G1 # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of ; realm = MY_REALM # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. passdb backend = tdbsam # Using the following line enables you to customise your configuration # on...

...he # argument list can include My_PDC_Name, [My_BDC_Name], and [My_Next_BDC_Name]: # # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # # Use "password server = *" to automatically locate Domain Controllers. ; security = domain ; passdb backend = tdbsam ; realm = MY_REALM ; password server = <NT-Server-Name> # ----------------------- Domain Controller Options ------------------------ # # security = must be set to user for domain controllers. # # passdb backend = the backend used to store user information in. New # installations should use either tdbsam or...

..._PDC_Name, [My_BDC_Name], and [My_Next_BDC_Name]: # # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # # Use "password server = *" to automatically locate Domain Controllers. ; security = domain ; passdb backend = tdbsam ; realm = MY_REALM ; password server = <NT-Server-Name> # ----------------------- Domain Controller Options ------------------------ # # security = must be set to user for domain controllers. # # passdb backend = the backend used to store user information in. New # installations should use eithe...

...ame, [My_BDC_Name], and [My_Next_BDC_Name]: > # > # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] > # > # Use "password server = *" to automatically locate Domain Controllers. > > ; security = domain > ; passdb backend = tdbsam > ; realm = MY_REALM > > ; password server = <NT-Server-Name> > > # ----------------------- Domain Controller Options ------------------------ > # > # security = must be set to user for domain controllers. > # > # passdb backend = the backend used to store user information in. New >...

...# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ; password server = <NT-Server-Name> # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of ; realm = MY_REALM # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # passdb backend = tdbsam # Using the following line enables you to customise your configuration # on...