Windows Server

Emerrlly · Guest

Cannot access primary domain from sub domian & vice versa.
WIN replication fail. WIN record of [20h] File Server is not to be
replicate between the two domain.

Robert L [MS-MVP] · Guest

A WINS event ID 4102 event message typically means that there is a communication failure during a WINS connection. check this web page for the resolutions,

Event ID 4102 - The connection was aborted by the remote WINS. Remote WINS may not be configured to replicate with the server
Resolutions:1. Make sure the all WINS servers are configured correctly such as from either Pull only or Push only, to Push/Pull...
http://www.chicagotech.net/Troubleshooting/eventid4102.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Emerrlly" <Emerrlly@discussions.microsoft.com> wrote in message news:BCBB4005-4DBF-462E-A46B-A664F22944C8@microsoft.com...
Cannot access primary domain from sub domian & vice versa.
WIN replication fail. WIN record of [20h] File Server is not to be
replicate between the two domain.

Emerrlly · Guest

Dear Robert L,
Thanks for your prompt action.
Previously when I setup my WIN is work smooth and fine for all the
replication and all the fuction. Only start from last week, the event ID
prompt out the Event ID 4102.
I already try to trouble shoot on this problem by remove all the replication
partner and add again. But this still not working !

"Robert L [MS-MVP]" wrote:

Paul Williams [MVP] · Guest

Bear in mind though, that although there might be WINS problems, this isn't
going to be causing cross-domain name resolution to be failing (well, it
might help, but isn't the be all and end all). DNS is what is needed for a
parent and child domain to have their trust working and cross-domain
authentication working.

How is your DNS setup? In Windows 2000 people usually had an Integrated
zone in both domains, with a delegation in the parent and a secondary zone
in the child domain (and the option to "append parent suffixes of the
primary DNS suffix" or a DNS suffix search list in the child and a DNS
Suffix Search list in the parent).

If WINS was helping with this in the past you should correctly configure DNS
now. You also need to start monitoring replication. Running DCDIAG /V /C
/E and NETDIAG /V from any Domain Controller will help start troubleshooting
if there are other problems (as well as DNS).

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

	Windows Server Forum Index -> Active Directory	All times are GMT
Page 1 of 1