Hi Everyone, Has anyone seen an issue where WinBind does not work after a reboot (or a restart of the WinBind service) until you issue a wbinfo -u command? This is what is happening on my system. The PAM modules are all in place and configured correctly as they work once the wbinfo command is issued. I get a very fast "user unknown to underlying authentication module" that flashes up at the login prompt unless the wbinfo command is run first. The odd thing is that logging in with the wrong password gives an invalid login message, so I know that WinBind is communicating with AD to some degree. I can provide more details if necessary; just figured maybe someone else had this exact problem as I'm running a very stock configuration. Thanks, Coz