Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

WINS shows some Unknown servers and Event ID 4102

Active Directory, Domain, DNS, WINS, DHCP, SBS, New Releases.

WINS shows some Unknown servers and Event ID 4102

Postby chicagotech » Fri May 30, 2008 8:47 pm

Q: our WINS server has the following event.
Event Type: Error
Event Source: Wins
Event Category: None
Event ID: 4102
Date: 4/29/2008
Description:
The connection was aborted by the remote WINS. Remote WINS may not be configured to replicate with the server.
Data:
0000: 37 03 00 00 08 00 00 e0 7......à

When I open the WINS Replication Partners, I see 3 Unknown servers under server name. After deleting these 3 unknown servers, I don't have this event. But I worry they may come back. Why are they here? How can I prevent these unknown servers show up in the WINS?

A: a WINS event ID 4102 event message typically means that there is a
communication failure during a WINS connection. This may occur if a WINS
server is configured as a Push or Pull partner with a computer that is not
configured as a partner with the first WINS server. You need to verify
that all WINS Servers in the environment are correctly configured.

You can re-add replication partner as follow steps.

1. Remove the replication partner in WINS console on both Servers.
2. Open command prompt, type these commands and type Enter:
Net stop wins
Cd c:\windows\system32\wins
Jetpack wins.mdb tmp.mdb
Net start wins.
3. Open WINS console, right click Replication partners and click New
Replication partner.
4. Add the IP address of the other WINS server on both Server and click OK.
5. Then please check the issue and monitor it for a period of time.

This issue can be also caused when the WINS server is multi-homed. When
configuring replication partners, only one IP address may be entered for a
given partner. If you attempt to add another IP address for the same
replication partner, WINSADMN realizes that this is the same system as the
one previously already entered, and switches the IP address in the list to
the one that the WINS server is bound to on the remote machine.

However, when replication actually occurs, Windows Sockets is the interface
used. The outgoing pull request uses socket()/bind()/connect() calls, and
on the bind it specifies INADDR_ANY. This means that the outgoing call can
be sourced from any IP address on a computer. If it's sourced from any IP
address other than the one that the WINS server is bound to, replication
fails. The event log will container "Connection aborted by remote client."
The replication fails because the WINS server being contacted compares the
source address of the incoming requests to its list of authorized
replication partners.

In this situation, you need to make sure that each IP address should be
entered as a replication partner on all machines that will replicate with a
multi-homed computer.

More information:

Event 4102 Error with WINS Server
http://support.microsoft.com/kb/137849

Multihomed WINS Server Replication Partner Failures
http://support.microsoft.com/kb/139380

Troubleshooting WINS error event ID 4102, 4243, 4242, and 4286 messages
http://support.microsoft.com/kb/321208/en-us

WINS replication overview
http://technet2.microsoft.com/windowsse ... ba-4250-8b
6b-7b3465ab29731033.mspx?mfr=true

185786 Recommended Practices for WINS
http://support.microsoft.com/?id=185786

WINS replication overview
http://technet2.microsoft.com/windowsse ... ba-4250-8b
6b-7b3465ab29731033.mspx?mfr=true

185786 Recommended Practices for WINS
http://support.microsoft.com/?id=185786
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 7066
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Postby chicagotech » Fri May 30, 2008 8:48 pm

the WINS server does have the feature of enable
automatic partner configuration. You can configure a WINS server to
automatically configure other WINS server computers as its replication
partners. With this automatic partner configuration, other WINS servers
are discovered when they join the network and are added as replication
partners. With this configuration, it will enable the WINS server to
monitor multicast announcements from other WINS servers and to perform the
following configuration steps automatically. When you configure the
Automatic partner configuration option, the WINS server:

1. Adds the IP addresses for the discovered servers to its list of
replication partner servers.
2. Configures the discovered servers as both push and pull partners.
3. Configures pull replication at two-hour intervals with the discovered
servers.

So please check the properties of the Replication partner in the WINS
console to make sure that the enable automatic partner configuration is not
enabled.

For more information, please check the below link for your reference.

Enable automatic partner configuration
http://technet2.microsoft.com/windowsse ... 6e-4cb9-91
63-fc84992134231033.mspx?mfr=true

Specifying Automatic Partner Configuration
http://technet2.microsoft.com/windowsse ... 14-4e01-a3
ba-e40848efe9c51033.mspx?mfr=true
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 7066
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Postby chicagotech » Fri May 30, 2008 8:49 pm

Your are right about "the WINS server does have the
feature of enable automatic partner configuration". I found the some
computers were added the replication Partners again. I just disable
automatic partner configuration. I will post back if we have the same issue.

Thank you very much.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 7066
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Postby guest » Sun Jun 01, 2008 10:01 am

We had two cases like this one.

1. Whenever a client establishes the VPN, his windows domain controller registers the IP to the WINS server as partner.

2. One of technician setup a test SBS domain in their LAN. The SBS registers the SBS IP in the WINS as partner.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm


Return to Windows

Your Ad Here

Who is online

Users browsing this forum: No registered users and 9 guests