ESX 4.1 server can't join Novell DSFW domain server for authentication

[bridouxl]

Hello,

i try to activate AD authentication on an ESX server 4.1 via DSFW but still don't work
the ESX server can join a real AD server on 2008R2.

see log at ESX side with DSFW test:
Mar 29 09:53:47 esx-test /usr/lib/vmware/bin/vmware-hostd[4597]: DJRunJoinProcess: 0x80047: 0x995 - Unknown error
Mar 29 09:53:47 esx-test /usr/lib/vmware/bin/vmware-hostd[4597]: Stack Trace:
Mar 29 09:53:47 esx-test /usr/lib/vmware/bin/vmware-hostd[4597]:         /build/mts/release/bora-301967/likewise/esxi-esxi/x/domainjoin/libdomainjoin/src/djauthinfo.c:872
Mar 29 09:53:47 esx-test /usr/lib/vmware/bin/vmware-hostd[4597]:         /build/mts/release/bora-301967/likewise/esxi-esxi/x/domainjoin/libdomainjoin/src/djauthinfo.c:1218

no more log at DFSW side.

thanks

[ccliu77]

Make sure your environment is most latest OES 2 Sp3 + VMware View 4.6. It can work smoothly without any problem.

Another step to get rid of quick prep issue:

"In iManager if we get on to modify object -> Modify 'Login Policy' object which will be under security container -> set "Delay after failed login attempts" to 0

After setting this we will have "SasLoginFailureDelay" attribute on "Login Policy" object is set to 0.

If DSfW server does not have the  Root partition, we have to trigger BackLinker background process on the DSfW servers, so that the login polciy which is cached on EXRef gets update.
After the backlinker process we will have to restart ndsd on DSfW servers. "

For View versions older than 4.6, several fixes are needed. If possible please contact with Novell support.

I have "DSFW + VMware View 4.6" run for 100 nodes of virtual machines for quite a long time. So far so good. If u wanna talk offline, please send me email: xidu2011@gmail.com.

[All4world]

I just fixed the same issue following the upper steps. It really works. Thanks a lot.