Page 1 of 1
limiting dhcp scopes to certain devices
#1
Posted 09 November 2009 - 09:22 AM
Here is a question to the experts:
Is there any way to limit DHCP scopes to a certain type of device (in my case printers) by filtering MAC adresses or another property which is unique to a certain device type?
Is there any way to limit DHCP scopes to a certain type of device (in my case printers) by filtering MAC adresses or another property which is unique to a certain device type?
#2
Posted 09 November 2009 - 09:45 AM
Well, I'm not too sure about other means, but MAC addresses are unique to the manufacturer, not the device type.
If you had the MAC addresses of all your printers you could just created IP reservations.
If you had the MAC addresses of all your printers you could just created IP reservations.
#3
Posted 09 November 2009 - 04:57 PM
actually I would like to get around using reservations. if there was a possibility to filter for somelthing like "MAC adress begins with AA-BB-CC or AA-BB-DD" and limit the scope to that, that would be a great help. As right now the situation is that most of my printer NICs are from not more than 2 different manufacturers. (We got a pretty homogenous printer collection)
edit:
this looks interesting
http://blogs.technet.com/teamdhcp/archive/...allout-dll.aspx
edit:
this looks interesting
http://blogs.technet.com/teamdhcp/archive/...allout-dll.aspx
This post has been edited by bj-kaiser: 09 November 2009 - 05:35 PM
#4
Posted 09 November 2009 - 09:08 PM
bj-kaiser, on Nov 9 2009, 04:57 PM, said:
actually I would like to get around using reservations. if there was a possibility to filter for somelthing like "MAC adress begins with AA-BB-CC or AA-BB-DD" and limit the scope to that, that would be a great help. As right now the situation is that most of my printer NICs are from not more than 2 different manufacturers. (We got a pretty homogenous printer collection)
edit:
this looks interesting
http://blogs.technet.com/teamdhcp/archive/...allout-dll.aspx
edit:
this looks interesting
http://blogs.technet.com/teamdhcp/archive/...allout-dll.aspx
Link How-to
Link Technet
Not sure you will need that add-in dll, but does look like it has cool features. Post back if it's easy to use, we have a need to banish all iPhones in my house. Modern Punishments for Modern Kids.
This post has been edited by MrJinje: 09 November 2009 - 09:26 PM
#5
Posted 10 November 2009 - 04:59 AM
MrJinje, on Nov 10 2009, 04:08 AM, said:
Check out these links. Looks simple enough, probably need entries for each printer mfg.
Link How-to
Link Technet
Not sure you will need that add-in dll, but does look like it has cool features. Post back if it's easy to use, we have a need to banish all iPhones in my house. Modern Punishments for Modern Kids.
Link How-to
Link Technet
Not sure you will need that add-in dll, but does look like it has cool features. Post back if it's easy to use, we have a need to banish all iPhones in my house. Modern Punishments for Modern Kids.
The two links of you do not really help me. They describe how to use user/vendor classes to hand out different settings depending on the user/vendor class the DHCP client sends with its request. (example: hand out adresses of provisioning servers to IP phones and the like).
This does not allow you to separate clients into different scopes/ip-ranges by user or vendor class.
and on your iphone problem, take a look at your DHCP traffic with the network monitor and figure out if the iPhones send DHCP vendor class in their requests. My printer NICs apparently don't.
And always remember, DHCP is a protocol from the good old times. you can always send a different vendor class if you can manipulate your DHCP client. So take that option of not handing them out IP adresses by blocking a certain vendor class with a grain of salt.
#6
Posted 10 November 2009 - 09:17 AM
I'm not too familiar with this, but I have been told that you can do that with VLAN's.
#8
Posted 03 February 2010 - 10:10 AM
using a Vlan to connect the ports used by the printer and then assigning the DHP scope to the Vlan may be easier then trying to filter out ever other device on your network (not to mention putting a larger workload on your DHCP server) is there a need too have all th eprinters set to DHCP would it be preferable to set static IP's to printers to make it easier to find and remeber said printers?
Share this topic:
Page 1 of 1



Help
Back to top









