Everything, Everything

2024: J F M A M J J A S O N
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
SendExtraRecord
Tuesday 23rd April, 2013 17:30 Comments: 0
Stupidly, I enabled the SendExtraRecord on one of my servers. According to Microsoft, this breaks:
  • SQL Server
  • Terminal Services/Remote Desktop with Network Level Authentication (NLA)
  • Some Routing Remote Access Service (RRAS) scenarios
Well that would certainly explain why I can't remote desktop into the server anymore. Doh!

An authentication error has occurred.
The token supplied to the function is invalid

SendExtraRecord is bad

EDIT: By disabling all ciphers except a couple of RC4 ones (128-bit SHA and MD5) or by changing the priority of ciphers so the RC4 ones are first, it's possible to Remote Desktop back in and undo the damage. It was quick and easy (aside from having to reboot Windows for the new settings to kick in) using this neat free tool: IIS Crypto.
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3