Hello,

Yesterday I upgraded a test server to Hardy x64 and was able to successfully get samba and likewise-open onto the our AD domain. Everything seems to have gone well except for of course vmware server 1.0.5. I had wanted to authenticate vmware server console with AD so it could be easily remotely administered, but unfortunately this did not work out. I looked into the problem and found the following in the auth.log file:

Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM unable to dlopen(/lib/security/pam_lwidentity.so)
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM [error: /lib/security/pam_lwidentity.so: wrong ELF class: ELFCLASS64]
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM adding faulty module: /lib/security/pam_lwidentity.so
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM (other) illegal module type: @include
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM pam_parse: expecting return value; [...common-auth]
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM (other) no module name supplied
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM unable to dlopen(<*unknown module path*>)
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM [error: <*unknown module path*>: cannot open shared object file: No such file or directory]
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM adding faulty module: <*unknown module path*>
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM (other) illegal module type: @include
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM pam_parse: expecting return value; [...common-account]
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM (other) no module name supplied
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM (other) illegal module type: @include
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM pam_parse: expecting return value; [...common-password]
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM (other) no module name supplied
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM (other) illegal module type: @include
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM pam_parse: expecting return value; [...common-session]
Apr 24 15:48:58 psvhost002 vmware-authd[27493]: PAM (other) no module name supplied

So from this I guess we can deduce two things: vmware isn't going to load the pam_lwidentity module from likewise-open since it is compiled for amd64 and apparently vmware doesn't like include directives in pam.d files. Can anyone suggest a good workaround for the pam_lwidentity issue?

PS. Sorry for double posting, I posted this question in the x64 forum before I noticed there was a virtualization forum, and this one seemed to be more appropriate for the question.