Re: Windows 2000 Replication Issue (Error ID 1311) & (Endpoint Mapper)

Tech-Archive recommends: Fix windows errors by optimizing your registry

Try running netdiag, repadmin and dcdiag. Look for fail, error and warning
errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /s:DC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
start c:\repl.txt


See for more details

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/1d4ce93c-54f2-4069-a708-251509c38837.mspx



Endpoint mapper specific KB article
http://support.microsoft.com/?kbid=839880

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


"deckydee" <deckydee@xxxxxxxxxxx> wrote in message
news:1126774999.560408.203160@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I am hoping that someone can help me out here as I am in a spot of
> bother! :o)
>
> I am consultant that has to go to a company next week because they are
> getting an error in their Windows 2000 Replication Monitor:
>
> 'Replication Failure: The reason is: There are no more endpoints
> available from the endpoint mapper'
>
> That is not all; when I go to the Directory Service Event viewer I get
> this error as well:
>
> Event Type: Error
> Event Source: NTDS KCC
> Event Category: (1)
> Event ID: 1311
> Date: 14-9-2005
> Time: 16:05:37
> User: N/A
> Computer: IBADC00
> Description:
> The description for Event ID (1311) in Source ( NTDS KCC ) cannot be
> found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: DC=UPP,DC=XXX.
>
> So as you can imagine, down the right left hand side, I have three
> servers that have a red 'X' on them and the rest are ok.
>
> The first thing that I did was I researched the 'Endpoint Mapper'
> problem, I was directed to this site:
>
> http://support.microsoft.com/?kbid=839880
>
> I can already tell you at this stage that the correct entries are in
> the registry and that Port 135 is listening.
>
> Then after not having much success with that I moved to research the
> '1311' problem.
>
> There were several discussion groups about this error, but none that I
> fell can solve my problem.
>
> I also tried this site, but even though it said that it was for
> 'Troubleshooting error 1311, it does not have the same error as I do.
> Even if I did, I don't understand it too well. You see the other
> error messages don't have "The local computer may not have the
> necessary registry information or message DLL files to display messages
> from a remote computer"
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q214745
>
> My real problem is that because of the two separate errors, I am not
> sure if the problem is RPC or KCC!
>
> I also checked this site:
>
> http://support.microsoft.com/?id=244368
>
> And found nothing of much use.
>
> To be 100% sure about what I am doing I have read this site:
>
> http://support.microsoft.com/kb/199174/en-us
>
> But before you start, I am guessing that I have to do the following:
>
>
> 1 - Verify that DNS is working by going to the main DC and typing:
>
> (NSLookup [FQDN of the DC in remote site, e.g. dc3.domain.local])
>
>
> 2 - Check whether Time Service is synchronizing on the problematic
> servers
>
> Could someone please be so kind as to help me out here and tell me what
> the problem is? I would greatly appreciate it
>
> Declan D
>


.

Relevant Pages

  • Re: cant login to exchange
    ... Is your workstation configured to use one of your companys DNS servers? ... see Help and Support Center at ... > message DLL files to display messages from a remote computer. ...
    (microsoft.public.exchange2000.general)
  • Windows 2000 Replication Issue (Error ID 1311) & (Endpoint Mapper)
    ... The local computer may not have the necessary registry ... The first thing that I did was I researched the 'Endpoint Mapper' ... necessary registry information or message DLL files to display messages ...
    (microsoft.public.win2000.active_directory)