Since I still have Windows NT clients, I have set up two Windows 2000 WINS
servers in my enterprise (that also act as DNS and DC's). One (Alpha) is
multihomed and acts as a RRAS and DHCP server. I have set Alpha up for Pull
replication and Bravo for Push replication. For some odd reason WINS
decides on it's own to add all of the IP addresses of the machines,
including the ones I have already put in there as <unknown>(s).

I also get System Error 4102 (The connection was aborted by the remote WINS.
Remote WINS may not be configured to replicate with the server. ) in the
event log. What could be causing this behavior and how can I get WINS back
on track to replicate properly using only the internal IP addresses?

I have also disabled NetBios over TCP/IP for the (10.0.0.2) IP address.

Alpha (multihomed server)
Replication Partners
BRAVO (192.0.0.2) Push
<unknown> (192.0.0.2) Pull - Internal IP Address

Bravo
Replication Partners
ALPHA (192.0.0.1) Pull
<unknown> (192.0.0.1) Push - Internal IP Address
<unknown> (192.0.0.107) Push/Pull - DHCP/RRAS IP Address
<unknown> (10.0.0.2) Push/Pull - External IP address to router/firewall

Did you do the regedits of 292822 on the multihomed server?

Marina

"Jason Gallas" <(E-Mail Removed)> schreef in bericht
news:#(E-Mail Removed)...
> Since I still have Windows NT clients, I have set up two Windows 2000 WINS
> servers in my enterprise (that also act as DNS and DC's). One (Alpha) is
> multihomed and acts as a RRAS and DHCP server. I have set Alpha up for
Pull
> replication and Bravo for Push replication. For some odd reason WINS
> decides on it's own to add all of the IP addresses of the machines,
> including the ones I have already put in there as <unknown>(s).
>
> I also get System Error 4102 (The connection was aborted by the remote
WINS.
> Remote WINS may not be configured to replicate with the server. ) in the
> event log. What could be causing this behavior and how can I get WINS
back
> on track to replicate properly using only the internal IP addresses?
>
> I have also disabled NetBios over TCP/IP for the (10.0.0.2) IP address.
>
> Alpha (multihomed server)
> Replication Partners
> BRAVO (192.0.0.2) Push
> <unknown> (192.0.0.2) Pull - Internal IP Address
>
> Bravo
> Replication Partners
> ALPHA (192.0.0.1) Pull
> <unknown> (192.0.0.1) Push - Internal IP Address
> <unknown> (192.0.0.107) Push/Pull - DHCP/RRAS IP Address
> <unknown> (10.0.0.2) Push/Pull - External IP address to
router/firewall
>
>
>

No I did not, but thank you. I will try these and see if the problem is
resolved.

Jason

"Marina Roos" <(E-Mail Removed)> wrote in message
news:lq3Ma.71004$(E-Mail Removed)...
> Did you do the regedits of 292822 on the multihomed server?
>
> Marina
>
> "Jason Gallas" <(E-Mail Removed)> schreef in bericht
> news:#(E-Mail Removed)...
> > Since I still have Windows NT clients, I have set up two Windows 2000
WINS
> > servers in my enterprise (that also act as DNS and DC's). One (Alpha)
is
> > multihomed and acts as a RRAS and DHCP server. I have set Alpha up for
> Pull
> > replication and Bravo for Push replication. For some odd reason WINS
> > decides on it's own to add all of the IP addresses of the machines,
> > including the ones I have already put in there as <unknown>(s).
> >
> > I also get System Error 4102 (The connection was aborted by the remote
> WINS.
> > Remote WINS may not be configured to replicate with the server. ) in the
> > event log. What could be causing this behavior and how can I get WINS
> back
> > on track to replicate properly using only the internal IP addresses?
> >
> > I have also disabled NetBios over TCP/IP for the (10.0.0.2) IP address.
> >
> > Alpha (multihomed server)
> > Replication Partners
> > BRAVO (192.0.0.2) Push
> > <unknown> (192.0.0.2) Pull - Internal IP Address
> >
> > Bravo
> > Replication Partners
> > ALPHA (192.0.0.1) Pull
> > <unknown> (192.0.0.1) Push - Internal IP Address
> > <unknown> (192.0.0.107) Push/Pull - DHCP/RRAS IP Address
> > <unknown> (10.0.0.2) Push/Pull - External IP address to
> router/firewall
> >
> >
> >
>
>