Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 4102 Source: Wins

Connection was aborted by the remote WINS
This message indicates that WINS replication is not configured properly. Check the Push/Pull partners of the server reporting the error.
In my case, I had this problem with a DC which had two IP addresses on the same subnet. After removing the second IP, everything worked as expected (including setting up the secure channel with a trusted domain's DC).
See ME925340 for a hotfix applicable to Microsoft Windows Server 2003.
Check ME185786 for some Microsoft recommended practices for WINS.

As per MSW2KDB, this event record indicates that a replication failed with a partner. If the replication failure continuously occurs with the same replication partner, the partner might not be configured properly for replication.
In my case, this error appeared because the time on my servers was out of sync. After I synchronized the time, this error disappeared.

The very first thing to check for is a reboot of the Wins Server.
For Windows 2000 see also Microsoft Knowledge Base Article - ME289189 and ME321208.
When WINS and RRAS are on the same server, and WINS is replicating across a demand-dial interface, WINS must be set to replicate with any partner. See ME171168.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.