locked
DHCP Callout API Shared Library problems RRS feed

  • Question

  • Hi,

     

    We have created a DHCP Callout API shared library, e.g. "hello world', after reviewing MSDN docs and A.J. Anto's blog with the details of the registry keys and so forth, implemented and exported the DhcpAddressDelHook,DhcpAddressOfferHook,DhcpControlHook, DhcpServerCalloutEntry,DhcpDeleteClientHook,DhcpHandleOptionsHook,DhcpNewPktHook,DhcpPktDropHook,DhcpPktSendHook methods. In short A.J. Anto's example.

     

    We've set the registry keys according to A.J. Anto's Blog as:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DHCPServer\Parameters
    1)
    Name :  CalloutDlls
    Value : list of path/filenames for the dlls to be loaded. In our case it is c:\callout\callout.dll
    Type : REG_MULTI_SZ
    2)
    Name : CalloutEnabled
    Value :
     1 = DHCP Server attempts to load callout.dlls
    Type : DWORD

     

    All seems well, but after successfully starting the DHCP server, the Event Viewer does not show Event 1033 (showing the DLL was loaded), nor does it show 1031, 1032, 1034, which show problems with the DLL loading.

     

    Could someone with a running Callout Library share the details of their DLL solution/project creation and MS technologies, and debugging approaches for loading this library?

     

    Thanks,

     

    Andrew


    Thursday, August 30, 2007 5:02 PM

Answers

  • Enable dhcp server logging and restart dhcp server process. You may see some traces like..

     

    1. Could not load dll: <error>

    2. Could not get tbl for: <error>

    3. Initialized callout dll

     

    You should be able to see either one of above traces in your log file. Based on error code, you can take further action ;-)

     

    HTH

    Tuesday, September 4, 2007 5:39 AM
  • Tuesday, September 4, 2007 5:42 AM

All replies

  • Enable dhcp server logging and restart dhcp server process. You may see some traces like..

     

    1. Could not load dll: <error>

    2. Could not get tbl for: <error>

    3. Initialized callout dll

     

    You should be able to see either one of above traces in your log file. Based on error code, you can take further action ;-)

     

    HTH

    Tuesday, September 4, 2007 5:39 AM
  • Tuesday, September 4, 2007 5:42 AM