This behavior can occur because of network outage or if the Wins server is down.
1. Check if this issue is reoccuring
2. Check the uptime and the connectivity of both servers
3. Check if the Wins server is running / configured correctly
4. This could also be caused by a Firewall / NAT issue.
This event may indicate a WINS server under constant stress. See "JSI Tip 1849" for additional information about this issue.
On our Firewall, NAT was enabled. When I turned off NAT for the WINS servers, the problem was solved.
When you have two Windows Internet Name Service (WINS) servers that are configured to replicate with each other across a router or firewall, you may receive this error in the event log. See ME174395
for more information.
This message usually occurs when a WINS server is down and one of its replication partners tries to connect to it. The message is recorded in the replication partner log. It could also mean that a router or firewall is blocking the protocols required for WINS replication.
Error caused by WINS server attempts to replicate with "ghost" servers, such as 169.254.x.x or previously removed WINS servers. See ME135844
on how to remove ghost enteries.