Connection to webserver - TCP reset from server

This link is accessible within our LAN but not when a user on distant is using Direct Acces. It worked until about 10 days ago, then suddenly the webserver refuse connection with the message "TCP reset from server" for traffic from users with Direct Access.

Windows server 2012 R2 with IIS.

No local Firewall

No other Firewall is blocking the connection

Routing is correct.

nslookup works

But still the webserver refuse connection from client with the message "TCP reset from server". But no problem if the user is in place and directly on the LAN.

netstat - aon displays port 80 is PID 4 listening - NT Kernel & System.

Server was patched about 12 days ago with Microsoft latest security updates.

I hope here is text that shows what I have done and the result in a more readable form:

1. Using curl from server within the LAN and run aginst the problem server:

curl -v -H "Range: bytes=00-18446744073709551615"

  • Trying 123.456.78.99... * TCP_NODELAY set * Connected to test.domian.com (123.456.78.99) port 80 (#0) > GET /test HTTP/1.1 > Host: > User-Agent: curl/7.55.1 > Accept: / > Range: bytes=00-18446744073709551615 – < HTTP/1.1 400 Bad Request < Content-Type: text/html; charset=us-ascii < Server: Microsoft-HTTPAPI/2.0 < Date: Wed, 20 Oct 2021 13:00:43 GMT < Connection: close < Content-Length: 339 <
Bad Request

Bad Request - Invalid Header


HTTP Error 400. The request has an invalid header name.

2. Using curl from client on distant with Direct Acces:

curl -v -H "Range: bytes=00-18446744073709551615" * Trying 123.456.78.99... * TCP_NODELAY set

  • Connected to test.domain.com (123.456.78.99) port 80 (#0) > GET / HTTP/1.1 > Host: test.domain.com > User-Agent: curl/7.55.1 > Accept: / > Range: bytes=00-18446744073709551615 >
  • Recv failure: Connection was reset * Closing connection 0 curl: (56) Recv failure: Connection was reset –

As you can see I get 2 different results when I'm using curl:

  1. Result on place in LAN when type the same url in a webbrowser
  2. Result on a client when user is sitting on distant with Direct Access and type the same url in a webbrowser.

Summation:I cannot reach this URL when I try http: // only if I use https: //

17 Reset to default

Know someone who can answer? Share a link to this question via email, Twitter, or Facebook.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like