As per Microsoft: "The computer was expecting data from another computer but has not received it. Either the other computer is not sending, or the thread on this computer that listens for data has encountered an error". See MSW2KDB
for more information.
From a newsgroup post: "I encountered this error myself some time ago. I discovered that it happened after I installed a fiber virtual NIC for our SAN backup solution. I suspected that it had something to do with the adapter binding order. I moved the physical NIC to the top of the binding list, rebooted and this solved the problem. Check your source and destination server, whether your adapter binding order is correct".
As per Microsoft, the computer was expecting data from another computer but has not received it. Either the other computer is not sending, or the thread on this computer that listens for data has encountered an error.
See also the link below for detailed information about NetDDE.
We originally received events that the teamed nics had dropped their links to the network. Upon their recovery we received the event id 206, listen failed 15 (Source netdde). This event happens every 30 minutes.
To resolve, we restarted the NETdde service and the events quickly subsided. Associated with this service is our Seagate Page Server that is run on a number of our machines. It also needed to be restarted. When restarting Netdde service, the Seagate Page Server was a dependent and was restarted as well. I have seen some speculation that initial cause of the disconnection of the nics is due to the binding order in the advanced setting. I have swapped the binding order of the cpqteam and tcpip objects to see if this resolves our initial problem. Also instead of Load balancing the team, we are testing the fault tolerance setting instead.