alexwhite19800
asked on
Application timeout
Hi
I have an application that runs on ServerA that needs to make a connection to ServerB.
Both are Windows 2012 Servers.
I had a couple of questions
1. If ServerB was hard down, is there a standard TCP timeout that applications utilise to confirm this
2. If ServerB was up, but the network path to ServerB was down, is this the same as situation A
3. If ServerB was up, but the network path to B was down, is the TCP response the same?
I have an application that runs on ServerA that needs to make a connection to ServerB.
Both are Windows 2012 Servers.
I had a couple of questions
1. If ServerB was hard down, is there a standard TCP timeout that applications utilise to confirm this
2. If ServerB was up, but the network path to ServerB was down, is this the same as situation A
3. If ServerB was up, but the network path to B was down, is the TCP response the same?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you. In relation to the TCP TTL, would you agree it's based on the source OS and the figures are:
http://subinsb.com/default-device-ttl-values
So if Server A is a Windows 2008 Server, the TTL for the packet would be 128ms?
http://subinsb.com/default-device-ttl-values
So if Server A is a Windows 2008 Server, the TTL for the packet would be 128ms?
The default would be 128 seconds, which is just over 2 minutes.
are you want to ensure the high availiblity for your app if yes you can use Windows Load Balancer it's a good solution for Layer 4 load balancing