<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx</link><description>Ah now for the best part. I had always wanted to test this callout API thing. This is perhaps the most powerful way to leverage your Windows DHCP server. With the DHCP server callout, in a way, the whole DHCP server source code is before you for you to</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#380608</link><pubDate>Fri, 25 Feb 2005 23:37:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:380608</guid><dc:creator>Kevin Marquette</dc:creator><description>I have looked for this before, I just didn't know what to search for.&lt;br&gt;&lt;br&gt;I have looked for scripting dhcp, loading dhcp as a ActiveX control, and commandline access.  And I never found what I was looking for.&lt;br&gt;&lt;br&gt;I was wanting to track DHCP requests and limit who is to receive them.  This is exactly what I needed.  &lt;br&gt;&lt;br&gt;other questions. How would this work with VB.NET?  I probably shouldn't write DHCP dll's in managed code, but VB is our standard language.  Would it be easyer to write a wrapper in C++ to let me do the work in VB.NET?  Any thoughts?&lt;br&gt;&lt;br&gt;What about running 2 DHCP Servers on the same box and loading custom DLL's.  I want one group of computers to get one ip range and another to get a different range.  Would that be possible, or am I dreaming.   &lt;br&gt;&lt;br&gt;</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#381140</link><pubDate>Sun, 27 Feb 2005 10:03:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:381140</guid><dc:creator>Kevin Marquette</dc:creator><description>I have looked for this before, I just didn't know what to search for.&lt;br&gt;&lt;br&gt;I have looked for scripting dhcp, loading dhcp as a ActiveX control, and commandline access. And I never found what I was looking for.&lt;br&gt;&lt;br&gt;I was wanting to track DHCP requests and limit who is to receive them. This is exactly what I needed. &lt;br&gt;&lt;br&gt;other questions. How would this work with VB.NET? I probably shouldn't write DHCP dll's in managed code, but VB is our standard language. Would it be easyer to write a wrapper in C++ to let me do the work in VB.NET? Any thoughts?&lt;br&gt;&lt;br&gt;What about running 2 DHCP Servers on the same box and loading custom DLL's. I want one group of computers to get one ip range and another to get a different range. Would that be possible, or am I dreaming.</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#381158</link><pubDate>Sun, 27 Feb 2005 13:08:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:381158</guid><dc:creator>A.J.Anto</dc:creator><description>I guess you can write C++ wrapper arround the managed code. This should be possible.&lt;br&gt;Other than that, I don't know why you should be running two DHCP servers on the same box. If all you wanted to acheive was to make sure that computers belonging to two distinct groups are allocated an IP address from two distinct ranges (scopes in DHCP terminology), I am afraid that this is not possible today. The reason why this is not possible today is that the DHCP server chooses a scope from which it doles out an IP address based only on the subnet where the client is existing. This is done so that the machine gets an address that is appropriate to the link.</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#381293</link><pubDate>Mon, 28 Feb 2005 00:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:381293</guid><dc:creator>Kevin Marquette</dc:creator><description>I have an idea that should work in theory.&lt;br&gt;&lt;br&gt;I want to give a scope to all authorized computers and a private scope to all others.  &lt;br&gt;The computers will exist on the same physical network, but on different subnets.&lt;br&gt;&lt;br&gt;I do have a reason for my madness</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#382366</link><pubDate>Tue, 01 Mar 2005 17:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:382366</guid><dc:creator>A.J.Anto</dc:creator><description>I guess you can do that. But for this you must sort of hack the packet pointer variable 'Packet' got in the the function DhcpNewPktHook. You can overwrite the giaddr field in the packet buffer to the subnet address of the scope from which you want to assign the IP address. Say for unauthenticated computers you might want to allocate addresses from scope 192.168.200.0 then you might want to overwrite the giaddr field to 192.168.200.1 to fool the server that this packet had come from the segment 192.168.200.0 and hence we must allocate the address from that scope. This is in accordance with the RFC 2131. This is fine but this involves parsing the packet which is a BYTE *. I really don't know if this will work. Have not tried it myself. The possible issues that might arise is that: if the packet origanally comes from the local network on which the DHCP server is attached then the DHCP server might send the resonse in a different way than when the packet orignates from the remote network as we are feingning it.</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#392206</link><pubDate>Thu, 10 Mar 2005 19:45:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:392206</guid><dc:creator>A.J.Anto (On behalf of Rob White)</dc:creator><description>Hi, &lt;br&gt;&lt;br&gt;I've just read your article &lt;a target="_new" href="http://weblogs.asp.net/anto_rocks/archive/2005/02/25/380510.aspx"&gt;http://weblogs.asp.net/anto_rocks/archive/2005/02/25/380510.aspx&lt;/a&gt;, I built the dll from your source code and installed it on my server, sure enough up popped the event number 1033, it seemed that everything went well. Now I paused, and resumed my server, to check it was working correctly, but the text file callout.txt remained blank. I've also been playing with DhcpEnumSubnetClients, with equally low success rates. Both your dll and the code I wrote to make use of the DhcpEnumSubnetClients function look like they should work, but both are returning nothing. &lt;br&gt;&lt;br&gt;Is there something that I need to install on my server? (it's a windows 2003 server, if that makes any difference) Is there a redistributable or some such that I need to install? &lt;br&gt;&lt;br&gt;Any help would be gratefully received. &lt;br&gt;Regards, &lt;br&gt;Rob&lt;br&gt;</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#392216</link><pubDate>Thu, 10 Mar 2005 19:52:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:392216</guid><dc:creator>A.J.Anto</dc:creator><description>You do not need anything further than a Win2K3 server. I assume the file was created by the DHCP server but you don't see anything there. I don't get understand why this should be happening. Maybe we are missing something. Did u change the registry? Maybe there is someone else in the blogosphere who can help Rob??</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#398782</link><pubDate>Fri, 18 Mar 2005 23:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:398782</guid><dc:creator>Tom Handerkin</dc:creator><description>This is what I obtained. Can you explain this?&lt;br&gt;&lt;br&gt;Value obtained from file system volume descriptor pointer: 0x347cb00&lt;br&gt;The old setting was THU JAN 01 00:00:00 1970&lt;br&gt;Accepted system dates are greater than THU DEC 27 00:00:00 1990&lt;br&gt;ramdrv:/  - Volume is OK &lt;br&gt;tffsdrv: DOS mounting Complete &lt;br&gt;tffsdrv:/  - Volume is OK                                                       &lt;br&gt;nvdrv: DOS mounting Complete &lt;br&gt;nvdrv:/  - Volume is OK                                                     &lt;br&gt;0x34b97c8 (tStartup): WARNING: RAM db is deleted&lt;br&gt;</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#421336</link><pubDate>Tue, 24 May 2005 10:07:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:421336</guid><dc:creator>Qflash</dc:creator><description>RePost:&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://www.yeyan.cn/Programming/DHCPServerAPIfunctions.aspx"&gt;http://www.yeyan.cn/Programming/DHCPServerAPIfunctions.aspx&lt;/a&gt;</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#421354</link><pubDate>Tue, 24 May 2005 11:34:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:421354</guid><dc:creator>anto_rocks</dc:creator><description>check out this: &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/anto_rocks/archive/2005/05/24/421353.aspx"&gt;http://blogs.msdn.com/anto_rocks/archive/2005/05/24/421353.aspx&lt;/a&gt;</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#423314</link><pubDate>Tue, 31 May 2005 03:59:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:423314</guid><dc:creator>JPawlak</dc:creator><description>Does anyone know how to dissect the lpbyte packet parameter and get the hostname requesting the IP address?&lt;br&gt;&lt;br&gt;Thanks.</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#425726</link><pubDate>Mon, 06 Jun 2005 19:42:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:425726</guid><dc:creator>Neal Ridgeway</dc:creator><description>Wow, I have finally found someone doing something with the callout.&lt;br&gt;I have had the callout running for sometime now on a Windows 2K3 server in the lab pumping out all kinds of good stuff.&lt;br&gt;My plan is to set up a parameter and reject those machines that dont pass the various test such as minimum patch level and virus pattern files.&lt;br&gt;The DLL was easy, the hard part has been the &amp;quot;back end&amp;quot; stuff.</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#506603</link><pubDate>Thu, 22 Dec 2005 06:30:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:506603</guid><dc:creator>Tian Qiang Chen</dc:creator><description>Hello,&lt;br&gt;&lt;br&gt;I'm lucky to find the article and the web site. It is very useful for me to develop an external dll of a DHCP server.&lt;br&gt;&lt;br&gt;I am planing to reject to offer address to some machine. How can I do it? &lt;br&gt;&lt;br&gt;Thanks</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#509536</link><pubDate>Thu, 05 Jan 2006 09:20:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:509536</guid><dc:creator>Timrza.Chen</dc:creator><description>well, DhcpNewPktHook may fit your needs,&lt;br&gt;&lt;br&gt;set the (LPBOOL ProcessIt) flag with FALSE, DHCP will drop the packet, you can add your own judgement to process it. be care LPBOOL. it is a point;</description></item><item><title>Thank you</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#537431</link><pubDate>Thu, 23 Feb 2006 03:37:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:537431</guid><dc:creator>Useful blog</dc:creator><description>Very nice blog!</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#559990</link><pubDate>Fri, 24 Mar 2006 18:28:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:559990</guid><dc:creator>Juan Segura</dc:creator><description>I want to assign IPs from a different pools depending on the network card.&lt;br&gt;&lt;br&gt;I have a W2K3 server with 4 network cards and I want a range of IPs for every card. I conect a group of clients to every card and I can know what group of clients belong with the IP of the client in a proxy application.&lt;br&gt;&lt;br&gt;I can make the DLL in VS2005 C#?&lt;br&gt;&lt;br&gt;GREAT!!!</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#568713</link><pubDate>Wed, 05 Apr 2006 10:11:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:568713</guid><dc:creator>ratna</dc:creator><description>I ave included the callout.dll in windows2003 server.everthing sems to be fine but the dll is not able to log the messages when a new client request for an ipaddress from DHCP server.&lt;br&gt;&lt;br&gt;please help</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#594367</link><pubDate>Wed, 10 May 2006 10:54:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:594367</guid><dc:creator>Mazdisna Meenavee Mehr</dc:creator><description>Hi&lt;br&gt;Dear&lt;br&gt;I want to use your method that is a very good &lt;br&gt;way to have an extention to DHCP&lt;br&gt;But when I make this DLL in VC++.Net 2003 and make regitery changes I have a very bad Error &lt;br&gt;1034 : The sepscified procedure could not bE found&lt;br&gt;My server Is Win 2003&lt;br&gt;and i dont know exactly where i should paste your code sample&lt;br&gt;I make an Class Lib in VC++.Net 2003 and paste the sample code in cpp file what is wrong&lt;br&gt;Please Help Me?&lt;br&gt;Please&lt;br&gt;Best regards&lt;br&gt;Meenavee</description></item><item><title>Modify responses</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#625761</link><pubDate>Sun, 11 Jun 2006 01:37:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:625761</guid><dc:creator>Scrappy</dc:creator><description>I have taken a looka t using the DHCP call out but I need some assistants in tryin to determine how to manipulate the response. I understan I need to modify the packet contents before being sent. Again I think I need to use the call out DhcpNewPktHook. I can not figure out how to refrenece the portion of the packet?&lt;br&gt;Any quick sample on how to make this call? or perhaps does someone know who might help. All I want is help on changing various response fields such as gateway &amp;amp; mask values. Please help I am my witts end.&lt;br&gt;&lt;br&gt;Cheers,&lt;br&gt;Scrappy</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#632503</link><pubDate>Thu, 15 Jun 2006 20:18:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:632503</guid><dc:creator>Matthew Bailey</dc:creator><description>I work at an ISP and I am trying to use these API functions to migrate our DSL Customers from Static IP's to DHCP. In order for me to sell this the transition must be seamless. Our Router will append Option 82 which contains the ATM Virtual Circuit that is assigned to the customer. I have a working DLL that will disect the packet and get the Virtual Circuit information out, and then it will Query our MySQL database to reference ther Virtual Circuit to there old Static IP. Now all I need to do is send the IP that I get from the Database, how can I do this, should I use DHCPPacketSendHook?</description></item><item><title>Packet hooks in C#.Net</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#669409</link><pubDate>Tue, 18 Jul 2006 10:53:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:669409</guid><dc:creator>Phil</dc:creator><description>Hi, this is certainly the most useful BLOG on the subject. Thanks Anton.&lt;br&gt;&lt;br&gt;Is it possible to hook into the server callout functions using c#.net or vb.net? Is so , how do I call it?&lt;br&gt;&lt;br&gt;phil</description></item><item><title>Introducing a callout DLL ;)</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#726943</link><pubDate>Sun, 27 Aug 2006 17:56:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:726943</guid><dc:creator>Oliver</dc:creator><description>Hi,&lt;br&gt;&lt;br&gt;the &amp;quot;restrict clients&amp;quot; feature was one thing that bugged me back in 2003, so I wrote a Delphi callout DLL for the MS DHCP server back then. Although it performed quite well, I decided to port it to C at some point and enhance it a little. The result is MACkerer2 and you can read about it here:&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://blog.assarbad.info/20060814/mackerer_en/"&gt;http://blog.assarbad.info/20060814/mackerer_en/&lt;/a&gt;&lt;br&gt;&lt;br&gt;The whole idea is to limit the clients by their MAC addresses, which are stored in an Apache-like configuration file. There are advanced logging features that will blow your mind if you would like to give a certain context to the IP/MAC (i.e. lease) that was given out on 3rd of May 2004, for example. If you have given the respective information in the configuration file, it will be contained in the log file. Logging features can be turned on and off ...&lt;br&gt;&lt;br&gt;The tool (i.e. the DLL) is OpenSource under the BSD license which allows anyone to use it even in ClosedSource projects as long as the conditions of the license are met.&lt;br&gt;&lt;br&gt;The DLL as it is provided for download from&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://assarbad.info/stuff/MACkerer2.rar"&gt;http://assarbad.info/stuff/MACkerer2.rar&lt;/a&gt;&lt;br&gt;was running for more than 2 years in its current form on Windows 2000 Server and Windows 2003 Server and has proven its reliability. The method was, as I pointed out, implemented earlier in a Delphi DLL and is approx. 1 year older than the version of the DLL offered.&lt;br&gt;&lt;br&gt;Have fun with MACkerer2 ... and spread the word!&lt;br&gt;&lt;br&gt;// Oliver</description></item><item><title>gimp Milan</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#1322458</link><pubDate>Tue, 19 Dec 2006 07:41:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1322458</guid><dc:creator>gimp Milan</dc:creator><description>&lt;p&gt;Ah now for the best part. I had always wanted to test this callout API thing. This is perhaps the most powerful way to leverage your Windows DHCP server. With the DHCP server callout, in a way, the whole DHCP server source code is before you for you to change and fine tune to your specific needs. In reality you really don't get the source code access but you do get all the power you would get had you really had the source code access. This is perhaps the best way to encourage people to build upon and extend your software's capability while still staying in the commercial&amp;amp;nbsp;realm and without throwing open the product's source code.&amp;amp;nbsp;I won't discuss the&amp;amp;nbsp;nitty-gritties of this callout technique as it has been properly documented&amp;amp;nbsp;here: DHCP Server callout API.&lt;/p&gt;
&lt;p&gt;I do not agree. Go to &lt;a rel="nofollow" target="_new" href="http://www.hotelsmall.info/laurel_Italy/abstruse_Lombardia/gimp_Milan_1.html"&gt;http://www.hotelsmall.info/laurel_Italy/abstruse_Lombardia/gimp_Milan_1.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>crayon La%20Baule</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#1481062</link><pubDate>Wed, 17 Jan 2007 04:12:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1481062</guid><dc:creator>crayon La%20Baule</dc:creator><description>&lt;p&gt;Ah now for the best part. I had always wanted to test this callout API thing. This is perhaps the most powerful way to leverage your Windows DHCP server. With the DHCP server callout, in a way, the whole DHCP server source code is before you for you to change and fine tune to your specific needs. In reality you really don't get the source code access but you do get all the power you would get had you really had the source code access. This is perhaps the best way to encourage people to build upon and extend your software's capability while still staying in the commercial&amp;amp;nbsp;realm and without throwing open the product's source code.&amp;amp;nbsp;I won't discuss the&amp;amp;nbsp;nitty-gritties of this callout technique as it has been properly documented&amp;amp;nbsp;here: DHCP Server callout API.&lt;/p&gt;
&lt;p&gt;I do not agree. Go to &lt;a rel="nofollow" target="_new" href="http://www.myromehotel.info/toll_France/caisson_Pays%20de%20la%20Loire/crayon_La%20Baule_1.html"&gt;http://www.myromehotel.info/toll_France/caisson_Pays%20de%20la%20Loire/crayon_La%20Baule_1.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#2394495</link><pubDate>Thu, 03 May 2007 17:12:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2394495</guid><dc:creator>Phill Bowden</dc:creator><description>&lt;p&gt;Great post. The MSDN documentation on this stuff is ok, but it contains a flaw in not telling us that the registry value required is &amp;quot;CalloutDlls&amp;quot;. Without that info no-one is going to be able to use this stuff, and this is the only place I was able to find it.&lt;/p&gt;
</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#4275752</link><pubDate>Tue, 07 Aug 2007 12:58:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4275752</guid><dc:creator>Marc Thomas</dc:creator><description>&lt;p&gt;Has anyone managed to use DHCPPacketSendHook or DhcpNewPktHook to modify the packet and add more options for example. I understand the API reasonably well, however it isn't obvious how to handle memory allocation/freeing etc when extending the packet. Has anyone done this?&lt;/p&gt;
</description></item><item><title>I do not think so</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#4392880</link><pubDate>Wed, 15 Aug 2007 03:31:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4392880</guid><dc:creator>warsaw hotels</dc:creator><description>&lt;p&gt;Ah now for the best part. I had always wanted to test this callout API thing. This is perhaps the most powerful way to leverage your Windows DHCP server. With the DHCP server callout, in a way, the whole DHCP server source code is before you for you to change and fine tune to your specific needs. In reality you really don't get the source code access but you do get all the power you would get had you really had the source code access. This is perhaps the best way to encourage people to build upon and extend your software's capability while still staying in the commercial&amp;amp;nbsp;realm and without throwing open the product's source code.&amp;amp;nbsp;I won't discuss the&amp;amp;nbsp;nitty-gritties of this callout technique as it has been properly documented&amp;amp;nbsp;here: DHCP Server callout API.&lt;/p&gt;
&lt;p&gt;I do not agree. Go to &lt;a rel="nofollow" target="_new" href="http://apartments.waw.pl/"&gt;http://apartments.waw.pl/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#6907424</link><pubDate>Sun, 30 Dec 2007 14:41:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6907424</guid><dc:creator>Son Vuong Kim</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The good work. I am researching DHCP for detect new computer when plug in LAN, so You could share your code to me .&lt;/p&gt;
&lt;p&gt;Thanks very much&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#6907429</link><pubDate>Sun, 30 Dec 2007 14:43:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6907429</guid><dc:creator>Son Vuong Kim</dc:creator><description>&lt;p&gt;My email: vuongkimson@gmail.com&lt;/p&gt;
</description></item><item><title>re: All about the DHCP server callout API functions.</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#8337906</link><pubDate>Wed, 26 Mar 2008 18:43:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8337906</guid><dc:creator>Dave</dc:creator><description>&lt;p&gt;Is there a way not to allow the dhcp server to assign an IP to a machine until you make a reservation for the machine, without using the call out api?&lt;/p&gt;
&lt;p&gt;for example, on a Linux machine, you can configure the Linux DHCP server with option &amp;quot;ignore unknown-clients&amp;quot; to forbid the server assign IPs to unknown machines.&lt;/p&gt;
&lt;p&gt;Thank&lt;/p&gt;
&lt;p&gt;Dave&lt;/p&gt;
</description></item><item><title>Concesi?n direcciones por DHCP | hilpers</title><link>http://blogs.msdn.com/anto_rocks/archive/2005/02/25/380510.aspx#9350142</link><pubDate>Tue, 20 Jan 2009 22:18:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9350142</guid><dc:creator>Concesi?n direcciones por DHCP | hilpers</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.hilpers-esp.com/387544-concesion-direcciones-por-dhcp"&gt;http://www.hilpers-esp.com/387544-concesion-direcciones-por-dhcp&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>