sub-auth dll (Msv1_0SubAuthenticationFilter) wrt 32/64 bit 2003 se
in [Win32 Kernel]
|
Prev: Reminder - Microsoft Responds to the Evolution of Community
Next: Strange USB-Audio streaming behaviour of DPC
From: Anil Goel on 22 May 2010 03:43 Hi, We have implemented a dll (ipolicy_subauth.dll). This DLL implements and exports the function – “Msv1_0SubAuthenticationFilter”. The registery setting has been done at – HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Auth0 and the value is set to location of this DLL. On Winodws 2003 server SP2 (32 bit edition), this is working fine perfectly. Whenever a user logs on the PDC, this function receives the user login information and I can process it. Whenever the system re-boots this DLL becomes in use and I cannot delete it. When I have installed the same DLL on Windows 2003 Server R2 SP2 (64 bit edition) or Windows 2008 server (64 bit edition). This is not working. The same registery settings have been done. Looks like this DLL is not getting loaded in the system. I can delete it. Whenever user log on the PDC no information is getting received in this sub-authentication package. Has anyone seen this kind of problem, the question I would like to have answers are – 1. Is there something specific to 64 bit that needs to be done. 2. How to make DLL loaded by the system – is there some more registry settings that need to be done. 3. Can a 32 bit application DLL that has been set as sub authentication package, can be used in a 64 bit environment. Other 32 bit applications that I I have are working fine on these 64 bit servers. Any help on this would be greatly appreciated as it has been a customer issue who has upgraded from 32 bit platform to 64 bit platform. Kind of critical. Regards, -- Anil Goel
From: m on 22 May 2010 16:25
I don't know anything about sub-authentication DLLs, but I suspect that your problem is related to either: 1) registry reflection 2) trying to load a 32 bit DLL into a 64 bit process (or vice versa) "Anil Goel" <AnilGoel(a)discussions.microsoft.com> wrote in message news:CC90E580-9F47-4B9D-ADEB-3D57182731C2(a)microsoft.com... > Hi, > > We have implemented a dll (ipolicy_subauth.dll). This DLL implements and > exports the function – “Msv1_0SubAuthenticationFilter”. > > The registery setting has been done at – > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Auth0 and > the value is set to location of this DLL. > > On Winodws 2003 server SP2 (32 bit edition), this is working fine > perfectly. > Whenever a user logs on the PDC, this function receives the user login > information and I can process it. Whenever the system re-boots this DLL > becomes in use and I cannot delete it. > > When I have installed the same DLL on Windows 2003 Server R2 SP2 (64 bit > edition) or Windows 2008 server (64 bit edition). This is not working. The > same registery settings have been done. Looks like this DLL is not getting > loaded in the system. I can delete it. Whenever user log on the PDC no > information is getting received in this sub-authentication package. > > Has anyone seen this kind of problem, the question I would like to have > answers are – > 1. Is there something specific to 64 bit that needs to be done. > 2. How to make DLL loaded by the system – is there some more registry > settings that need to be done. > 3. Can a 32 bit application DLL that has been set as sub authentication > package, can be used in a 64 bit environment. Other 32 bit applications > that > I I have are working fine on these 64 bit servers. > > Any help on this would be greatly appreciated as it has been a customer > issue who has upgraded from 32 bit platform to 64 bit platform. Kind of > critical. > > Regards, > > -- > Anil Goel |