pam_nt_dom and winbind problems

[Luke McKee]

Tim Potter wrote:

> Luke McKee writes:
>
> > 'wbinfo -t' returns:
> > "could not check secret"
> >
> > interperation /var/log/log.winbindd
> > when connecting to our DC it does not use a password to connect
> >
> > Should winbindd use it's machine account?
>
> Yes - you have to be joined to the domain for this to work,
> although the "could not check secret" sounds more like wbinfo not
> being able to talk to the winbind daemon.
>

lstat64("/tmp/.winbindd", {st_mode=S_IFDIR|0755, st_size=2048, ...}) = 0

lstat64("/tmp/.winbindd/pipe", {st_mode=S_IFSOCK|0777, st_size=0, ...})
= 0
socket(PF_UNIX, SOCK_STREAM, 0)         = 3
connect(3, {sin_family=AF_UNIX, path="
                                               /tmp/.winbindd/pipe"},
110) = 0
select(4, [3], NULL, NULL, {0, 0})      = 0 (Timeout)
write(3, "\26\0\0\0\232\30\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
520) = 520
read(3, "\224\2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
660) = 660

Tim there is the strack trace. Interestingly when I was trying before
the /tmp/.winbind/pipe file wasn't there.
Can any TNG developer tell me what the response wbinfo is getting back
from winbindd means?

(I'm not on Samba technical so this will be my last post there. Email me
direct if your on that list)
I'm posting to samba technical because thats what the pam_ntdom_auth
told me to read.

Luke