undiagnosed errors in the system log

[Guest]

source: server
type: error
event id: 2510
message: The server service was unable to map error code 1351.

Used net helpmsg to resolve 1351 and it says:
Configuration information could not be read from the domain controller,
either because the machine is unavailable, or access has been denied.

Problem is I have no Idea what process is trying to read this configuration
info. or what info it is trying to read.

notes:
-errors have been occuring intermittently for the last month
-I can not correlate any activity to the times of the error messages
-I thought it might be a group policy problem, but I have eliminated that as
a possibility
-all internet searches for event id 2510 with code 1351 have had no success
-the domain controller where the error is occuring is the PDC emulator
-no other domain controllers have this error
-no know user rights or permissions were change prior to seeing the error

 

[Cary Shultz [A.D. MVP]]

BSlate,

I assume that you have already looked at the following:

http://www.eventid.net/display.asp?eventid=2510&eventno=559&source=Server&phase=1

Unfortunately, there is no real answer there.

Are you having any AD Replication errors? I am thinking that the
'Configuration' info could be the Configuration NC...one of the three NCs in
Active Directory ( the Configuration NC, the Schema NC and the Domain NC ).

This might help us more......have you installed the Support Tools and run
dcdiag /v and netdiag /v?

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com

 

[Guest]

Yes, I had already seen that post. I did run the dcdiag /v and netdiag/v and
the only errors I got were from dcdiag and related to the system log errors
I'm trying to figure out. No replication errors showing in the logs.

I do have more information now.

About half of our users, because of a legacy application, are using W98. I
was told this morning that they are no longer able to change their network
passwords using a custom change password program that shells out to run "net
password". Armed with this info. I was able to correlate the change password
attempts with the errors in the system log.

But now my problem is that I cannot understand why "net password" is failing
and causing this error.