search for: tapisrv

Hi! I'm not sure I understand how SPNs are registered in the AD domain. I know when a regular samba server is joined to an AD domain, a few SPNs are registered - namely, CIFS/$netbios_name and each for CIFS/$netbios_aliases (where netbios name and netbios aliases are the parameters in smb.conf - yes I know these are obsolete, but in this case they're actually used for non-obsolete task).

...dhcp,dnscache,replicat or,eventlog,eventsystem,policyagent,oakley,dmserver,dns,mcsvc,fax,msiserver,i as,messenger,netlogon,netman,netdde,netddedsm,nmagent,plugplay,protectedstora ge,rasman,rpclocator,rpc,rpcss,remoteaccess,rsvp,samss,scardsvr,scesrv,seclog on,scm,dcom,cifs,spooler,snmp,schedule,tapisrv,trksvr,trkwks,ups,time,wins,ww w,http,w3svc,iisadmin,msdtc Which if you look closely, you will find that 'host' or 'HOST' is mapped to 'cifs', so you do not require explicit 'CIFS' SPNs. This isn't a Samba thing, it is a Windows AD thing. You do however need...

...tifyWinEvent (32769,0x00010029,-4,3)-stub! fixme:hook:NotifyWinEvent (32769,0x00010029,-4,2)-stub! fixme:hook:NotifyWinEvent (32769,0x00010029,-4,1)-stub! FIXME:pthread_cond_init mcop warning: user defined signal handler found for SIG_PIPE, overriding fixme:process:CreateProcessA (C:\windows\system\tapisrv.exe,...): NORMAL_PRIORITY_CLASS ignored FIXME:pthread_cond_init fixme:ole:RpcServerUseProtseqEpExA (ncacn_np,20,\pipe\tapsrv,0x405d6e00,{12,0,0}): stub fixme:ole:RpcServerUseProtseqEpExA (ncalrpc,20,tapsrvlpc,0x405d6e00,{12,0,0}): stub fixme:ole:RpcServerRegisterIf2 (0x4018d4,(nil),(nil),0,1234,429...

...dhcp,dnscache,replicat or,eventlog,eventsystem,policyagent,oakley,dmserver,dns,mcsvc,fax,msiserver,i as,messenger,netlogon,netman,netdde,netddedsm,nmagent,plugplay,protectedstora ge,rasman,rpclocator,rpc,rpcss,remoteaccess,rsvp,samss,scardsvr,scesrv,seclog on,scm,dcom,cifs,spooler,snmp,schedule,tapisrv,trksvr,trkwks,ups,time,wins,ww w,http,w3svc,iisadmin,msdtc msDS-Other-Settings: DisableVLVSupport=0 msDS-Other-Settings: DynamicObjectMinTTL=900 msDS-Other-Settings: DynamicObjectDefaultTTL=86400 distinguishedName: CN=Directory Service,CN=Windows NT,CN=Services,CN=Configura tion,DC=<domain>...

Hai,   I've checked out the log you send and i re-read the complete thread.   Based on thats done and what i did see in you logs now, looks like a  * (wildcard)  entry is giving the problem. But i am not sure of that, the wildcard bugs should be fixed, when i look in bugzilla.  (#10435 #12952 )   I've forwarded the mail to Rowland also before we go throw things at you again. ;-)