winbind "warm up" period?

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ronan Waide wrote:
| Just restarted winbind now, and wbinfo -t didn't work the first time:
|
| [root at workst1 nsswitch]# service winbind restart
| Shutting down Winbind services:                            [  OK  ]
| Starting Winbind services:                                 [  OK  ]
| [root at workst1 nsswitch]# wbinfo -t
| checking the trust secret via RPC calls failed
| error code was  (0x0)
| Could not check secret
| [root at workst1 nsswitch]# wbinfo -t
| checking the trust secret via RPC calls succeeded
|
| Is there some notional "warm up" period for winbind before you can run
| wbinfo -t?
|
| Note also the entirely useless error code :)

Look for name resolution timeout issues.  When
winbindd starts up, it adds the list of trusted domains.
You are probably seeing timeouts with remotes DC's.





cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/adarIR7qMdg1EfYRAn+VAKCIQO7jyUQBND+woACpP1VYmyRDWgCcCOvf
78vmx94RRTvZt3c9OSFloUc=
=GeIy
-----END PGP SIGNATURE-----