The “netsh advfirewall consec” command does not preserve the order of the authentication methods that are specified in a connection security rule on a Windows Vista-based computer
You use the netsh advfirewall consec command together with the auth1 or auth2 authentication parameters to create a connection security rule that will work together with authentication methods that are specified on a Windows Vista-based computer. After you do this, the order of the values that you specify for the auth1 or auth2 parameters is not preserved in the connection security rule. Regardless of the order in which you specify the values for the auth1 and auth2 parameters, the connection security rule is created together with authentication parameters that are specified in the following order:
Auth1: ComputerKerb, ComputerCert, ComputerPSK, ComputerNTLM, Anonymous
Auth2: ComputerCert, UserKerb, UserCert, UserNTLM, Anonymous
For example, the following command creates a connection security rule that lists the ComputerKerb authentication method before the ComputerNTLM authentication method in the first authentication set:
netsh advfirewall consec add name=�Authentication Test� endpoint1=any endpoint2=any action=requestinrequestout auth1=computerntlm,computerkerb
Note: The netsh advfirewall consec set command also displays the same behavior when you use the auth1 or auth2 parameter with it.
For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB942963.

Start
About
FAQ
Blogroll
Shop
Tips and Tricks
Windows Updates
Hotfixes
Keyboard Shortcuts
Vista's Services
Vista's Commands
Product Reviews
Glossary
Videos
Web Links

Comments
There are no comments yet...Come on, share your thoughts!
Leave a Comment