zag wrote:Maybe something to do with the redirect i'm using in IIS, I will investigate.
Ahh... IIS, something I know nothing about. And because of that, this is just pure speculation on my part...
It seems like your server might be trying to connect to my server before returning the reply. Which, because there's no public facing IP for my development server, that's not possible and your server might be dropping the reply.
To explain, I have a router with a single public IP assigned to it. My development server is connected to that router, but is not accessible by the public IP. The router handles information returned and routes it to the proper machine. If your server attempts to actually connect to the router's public IP address (instead of just sending the reply), it will fail. And I believe it's that failure that causes the connection to be dropped.
Again, that's pure speculation from a somewhat warped thought process.