Bug 3238 - Can wbinfo tell us when it can't contact winbindd?
Can wbinfo tell us when it can't contact winbindd?
Product: Samba 3.0
Classification: Unclassified
Component: winbind
x86 Linux
: P3 trivial
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2005-11-03 22:23 UTC by Kevin Shanahan (dead mail address)
Modified: 2005-11-17 06:49 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Shanahan (dead mail address) 2005-11-03 22:23:12 UTC
When using the default winbind separator '\', wbinfo --set-auth-user fails
. I have these two lines in smb.conf:

   #winbind separator = \
   winbind use default domain = no

So, with that line commented out, the default separator setting is selected.

  test:~# testparm -v -s | grep "winbind separator"
          winbind separator = \


  test:~# wbinfo --set-auth-user="DOMAIN\Administrator"
  could not obtain winbind separator!
  test:~# echo $?
  test:~# wbinfo -t
  checking the trust secret via RPC calls failed
  error code was  (0x0)
  Could not check secret

To get it to work, I can do either:

   #winbind separator = \
   winbind use default domain = yes

   test:~# wbinfo --set-auth-user="Administrator"


   winbind separator = /
   winbind use default domain = no

   test:~# wbinfo --set-auth-user="DOMAIN/Administrator"

There is a related problem in that I can't explicitely set the winbind separator
 to '\' in the config file (but I'll file that as a separate bug).
Comment 1 Kevin Shanahan (dead mail address) 2005-11-04 15:47:36 UTC
(*red face*) It looks like the reason this command was failing was because
winbindd wasn't running (I hadn't run "net ads join" yet).

Even though it's pretty obvious that it needs to be running when you read the
man page, perhaps the tool itself could output an error saying that it couldn't
contact the running winbindd?

I'll change the summary to just be a suggestion...
Comment 2 Gerald (Jerry) Carter 2005-11-17 06:49:29 UTC
you can run wbinfo -p to "ping" winbindd.