1.
ASP.Net has a inbuilt feature to filter all the requests for malicious inputs like XSS. If the request processor finds a string value after the < symbol, then the
Request filtering would kick in and throw an error message similar to
"a potentially dangerous value was detected from ..."
A known vulnerability related to it is filed here -
http://www.securityfocus.com/archive/1/464796.
This request filtering feature could be enabled at page level or site level. May be you would be lucky finding a page that has this feature turned off.
2.
If the request filtering is turned off, then the website may employ some kind of AntiXss library to filter input data. The popular framework to do this in the Microsoft stack is the
Microsoft AntiXss library which is known for a vulnerability listed here -
http://blog.watchfire.com/wfblog/2012/01/microsoft-anti-xss-library-bypass.html3. The webpage may employ in-house custom written anti-xss libraries that you can bypass by trial and error.
Choose your fuzzing method based on the above points. If it is custom blacklist behind the filter you may have a better chance by trial and error.
to confirm if there is an Xss or not, please refer to the methodology per the recent G4H webcast -
http://www.garage4hackers.com/showthread.php?t=6042 [Direct youtube link -
https://www.youtube.com/watch?v=TKn5qdti66c]