Calling an asp webservice hosted by an ISP from our WCF service hosted on Windows 2008 Server is showing timeout/no response from webservice.
Using windows network monitor to packet capture and isolate packets sent a webservice i can see:
TLS handshake hello
TCP negotionating scale factor
TCP scale factor not supported
This appear to show no response to TCP payload which implies an IP block.
After contacting the webservice provider they have suggested that no IP block is in place and this issue is specific to Microsoft Windows 2008 Server, dynamic TCP Frame Size and their specific load balancers.
After some further research I believe the below will resolve.
To see the current configuration for the autoTuningLevel parameter, follow these steps:
click All Programs, and then click Accessories.
Right-click Command Prompt, and then click Run as Administrator.
If you are prompted for an administrator password or for confirmation, type the password, or clickContinue.
At the command prompt, type the following command, and then press ENTER: netsh interface tcp show global
The value for the autoTuningLevel parameter is listed as Receive Window Auto-Tuning Level.
We would expect this to be set to normal
At the command prompt, type the following command, and then press ENTER: netsh interface tcp set global autotuninglevel=disabled
The following list includes all possible values for the autoTuningLevel parameter:
/disabled: Sets the receive window at the default value.
/highlyrestricted: Lets the receive window grow beyond the default value, but does so very conservatively.
/restricted: Lets the receive window grow beyond the default value, but limits such growth in some scenarios.
/normal: Lets the receive window grow to accommodate most scenarios.
/experimental: Lets the receive window grow to accommodate extreme scenarios.
Note The experimental value may decrease performance in common scenarios. This value should be used only for research purposes.
Simply looking for further information on this problem from an independent source.
Hoping it will be patched by MS at some point.
Thank you Scott