When you see something like this in the log, what is happening is that the TS client tries to talk to the server using the WinHTTP library. When the WinHTTP library returns an error, the TS client will try to connect directly using WinSock.
In your case, the initial 'connect' fails. This is when the client sends a TCP connect packet and does not get back and ACK (and just times out after 20 seconds).
I can think of a few possible reaons.
1. The DNS returned the wrong host IP. The client ended-up talking to the wrong machine, and there is no service there.
2. The packets are getting lost.
3. The ISS service on the server is down.
For (2), you would need to do a network trace to see what is happening with your packets.
For (3), you need to look at the IIS logs. It could be that the service is getting reset.
<![LOG[Error. Received 0x80072ee2 from WinHttpSendRequest.]LOG]!><time="21:50:54.417+240" date="07-28-2015" component="TSMBootstrap" context="" type="1" thread="1944" file="libsmsmessaging.cpp:8870">
<![LOG[connect (sock, (struct sockaddr *) &SockAddrIn, sizeof (struct sockaddr_in)) == 0, HRESULT=8007274c (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,728)]LOG]!><time="21:51:15.426+240" date="07-28-2015"
component="TSMBootstrap" context="" type="0" thread="1944" file="libsmsmessaging.cpp:728">
<![LOG[socket 'connect' failed; 8007274c]LOG]!><time="21:51:15.426+240" date="07-28-2015" component="TSMBootstrap" context="" type="3" thread="1944" file="libsmsmessaging.cpp:728">
-
Edited by
Kerwin MedinaMicrosoft employee
7 hours 58 minutes ago