We have a n-tier (.net) web application where we have a Web tier -> App tier -> Database.
Everything worked fine until we went for load testing (using jmeter).
Your server is most probably overloaded as a result of your load test.
So it starts rejecting connections which appear as Connection Reset error.
So 3 options:
your load profile is too aggressive based on real traffic
your load profile is ok, your server is not correctly configured or undersized
your application cannot handle this load
You can check this by slowing rampup to see when you start facing issues.