Running an Internal Windows 2008 DHCP Server and Bell Aliant FibreOp
As I work from home, employed in the computer field, my home network is slightly more complex than the standard home network. One of the things I do different is run my DHCP server on a Windows 2008 Server instead of the one supplied with the Bell Aliant FibreOp “modem” (as my Internet is a FibreOp connection).
This issue I was running into is when the FibreOp modem needed to get an IP address after powering on, it would get it from my internal DHCP server. By having one of my internal IPs the modem could not talk to the Bell Aliant IP TV network thus I could not get TV. When the Bell Aliant modem cannot get an IP or cannot connect to the IP TV network it continuously reboots every 30 seconds or so.
What I discover that Microsoft has a callout DLL for the DHCP server that when installed allows you to Allow and/or Deny DHCP access by MAC address. The nice thing about the Bell Aliant modem is when it boots it shows you the MAC Address so it is easy to find.
To install the callout dll for the DHCP server, the binaries and instructions can be found at http://blogs.technet.com/b/teamdhcp/archive/2007/10/03/dhcp-server-callout-dll-for-mac-address-based-filtering.aspx . There are both 32-bit and 64-bit installers.
One note, when you enter the MAC address you wish to filter in the MACList.txt file, the sample file has the MAC Address as XX-XX-XX-XX-XX-XX, you need to remove the dashes for it to work.
Previously, if the power went out (for example) I had to turn off my DHCP server, let the Bell Aliant’s boxes fully boot, then turn on my DHCP server. The big issue was if I was not home and the power went out the wife and kids had no TV until I got home.
Note: Windows 2008 Server R2 has the MAC filter built in.







