I was wondering about the ramifications of implementing the ClassIDs for purposes of rudimentary NAC. If all the domain computers were to be set to use a proper User Class ID scope and the non-ClassID scope to be configured with intentionally wrongly configured gateway and DNS addresses, this would prevent rogue devices from joining the network upon jacking in. However, a company laptop would not be able to get an IP address anywhere outside the corporate network, unless the Class ID is removed, and the users are given administrative rights on the laptops to do so. I was trying to verify that this is the case, but there is no mention of this in your article. It should have been covered.

Alper8/4/2009 10:37:55 AM

succinct

Anonymous User 3/22/2005 11:07:36 AM

Great Article

Anonymous User 2/21/2005 12:53:55 PM

I posted a comment last time...well now that a new problem has arised...it worked once but many a times i am failing...
the nic seems to accept the accounts dhcp class what i gave....but not taking the scope of that class,rather taking scope of another class HR
what could be the problem.....in use is RTL8139

Raghu6/23/2004 1:14:32 AM

Zubair, Well Done

Raghu6/22/2004 12:31:00 PM

very good explenation

Rui Machado 4/8/2004 9:55:48 AM

Simply superb explanation. Straight to Point

neel3/5/2004 3:44:53 AM

Can this DHCP class ID be set in a domain or group policy?

Steven Gallagher 8/17/2001 8:58:54 AM