Event ID 4102, Server 2003 WINS

I continually keep getting this error in my primary WINS server. Event ID
4102, source WINS. The connection was aborted by the remote WINS. Remote
WINS may not be configured to replicte with the server.

How do I tell which WINS server this is applying to and what do I need to do
to correct it?

Thanks

Jeff

Break and restablish all replication scenarios. The error is basically
telling you that something is not right. MS recommends you create
a hub and spoke configuration where all WINS servers are pushing
and pulling with 1 main WINS server.

"Jeff M" <(E-Mail Removed) om> wrote in message news:
>I continually keep getting this error in my primary WINS server. Event ID
> 4102, source WINS. The connection was aborted by the remote WINS. Remote
> WINS may not be configured to replicte with the server.
>
> How do I tell which WINS server this is applying to and what do I need to
> do
> to correct it?
>
> Thanks
>
> Jeff

Only break and reestablish the replication scenarios on the primary WINS
server correct?

"Michael Giorgio - MS MVP" wrote:

> Break and restablish all replication scenarios. The error is basically
> telling you that something is not right. MS recommends you create
> a hub and spoke configuration where all WINS servers are pushing
> and pulling with 1 main WINS server.
>
> "Jeff M" <(E-Mail Removed) om> wrote in message news:
> >I continually keep getting this error in my primary WINS server. Event ID
> > 4102, source WINS. The connection was aborted by the remote WINS. Remote
> > WINS may not be configured to replicte with the server.
> >
> > How do I tell which WINS server this is applying to and what do I need to
> > do
> > to correct it?
> >
> > Thanks
> >
> > Jeff
>
>
>

Actually you can do this from any server running the WINS manager.
It is common to do this from ever WINS server and I believe that is
what causes the error. Just open the primary or main WINS server
and have it push and pull with each of your other WINS servers.

"Jeff M" <(E-Mail Removed)> wrote in message news:
> Only break and reestablish the replication scenarios on the primary WINS
> server correct?

I understand the push/pull apsect of the process but I want to clarify one
thing. Did you say to go and break or delete all my current replication
partner connections and recreate them?

"Michael Giorgio - MS MVP" wrote:

> Actually you can do this from any server running the WINS manager.
> It is common to do this from ever WINS server and I believe that is
> what causes the error. Just open the primary or main WINS server
> and have it push and pull with each of your other WINS servers.
>
> "Jeff M" <(E-Mail Removed)> wrote in message news:
> > Only break and reestablish the replication scenarios on the primary WINS
> > server correct?
>
>
>

No problem. Just break replication.

"Jeff M" <(E-Mail Removed)> wrote in message news:
>I understand the push/pull apsect of the process but I want to clarify one
> thing. Did you say to go and break or delete all my current replication
> partner connections and recreate them?

you'll need to use network monitor to identify the wins server that is
generating this message.
For more info check:
http://support.microsoft.com/default...b;en-us;321208
and some other hints here:
http://www.eventid.net/display.asp?e...e=Wins&phase=1


--
Regards,
Andrei Ungureanu
www.eventid.net
Test our new EventReader!
http://www.altairtech.ca/eventreader...lt2.asp?ref=au

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:%(E-Mail Removed)...
> No problem. Just break replication.
>
> "Jeff M" <(E-Mail Removed)> wrote in message news:
>>I understand the push/pull apsect of the process but I want to clarify one
>> thing. Did you say to go and break or delete all my current replication
>> partner connections and recreate them?
>
>