This refers to a too early closed question: http://social.technet.microsoft.com/Forums/windowsserver/en-US/1b92513d-5a41-4c14-9e3e-f35eebccd4d3/nps-calling-station-id-field-limit?forum=winserverNAP
I'm sorry, but regex does not help.
We need to authenticate per mac, and even we cut them in half per regex (remove the vendor string), it would still exceed the 256 chars limit.
Currently we are using the method stated in the tip from http://blogs.technet.com/b/nap/archive/2006/09/08/454705.aspx and the result is a Calling Station ID of 1080 chars and growing.
If there really is no other solution, this is a huge step back from server 2003 ias.
As mentioned, NPS service itself accepts more than 256 chars, but the GUI does not => why was this implemented?!?
I'm sorry, but regex does not help.
We need to authenticate per mac, and even we cut them in half per regex (remove the vendor string), it would still exceed the 256 chars limit.
Currently we are using the method stated in the tip from http://blogs.technet.com/b/nap/archive/2006/09/08/454705.aspx and the result is a Calling Station ID of 1080 chars and growing.
If there really is no other solution, this is a huge step back from server 2003 ias.
As mentioned, NPS service itself accepts more than 256 chars, but the GUI does not => why was this implemented?!?