DHCP Server Callout API works on 2K, not on 2003

I've implemented a DHCP Server Callout API handler as documented in
http://msdn.microsoft.com/library/en...server_api.asp. It
works perfectly on 2K Advanced Server, but on Windows Server 2003, the DLL
doesn't even get loaded.

On 2K AS, my callout DLL is loaded almost immediately upon startup of the
DHCP server, and an event with ID 1033 is placed in the System event log,
indicating the successful load of the callout DLL.

On 2003, the same DLL never gets loaded; running REGMON during DHCP server
startup shows no attempt to read the CalloutDlls or CalloutEnabled values of
the HKLM\System\CurrentControlSet\Services\DHCPServer\ Parameters registry
key. This suggests that the 2003 DHCP server is, for some unknown reason,
not even attempting to implement the callout mechanism.

So what has changed from Win 2K to Windows Server 2003 to break the callout
API?

Did you ever get a response regarding the DHCP Server Callout? I am starting
on a new project and was wondering if you might have some insight on what to
expect as I move further into this.


"Jeff Henkels" wrote:

> I've implemented a DHCP Server Callout API handler as documented in
> http://msdn.microsoft.com/library/en...server_api.asp. It
> works perfectly on 2K Advanced Server, but on Windows Server 2003, the DLL
> doesn't even get loaded.
>
> On 2K AS, my callout DLL is loaded almost immediately upon startup of the
> DHCP server, and an event with ID 1033 is placed in the System event log,
> indicating the successful load of the callout DLL.
>
> On 2003, the same DLL never gets loaded; running REGMON during DHCP server
> startup shows no attempt to read the CalloutDlls or CalloutEnabled values of
> the HKLM\System\CurrentControlSet\Services\DHCPServer\ Parameters registry
> key. This suggests that the 2003 DHCP server is, for some unknown reason,
> not even attempting to implement the callout mechanism.
>
> So what has changed from Win 2K to Windows Server 2003 to break the callout
> API?
>
>
>
>