windows cannot determine user or computer name - refers to windows 2000 server

Posted July 19, 2008 · July 19, 2008

I have some serious issues with our windows 2000 server.

it is a domain controller, out 2003 server is the PDC with the FSMO roles.

it appears the 2000 server is no longer able to replicate with the 2003

server as per below:

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1000

Date: 7/18/2008

Time: 4:59:56 PM

User: NT AUTHORITY\SYSTEM

Computer: mywindows2000server

Description:

Windows cannot determine the user or computer name. Return value

(-2146893022).

here are the results for dcdiag:

Performing initial setup:

Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\mywindows2003server

Starting test: Connectivity

......................... mywindows2003server passed test

Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\mywindows2003server

Starting test: Replications

[Replications Check,mywindows2003server] A recent replication

attempt failed:

From mywindows2000server to mywindows2003server

Naming Context: CN=Schema,CN=Configuration,DC=mydomain,DC=com

The replication generated an error (8456):

The source server is currently rejecting replication requests.

The failure occurred at 2008-07-19 10:52:51.

The last success occurred at 2008-05-24 07:47:13.

1323 failures have occurred since the last success.

Replication has been explicitly disabled through the server

options.

Active Directory doesnt work from the 2000 server, when I try to open AD

from the 2000 server it says:

naming information cannot be located becasuse the target principal name is

not correct

What do I need to do to fix this? If it was just another XP machine I read

that I could move it to a workgroup then add it back to the domain to fix

the event ID 1000 error, but this is a 2000 server that is a domain

controller.

Would you demote it then do dcpromo?

Posted July 19, 2008 · July 19, 2008

Re: windows cannot determine user or computer name - refers to windows 2000 server

Yes,

I would demote it, and then follow the instructions carefully for adding a

new domain controller, especially regarding DNS.

Anthony,

http://www.airdesk.co.uk

"Gary" <garym_dontspame@hotmail.com> wrote in message

news:OGShiXb6IHA.4596@TK2MSFTNGP03.phx.gbl...

>

> I have some serious issues with our windows 2000 server.

>

> it is a domain controller, out 2003 server is the PDC with the FSMO roles.

>

> it appears the 2000 server is no longer able to replicate with the 2003

> server as per below:

>

> Event Type: Error

>

> Event Source: Userenv

>

> Event Category: None

>

> Event ID: 1000

>

> Date: 7/18/2008

>

> Time: 4:59:56 PM

>

> User: NT AUTHORITY\SYSTEM

>

> Computer: mywindows2000server

>

> Description:

>

> Windows cannot determine the user or computer name. Return value

> (-2146893022).

>

> here are the results for dcdiag:

>

> Performing initial setup:

>

> Done gathering initial info.

>

> Doing initial required tests

>

> Testing server: Default-First-Site-Name\mywindows2003server

>

> Starting test: Connectivity

>

> ......................... mywindows2003server passed test

> Connectivity

>

> Doing primary tests

>

> Testing server: Default-First-Site-Name\mywindows2003server

>

> Starting test: Replications

>

> [Replications Check,mywindows2003server] A recent replication

> attempt failed:

>

> From mywindows2000server to mywindows2003server

>

> Naming Context: CN=Schema,CN=Configuration,DC=mydomain,DC=com

>

> The replication generated an error (8456):

>

> The source server is currently rejecting replication requests.

>

> The failure occurred at 2008-07-19 10:52:51.

>

> The last success occurred at 2008-05-24 07:47:13.

>

> 1323 failures have occurred since the last success.

>

> Replication has been explicitly disabled through the server

> options.

>

> Active Directory doesnt work from the 2000 server, when I try to open AD

> from the 2000 server it says:

>

> naming information cannot be located becasuse the target principal name is

> not correct

>

> What do I need to do to fix this? If it was just another XP machine I

> read that I could move it to a workgroup then add it back to the domain to

> fix the event ID 1000 error, but this is a 2000 server that is a domain

> controller.

>

> Would you demote it then do dcpromo?

>

Posted July 19, 2008 · July 19, 2008

Re: windows cannot determine user or computer name - refers to windows 2000 server

Hello Gary,

If the server is not important and only for redundancy, the easiest way is

to demote it and promote it again. But the question is, what is the reason

for the replication problem. Maybe it occurs again. Can you post an unedited

ipconfig /all so that we can exclude DNS problem. Also post a complete dcdiag,

netdiag and repadmin /showrepl.

Best regards

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have some serious issues with our windows 2000 server.

>

> it is a domain controller, out 2003 server is the PDC with the FSMO

> roles.

>

> it appears the 2000 server is no longer able to replicate with the

> 2003 server as per below:

>

> Event Type: Error

>

> Event Source: Userenv

>

> Event Category: None

>

> Event ID: 1000

>

> Date: 7/18/2008

>

> Time: 4:59:56 PM

>

> User: NT AUTHORITY\SYSTEM

>

> Computer: mywindows2000server

>

> Description:

>

> Windows cannot determine the user or computer name. Return value

> (-2146893022).

>

> here are the results for dcdiag:

>

> Performing initial setup:

>

> Done gathering initial info.

>

> Doing initial required tests

>

> Testing server: Default-First-Site-Name\mywindows2003server

>

> Starting test: Connectivity

>

> ......................... mywindows2003server passed test

> Connectivity

>

> Doing primary tests

>

> Testing server: Default-First-Site-Name\mywindows2003server

>

> Starting test: Replications

>

> [Replications Check,mywindows2003server] A recent replication

> attempt failed:

>

> From mywindows2000server to mywindows2003server

>

> Naming Context:

> CN=Schema,CN=Configuration,DC=mydomain,DC=com

>

> The replication generated an error (8456):

>

> The source server is currently rejecting replication

> requests.

>

> The failure occurred at 2008-07-19 10:52:51.

>

> The last success occurred at 2008-05-24 07:47:13.

>

> 1323 failures have occurred since the last success.

>

> Replication has been explicitly disabled through the

> server options.

>

> Active Directory doesnt work from the 2000 server, when I try to open

> AD from the 2000 server it says:

>

> naming information cannot be located becasuse the target principal

> name is not correct

>

> What do I need to do to fix this? If it was just another XP machine I

> read that I could move it to a workgroup then add it back to the

> domain to fix the event ID 1000 error, but this is a 2000 server that

> is a domain controller.

>

> Would you demote it then do dcpromo?

>

Posted July 20, 2008 · July 20, 2008

Re: windows cannot determine user or computer name - refers to windows 2000 server

well, I wouldnt say it was entirley unimportant, as it is our WSUS server,

and hosts the corp antivirus management software, and a few printers are

shared off of it.

but as long as the other servers are running I am okay networking wise.

if demoting it and promoting it back would work I am fine with that, but I

am willing to look at anything to resolve this.

here are the results from the test you suggested (I did notice something

about inbound replication being disabled, and simply running the repadmin

option, it couldnt be that simple could it?)

dcdiag

DC Diagnosis

Performing initial setup:

Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\mywindows2000server

Starting test: Connectivity

.......................... mywindows2000server passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\mywindows2000server

Starting test: Replications

[Replications Check,mywindows2000server] Inbound replication is disabled.

To correct, run "repadmin /options

mywindows2000server -DISABLE_INBOUND_REPL"

[Replications Check,mywindows2000server] Outbound replication is disabled.

To correct, run "repadmin /options

mywindows2000server -DISABLE_OUTBOUND_REPL"

.......................... mywindows2000server failed test Replications

Starting test: NCSecDesc

.......................... mywindows2000server passed test NCSecDesc

Starting test: NetLogons

.......................... mywindows2000server passed test NetLogons

Starting test: Advertising

Warning: DsGetDcName returned information for

\\mywindows2003server.mydomain.com,

when we were trying to reach mywindows2000server.

Server is not responding or is not considered suitable.

[mywindows2003server] LDAP bind failed with error 31,

A device attached to the system is not functioning..

Server mywindows2000server is advertising as a global catalog, but

it could not be verified that the server thought it was a GC.

.......................... mywindows2000server failed test Advertising

Starting test: KnowsOfRoleHolders

[mywindows2003server] DsBind() failed with error -2146893022,

The target principal name is incorrect..

Warning: mywindows2003server is the Schema Owner, but is not responding to

DS RPC

Bind.

Warning: mywindows2003server is the Schema Owner, but is not responding to

LDAP B

ind.

Warning: mywindows2003server is the Domain Owner, but is not responding to

DS RPC

Bind.

Warning: mywindows2003server is the Domain Owner, but is not responding to

LDAP B

ind.

Warning: mywindows2003server is the PDC Owner, but is not responding to DS

RPC Bi

nd.

Warning: mywindows2003server is the PDC Owner, but is not responding to LDAP

Bind

..

Warning: mywindows2003server is the Rid Owner, but is not responding to DS

RPC Bi

nd.

Warning: mywindows2003server is the Rid Owner, but is not responding to LDAP

Bind

..

Warning: mywindows2003server is the Infrastructure Update Owner, but is not

respo

nding to DS RPC Bind.

Warning: mywindows2003server is the Infrastructure Update Owner, but is not

respo

nding to LDAP Bind.

.......................... mywindows2000server failed test KnowsOfRoleHolders

Starting test: RidManager

[mywindows2000server] DsBindWithCred() failed with error -2146893022. The

target

principal name is incorrect.

.......................... mywindows2000server failed test RidManager

Starting test: MachineAccount

.......................... mywindows2000server passed test MachineAccount

Starting test: Services

NETLOGON Service is paused on [mywindows2000server]

.......................... mywindows2000server failed test Services

Starting test: ObjectsReplicated

.......................... mywindows2000server passed test ObjectsReplicated

Starting test: frssysvol

Error: No record of File Replication System, SYSVOL started.

The Active Directory may be prevented from starting.

.......................... mywindows2000server passed test frssysvol

Starting test: kccevent

.......................... mywindows2000server passed test kccevent

Starting test: systemlog

.......................... mywindows2000server passed test systemlog

Running enterprise tests on : mydomain.com

Starting test: Intersite

.......................... mydomain.com passed test Intersite

Starting test: FsmoCheck

.......................... mydomain.com passed test FsmoCheck

C:\Documents and Settings\administrator.mydomain>

NETDIAG

C:\Documents and Settings\administrator.mydomain>netdiag

.......................................

Computer Name: mywindows2000server

DNS Host Name: mywindows2000server.mydomain.com

System info : Windows 2000 Server (Build 2195)

Processor : x86 Family 6 Model 15 Stepping 8, GenuineIntel

List of installed hotfixes :

KB329115

KB820888

KB822343

KB822831

KB823182

KB823559

KB824105

KB824141

KB824146

KB824151

KB825119

KB826232

KB828028

KB828035

KB828741

KB828749

KB832353

KB832359

KB834707-IE6SP1-20040929.091901

KB835732

KB837001

KB839643

KB839645

KB840315

KB840987

KB841356

KB841533

KB841872

KB841873

KB842526

KB842773

KB867282-IE6SP1-20050127.163319

KB871250

KB873333

KB873339

KB883935

KB883939-IE6SP1-20050428.125228

KB885250

KB885834

KB885835

KB885836

KB888113

KB889293-IE6SP1-20041111.235619

KB890046

KB890047

KB890175

KB890859

KB890923-IE6SP1-20050225.103456

KB891711

KB891781

KB893066

KB893086

KB893756

KB893803

KB893803v2

KB894320

KB896358

KB896422

KB896423

KB896424

KB896688-IE6SP1-20051004.130236

KB896727-IE6SP1-20050719.165959

KB897715-OE6SP1-20050503.210336

KB899587

KB899588

KB899589

KB899591

KB900725

KB901017

KB901214

KB902400

KB904368

KB904706

KB905414

KB905495-IE6SP1-20050805.184113

KB905749

KB905915-IE6SP1-20051122.175908

KB908519

KB908523

KB908531

KB911280

KB911564

KB911567-OE6SP1-20060316.165634

KB912812-IE6SP1-20060322.182418

KB912919

KB913580

KB914388

KB914389

KB916281-IE6SP1-20060526.162249

KB917008

KB917159

KB917422

KB917537

KB917736

KB917953

KB918118

KB918899-IE6SP1-20060725.123917

KB920213

KB920670

KB920683

KB920685

KB920958

KB921398

KB921883

KB922582

KB922616

KB923191

KB923414

KB923694-OE6SP1-20061106.120000

KB923810

KB923980

KB924191

KB924270

KB924667

KB925398_WMP64

KB925486-IE6SP1-20060918.120000

KB925902

KB926436

KB927891

KB928090-IE6SP1-20070125.120000

KB928843

KB929969-IE6SP1-20061220.120000

KB930178

KB931768-IE6SP1-20070219.120000

KB931784

KB932168

KB933729

KB935839

KB935840

KB935966

KB936021

KB937894

KB938127-IE6SP1-20070626.120000

KB938827

KB941202-OE6SP1-20070820.120000

KB941568

KB941644

KB941672

KB941693

KB942831

KB943055

KB943484

KB943485

KB944338

KB945553

KB947864-IE6SP1-20080215.120000

KB948590

KB948881-IE6SP1-20080313.120000

KB950749

Q147222

Q828026

Update Rollup 1

Netcard queries test . . . . . . . : Passed

Per interface results:

Adapter : Local Area Connection 2

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : mywindows2000server

IP Address . . . . . . . . : 192.168.29.1

Subnet Mask. . . . . . . . : 255.255.255.0

Default Gateway. . . . . . : 192.168.29.254

Dns Servers. . . . . . . . : 192.168.29.8

192.168.30.10

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed

[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge

r Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Skipped

There are no WINS servers configured for this interface.

Global results:

Domain membership test . . . . . . : Passed

NetBT transports test. . . . . . . : Passed

List of NetBt transports currently configured:

NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

1 NetBt transport currently configured.

Autonet address test . . . . . . . : Passed

IP loopback ping test. . . . . . . : Passed

Default gateway test . . . . . . . : Passed

NetBT name test. . . . . . . . . . : Passed

[WARNING] You don't have a single interface with the <00> 'WorkStation Servi

ce', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Passed

PASS - All the DNS entries for DC are registered on DNS server

'192.168.29.8' and other DCs also have some of the names registered.

PASS - All the DNS entries for DC are registered on DNS server

'192.168.30.10

' and other DCs also have some of the names registered.

Redir and Browser test . . . . . . : Passed

List of NetBt transports currently bound to the Redir

NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser

NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Passed

DC list test . . . . . . . . . . . : Failed

[WARNING] Cannot call DsBind to mywindows2003server.mydomain.com

(192.168.29.8). [sEC

_E_WRONG_PRINCIPAL]

Trust relationship test. . . . . . : Passed

Secure channel for domain 'mydomain' is to

'\\mywindows2003server.mydomain.com'.

Kerberos test. . . . . . . . . . . : Passed

LDAP test. . . . . . . . . . . . . : Passed

[WARNING] Failed to query SPN registration on DC

'mywindows2003server.mydomain.com'.

Bindings test. . . . . . . . . . . : Passed

WAN configuration test . . . . . . : Skipped

No active remote access connections.

Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed

IPSec policy service is active, but no policy is assigned.

The command completed successfully

C:\Documents and Settings\administrator.mydomain>

repadmin /shorepl

C:\Documents and Settings\administrator.mydomain>repadmin /showrepl

Usage: repadmin <cmd> <args> [/u:{domain\\user}] [/pw:{password|*}]

Supported <cmd>s & args:

/sync <Naming Context> <Dest DSA> <Source DSA UUID> [/force] [/async]

[/full] [/addref] [/allsources]

/syncall <Dest DSA> [<Naming Context>] [<flags>]

/kcc [DSA] [/async]

/bind [DSA]

/propcheck <Naming Context> <Originating DSA Invocation ID>

<Originating USN> [DSA from which to enumerate host DSAs]

/getchanges NamingContext [sourceDSA] [/cookie:<file>]

/getchanges NamingContext [DestDSA] SourceDSAObjectGuid

[/verbose] [/statistics]

/showreps [Naming Context] [DSA [source DSA objectGuid]] [/verbose]

[/unreplicated] [/nocache]

/showvector <Naming Context> [DSA] [/nocache]

/showmeta <Object DN> [DSA] [/nocache]

/showtime <DS time value>

/showmsg <Win32 error>

/showism [<Transport DN>] [/verbose] (must be executed locally)

/showsig [DSA]

/showconn [DSA] [Container DN | <DSA guid>] (default is local site)

/showcert [DSA]

/queue [DSA]

/failcache [DSA]

/showctx [DSA] [/nocache]

Note:- <Dest DSA>, <Source DSA>, <DSA> : Names of the appropriate servers

<Naming Context> is the Distinguished Name of the root of the NC

Example: DC=My-Domain,DC=Microsoft,DC=Com

C:\Documents and Settings\administrator.mydomain>

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

news:ff16fb66a420c8cab8012da08a1c@msnews.microsoft.com...

> Hello Gary,

>

> If the server is not important and only for redundancy, the easiest way is

> to demote it and promote it again. But the question is, what is the reason

> for the replication problem. Maybe it occurs again. Can you post an

> unedited ipconfig /all so that we can exclude DNS problem. Also post a

> complete dcdiag, netdiag and repadmin /showrepl.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and

> confers no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>> I have some serious issues with our windows 2000 server.

>>

>> it is a domain controller, out 2003 server is the PDC with the FSMO

>> roles.

>>

>> it appears the 2000 server is no longer able to replicate with the

>> 2003 server as per below:

>>

>> Event Type: Error

>>

>> Event Source: Userenv

>>

>> Event Category: None

>>

>> Event ID: 1000

>>

>> Date: 7/18/2008

>>

>> Time: 4:59:56 PM

>>

>> User: NT AUTHORITY\SYSTEM

>>

>> Computer: mywindows2000server

>>

>> Description:

>>

>> Windows cannot determine the user or computer name. Return value

>> (-2146893022).

>>

>> here are the results for dcdiag:

>>

>> Performing initial setup:

>>

>> Done gathering initial info.

>>

>> Doing initial required tests

>>

>> Testing server: Default-First-Site-Name\mywindows2003server

>>

>> Starting test: Connectivity

>>

>> ......................... mywindows2003server passed test

>> Connectivity

>>

>> Doing primary tests

>>

>> Testing server: Default-First-Site-Name\mywindows2003server

>>

>> Starting test: Replications

>>

>> [Replications Check,mywindows2003server] A recent replication

>> attempt failed:

>>

>> From mywindows2000server to mywindows2003server

>>

>> Naming Context:

>> CN=Schema,CN=Configuration,DC=mydomain,DC=com

>>

>> The replication generated an error (8456):

>>

>> The source server is currently rejecting replication

>> requests.

>>

>> The failure occurred at 2008-07-19 10:52:51.

>>

>> The last success occurred at 2008-05-24 07:47:13.

>>

>> 1323 failures have occurred since the last success.

>>

>> Replication has been explicitly disabled through the

>> server options.

>>

>> Active Directory doesnt work from the 2000 server, when I try to open

>> AD from the 2000 server it says:

>>

>> naming information cannot be located becasuse the target principal

>> name is not correct

>>

>> What do I need to do to fix this? If it was just another XP machine I

>> read that I could move it to a workgroup then add it back to the

>> domain to fix the event ID 1000 error, but this is a 2000 server that

>> is a domain controller.

>>

>> Would you demote it then do dcpromo?

>>

>

Posted July 21, 2008 · July 21, 2008

Re: windows cannot determine user or computer name - refers to windows 2000 server

Hello Gary,

Did you run the commands to correct replication? If not do it, either you

will get an error, or it should start.

Make sure that the 2000 DC can ping all other DC's with ip address, comuptername

and FQDN.

Check if the \\domainname\netlogon is accessible and c:\winnt\sysvol folder

exists and that you can access it to the deepest level.

Running WSUS on a DC is not the best solution. Better run it on a memeber

server. A DC should only do it basic work as AD/DNS/GC and DHCP if used.

Please post also an unedited ipconfig /all from the 2003 server. You have

also a DNS server in another subnet 192.168.30.10 ? Is that also a DC?

Also have a deeper look into this articles, because some errors are also

in your outputs:

http://support.microsoft.com/kb/839880

http://support.microsoft.com/kb/837513/en-us

Best regards

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> well, I wouldnt say it was entirley unimportant, as it is our WSUS

> server,

> and hosts the corp antivirus management software, and a few printers

> are

> shared off of it.

> but as long as the other servers are running I am okay networking

> wise.

> if demoting it and promoting it back would work I am fine with that,

> but I am willing to look at anything to resolve this.

>

> here are the results from the test you suggested (I did notice

> something about inbound replication being disabled, and simply running

> the repadmin option, it couldnt be that simple could it?)

>

> dcdiag

> DC Diagnosis

> Performing initial setup:

>

> Done gathering initial info.

>

> Doing initial non skippeable tests

>

> Testing server: Default-First-Site-Name\mywindows2000server

>

> Starting test: Connectivity

>

> ......................... mywindows2000server passed test Connectivity

>

> Doing primary tests

>

> Testing server: Default-First-Site-Name\mywindows2000server

>

> Starting test: Replications

>

> [Replications Check,mywindows2000server] Inbound replication is

> disabled.

>

> To correct, run "repadmin /options mywindows2000server

> -DISABLE_INBOUND_REPL"

>

> [Replications Check,mywindows2000server] Outbound replication is

> disabled.

>

> To correct, run "repadmin /options mywindows2000server

> -DISABLE_OUTBOUND_REPL"

>

> ......................... mywindows2000server failed test Replications

>

> Starting test: NCSecDesc

>

> ......................... mywindows2000server passed test NCSecDesc

>

> Starting test: NetLogons

>

> ......................... mywindows2000server passed test NetLogons

>

> Starting test: Advertising

>

> Warning: DsGetDcName returned information for

> \\mywindows2003server.mydomain.com,

>

> when we were trying to reach mywindows2000server.

>

> Server is not responding or is not considered suitable.

>

> [mywindows2003server] LDAP bind failed with error 31,

>

> A device attached to the system is not functioning..

>

> Server mywindows2000server is advertising as a global catalog, but

>

> it could not be verified that the server thought it was a GC.

>

> ......................... mywindows2000server failed test Advertising

>

> Starting test: KnowsOfRoleHolders

>

> [mywindows2003server] DsBind() failed with error -2146893022,

>

> The target principal name is incorrect..

>

> Warning: mywindows2003server is the Schema Owner, but is not

> responding to DS RPC

>

> Bind.

>

> Warning: mywindows2003server is the Schema Owner, but is not

> responding to LDAP B

>

> ind.

>

> Warning: mywindows2003server is the Domain Owner, but is not

> responding to DS RPC

>

> Bind.

>

> Warning: mywindows2003server is the Domain Owner, but is not

> responding to LDAP B

>

> ind.

>

> Warning: mywindows2003server is the PDC Owner, but is not responding

> to DS RPC Bi

>

> nd.

>

> Warning: mywindows2003server is the PDC Owner, but is not responding

> to LDAP Bind

>

> .

>

> Warning: mywindows2003server is the Rid Owner, but is not responding

> to DS RPC Bi

>

> nd.

>

> Warning: mywindows2003server is the Rid Owner, but is not responding

> to LDAP Bind

>

> .

>

> Warning: mywindows2003server is the Infrastructure Update Owner, but

> is not respo

>

> nding to DS RPC Bind.

>

> Warning: mywindows2003server is the Infrastructure Update Owner, but

> is not respo

>

> nding to LDAP Bind.

>

> ......................... mywindows2000server failed test

> KnowsOfRoleHolders

>

> Starting test: RidManager

>

> [mywindows2000server] DsBindWithCred() failed with error -2146893022.

> The target

>

> principal name is incorrect.

>

> ......................... mywindows2000server failed test RidManager

>

> Starting test: MachineAccount

>

> ......................... mywindows2000server passed test

> MachineAccount

>

> Starting test: Services

>

> NETLOGON Service is paused on [mywindows2000server]

>

> ......................... mywindows2000server failed test Services

>

> Starting test: ObjectsReplicated

>

> ......................... mywindows2000server passed test

> ObjectsReplicated

>

> Starting test: frssysvol

>

> Error: No record of File Replication System, SYSVOL started.

>

> The Active Directory may be prevented from starting.

>

> ......................... mywindows2000server passed test frssysvol

>

> Starting test: kccevent

>

> ......................... mywindows2000server passed test kccevent

>

> Starting test: systemlog

>

> ......................... mywindows2000server passed test systemlog

>

> Running enterprise tests on : mydomain.com

>

> Starting test: Intersite

>

> ......................... mydomain.com passed test Intersite

>

> Starting test: FsmoCheck

>

> ......................... mydomain.com passed test FsmoCheck

>

> C:\Documents and Settings\administrator.mydomain>

>

> NETDIAG

>

> C:\Documents and Settings\administrator.mydomain>netdiag

>

> ......................................

>

> Computer Name: mywindows2000server

>

> DNS Host Name: mywindows2000server.mydomain.com

>

> System info : Windows 2000 Server (Build 2195)

>

> Processor : x86 Family 6 Model 15 Stepping 8, GenuineIntel

>

> List of installed hotfixes :

>

> KB329115

>

> KB820888

>

> KB822343

>

> KB822831

>

> KB823182

>

> KB823559

>

> KB824105

>

> KB824141

>

> KB824146

>

> KB824151

>

> KB825119

>

> KB826232

>

> KB828028

>

> KB828035

>

> KB828741

>

> KB828749

>

> KB832353

>

> KB832359

>

> KB834707-IE6SP1-20040929.091901

>

> KB835732

>

> KB837001

>

> KB839643

>

> KB839645

>

> KB840315

>

> KB840987

>

> KB841356

>

> KB841533

>

> KB841872

>

> KB841873

>

> KB842526

>

> KB842773

>

> KB867282-IE6SP1-20050127.163319

>

> KB871250

>

> KB873333

>

> KB873339

>

> KB883935

>

> KB883939-IE6SP1-20050428.125228

>

> KB885250

>

> KB885834

>

> KB885835

>

> KB885836

>

> KB888113

>

> KB889293-IE6SP1-20041111.235619

>

> KB890046

>

> KB890047

>

> KB890175

>

> KB890859

>

> KB890923-IE6SP1-20050225.103456

>

> KB891711

>

> KB891781

>

> KB893066

>

> KB893086

>

> KB893756

>

> KB893803

>

> KB893803v2

>

> KB894320

>

> KB896358

>

> KB896422

>

> KB896423

>

> KB896424

>

> KB896688-IE6SP1-20051004.130236

>

> KB896727-IE6SP1-20050719.165959

>

> KB897715-OE6SP1-20050503.210336

>

> KB899587

>

> KB899588

>

> KB899589

>

> KB899591

>

> KB900725

>

> KB901017

>

> KB901214

>

> KB902400

>

> KB904368

>

> KB904706

>

> KB905414

>

> KB905495-IE6SP1-20050805.184113

>

> KB905749

>

> KB905915-IE6SP1-20051122.175908

>

> KB908519

>

> KB908523

>

> KB908531

>

> KB911280

>

> KB911564

>

> KB911567-OE6SP1-20060316.165634

>

> KB912812-IE6SP1-20060322.182418

>

> KB912919

>

> KB913580

>

> KB914388

>

> KB914389

>

> KB916281-IE6SP1-20060526.162249

>

> KB917008

>

> KB917159

>

> KB917422

>

> KB917537

>

> KB917736

>

> KB917953

>

> KB918118

>

> KB918899-IE6SP1-20060725.123917

>

> KB920213

>

> KB920670

>

> KB920683

>

> KB920685

>

> KB920958

>

> KB921398

>

> KB921883

>

> KB922582

>

> KB922616

>

> KB923191

>

> KB923414

>

> KB923694-OE6SP1-20061106.120000

>

> KB923810

>

> KB923980

>

> KB924191

>

> KB924270

>

> KB924667

>

> KB925398_WMP64

>

> KB925486-IE6SP1-20060918.120000

>

> KB925902

>

> KB926436

>

> KB927891

>

> KB928090-IE6SP1-20070125.120000

>

> KB928843

>

> KB929969-IE6SP1-20061220.120000

>

> KB930178

>

> KB931768-IE6SP1-20070219.120000

>

> KB931784

>

> KB932168

>

> KB933729

>

> KB935839

>

> KB935840

>

> KB935966

>

> KB936021

>

> KB937894

>

> KB938127-IE6SP1-20070626.120000

>

> KB938827

>

> KB941202-OE6SP1-20070820.120000

>

> KB941568

>

> KB941644

>

> KB941672

>

> KB941693

>

> KB942831

>

> KB943055

>

> KB943484

>

> KB943485

>

> KB944338

>

> KB945553

>

> KB947864-IE6SP1-20080215.120000

>

> KB948590

>

> KB948881-IE6SP1-20080313.120000

>

> KB950749

>

> Q147222

>

> Q828026

>

> Update Rollup 1

>

> Netcard queries test . . . . . . . : Passed

>

> Per interface results:

>

> Adapter : Local Area Connection 2

>

> Netcard queries test . . . : Passed

>

> Host Name. . . . . . . . . : mywindows2000server

>

> IP Address . . . . . . . . : 192.168.29.1

>

> Subnet Mask. . . . . . . . : 255.255.255.0

>

> Default Gateway. . . . . . : 192.168.29.254

>

> Dns Servers. . . . . . . . : 192.168.29.8

>

> 192.168.30.10

>

> AutoConfiguration results. . . . . . : Passed

>

> Default gateway test . . . : Passed

>

> NetBT name test. . . . . . : Passed

>

> [WARNING] At least one of the <00> 'WorkStation Service', <03>

> 'Messenge

>

> r Service', <20> 'WINS' names is missing.

>

> WINS service test. . . . . : Skipped

>

> There are no WINS servers configured for this interface.

>

> Global results:

>

> Domain membership test . . . . . . : Passed

>

> NetBT transports test. . . . . . . : Passed

>

> List of NetBt transports currently configured:

>

> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>

> 1 NetBt transport currently configured.

>

> Autonet address test . . . . . . . : Passed

>

> IP loopback ping test. . . . . . . : Passed

>

> Default gateway test . . . . . . . : Passed

>

> NetBT name test. . . . . . . . . . : Passed

>

> [WARNING] You don't have a single interface with the <00> 'WorkStation

> Servi

>

> ce', <03> 'Messenger Service', <20> 'WINS' names defined.

>

> Winsock test . . . . . . . . . . . : Passed

>

> DNS test . . . . . . . . . . . . . : Passed

>

> PASS - All the DNS entries for DC are registered on DNS server

> '192.168.29.8' and other DCs also have some of the names registered.

>

> PASS - All the DNS entries for DC are registered on DNS server

> '192.168.30.10

>

> ' and other DCs also have some of the names registered.

>

> Redir and Browser test . . . . . . : Passed

>

> List of NetBt transports currently bound to the Redir

>

> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>

> The redir is bound to 1 NetBt transport.

>

> List of NetBt transports currently bound to the browser

>

> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>

> The browser is bound to 1 NetBt transport.

>

> DC discovery test. . . . . . . . . : Passed

>

> DC list test . . . . . . . . . . . : Failed

>

> [WARNING] Cannot call DsBind to mywindows2003server.mydomain.com

> (192.168.29.8). [sEC

>

> _E_WRONG_PRINCIPAL]

>

> Trust relationship test. . . . . . : Passed

>

> Secure channel for domain 'mydomain' is to

> '\\mywindows2003server.mydomain.com'.

>

> Kerberos test. . . . . . . . . . . : Passed

>

> LDAP test. . . . . . . . . . . . . : Passed

>

> [WARNING] Failed to query SPN registration on DC

> 'mywindows2003server.mydomain.com'.

>

> Bindings test. . . . . . . . . . . : Passed

>

> WAN configuration test . . . . . . : Skipped

>

> No active remote access connections.

>

> Modem diagnostics test . . . . . . : Passed

>

> IP Security test . . . . . . . . . : Passed

>

> IPSec policy service is active, but no policy is assigned.

>

> The command completed successfully

>

> C:\Documents and Settings\administrator.mydomain>

>

> repadmin /shorepl

>

> C:\Documents and Settings\administrator.mydomain>repadmin /showrepl

>

> Usage: repadmin <cmd> <args> [/u:{domain\\user}] [/pw:{password|*}]

>

> Supported <cmd>s & args:

>

> /sync <Naming Context> <Dest DSA> <Source DSA UUID> [/force] [/async]

>

> [/full] [/addref] [/allsources]

>

> /syncall <Dest DSA> [<Naming Context>] [<flags>]

>

> /kcc [DSA] [/async]

>

> /bind [DSA]

>

> /propcheck <Naming Context> <Originating DSA Invocation ID>

>

> <Originating USN> [DSA from which to enumerate host DSAs]

>

> /getchanges NamingContext [sourceDSA] [/cookie:<file>]

>

> /getchanges NamingContext [DestDSA] SourceDSAObjectGuid

>

> [/verbose] [/statistics]

>

> /showreps [Naming Context] [DSA [source DSA objectGuid]] [/verbose]

>

> [/unreplicated] [/nocache]

>

> /showvector <Naming Context> [DSA] [/nocache]

>

> /showmeta <Object DN> [DSA] [/nocache]

>

> /showtime <DS time value>

>

> /showmsg <Win32 error>

>

> /showism [<Transport DN>] [/verbose] (must be executed locally)

>

> /showsig [DSA]

>

> /showconn [DSA] [Container DN | <DSA guid>] (default is local site)

>

> /showcert [DSA]

>

> /queue [DSA]

>

> /failcache [DSA]

>

> /showctx [DSA] [/nocache]

>

> Note:- <Dest DSA>, <Source DSA>, <DSA> : Names of the appropriate

> servers

>

> <Naming Context> is the Distinguished Name of the root of the NC

>

> Example: DC=My-Domain,DC=Microsoft,DC=Com

>

> C:\Documents and Settings\administrator.mydomain>

>

> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

> news:ff16fb66a420c8cab8012da08a1c@msnews.microsoft.com...

>

>> Hello Gary,

>>

>> If the server is not important and only for redundancy, the easiest

>> way is to demote it and promote it again. But the question is, what

>> is the reason for the replication problem. Maybe it occurs again. Can

>> you post an unedited ipconfig /all so that we can exclude DNS

>> problem. Also post a complete dcdiag, netdiag and repadmin /showrepl.

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> I have some serious issues with our windows 2000 server.

>>>

>>> it is a domain controller, out 2003 server is the PDC with the FSMO

>>> roles.

>>>

>>> it appears the 2000 server is no longer able to replicate with the

>>> 2003 server as per below:

>>>

>>> Event Type: Error

>>>

>>> Event Source: Userenv

>>>

>>> Event Category: None

>>>

>>> Event ID: 1000

>>>

>>> Date: 7/18/2008

>>>

>>> Time: 4:59:56 PM

>>>

>>> User: NT AUTHORITY\SYSTEM

>>>

>>> Computer: mywindows2000server

>>>

>>> Description:

>>>

>>> Windows cannot determine the user or computer name. Return value

>>> (-2146893022).

>>>

>>> here are the results for dcdiag:

>>>

>>> Performing initial setup:

>>>

>>> Done gathering initial info.

>>>

>>> Doing initial required tests

>>>

>>> Testing server: Default-First-Site-Name\mywindows2003server

>>>

>>> Starting test: Connectivity

>>>

>>> ......................... mywindows2003server passed test

>>> Connectivity

>>>

>>> Doing primary tests

>>>

>>> Testing server: Default-First-Site-Name\mywindows2003server

>>>

>>> Starting test: Replications

>>>

>>> [Replications Check,mywindows2003server] A recent replication

>>> attempt failed:

>>>

>>> From mywindows2000server to mywindows2003server

>>>

>>> Naming Context:

>>> CN=Schema,CN=Configuration,DC=mydomain,DC=com

>>> The replication generated an error (8456):

>>>

>>> The source server is currently rejecting replication requests.

>>>

>>> The failure occurred at 2008-07-19 10:52:51.

>>>

>>> The last success occurred at 2008-05-24 07:47:13.

>>>

>>> 1323 failures have occurred since the last success.

>>>

>>> Replication has been explicitly disabled through the server options.

>>>

>>> Active Directory doesnt work from the 2000 server, when I try to

>>> open AD from the 2000 server it says:

>>>

>>> naming information cannot be located becasuse the target principal

>>> name is not correct

>>>

>>> What do I need to do to fix this? If it was just another XP machine

>>> I read that I could move it to a workgroup then add it back to the

>>> domain to fix the event ID 1000 error, but this is a 2000 server

>>> that is a domain controller.

>>>

>>> Would you demote it then do dcpromo?

>>>

Posted July 21, 2008 · July 21, 2008

Re: windows cannot determine user or computer name - refers to windows 2000 server

thanks a lot for the tips.

I should be able to look at this today.

we have a limited number of servers, which is why WSUS is on this server.

budget thing you know.

:)

gary

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

news:ff16fb66a43378cab94bb8f8f8bb@msnews.microsoft.com...

> Hello Gary,

>

> Did you run the commands to correct replication? If not do it, either you

> will get an error, or it should start.

>

> Make sure that the 2000 DC can ping all other DC's with ip address,

> comuptername and FQDN.

>

> Check if the \\domainname\netlogon is accessible and c:\winnt\sysvol

> folder exists and that you can access it to the deepest level.

>

> Running WSUS on a DC is not the best solution. Better run it on a memeber

> server. A DC should only do it basic work as AD/DNS/GC and DHCP if used.

>

> Please post also an unedited ipconfig /all from the 2003 server. You have

> also a DNS server in another subnet 192.168.30.10 ? Is that also a DC?

>

> Also have a deeper look into this articles, because some errors are also

> in your outputs:

> http://support.microsoft.com/kb/839880

>

> http://support.microsoft.com/kb/837513/en-us

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and

> confers no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>> well, I wouldnt say it was entirley unimportant, as it is our WSUS

>> server,

>> and hosts the corp antivirus management software, and a few printers

>> are

>> shared off of it.

>> but as long as the other servers are running I am okay networking

>> wise.

>> if demoting it and promoting it back would work I am fine with that,

>> but I am willing to look at anything to resolve this.

>>

>> here are the results from the test you suggested (I did notice

>> something about inbound replication being disabled, and simply running

>> the repadmin option, it couldnt be that simple could it?)

>>

>> dcdiag

>> DC Diagnosis

>> Performing initial setup:

>>

>> Done gathering initial info.

>>

>> Doing initial non skippeable tests

>>

>> Testing server: Default-First-Site-Name\mywindows2000server

>>

>> Starting test: Connectivity

>>

>> ......................... mywindows2000server passed test Connectivity

>>

>> Doing primary tests

>>

>> Testing server: Default-First-Site-Name\mywindows2000server

>>

>> Starting test: Replications

>>

>> [Replications Check,mywindows2000server] Inbound replication is

>> disabled.

>>

>> To correct, run "repadmin /options mywindows2000server

>> -DISABLE_INBOUND_REPL"

>>

>> [Replications Check,mywindows2000server] Outbound replication is

>> disabled.

>>

>> To correct, run "repadmin /options mywindows2000server

>> -DISABLE_OUTBOUND_REPL"

>>

>> ......................... mywindows2000server failed test Replications

>>

>> Starting test: NCSecDesc

>>

>> ......................... mywindows2000server passed test NCSecDesc

>>

>> Starting test: NetLogons

>>

>> ......................... mywindows2000server passed test NetLogons

>>

>> Starting test: Advertising

>>

>> Warning: DsGetDcName returned information for

>> \\mywindows2003server.mydomain.com,

>>

>> when we were trying to reach mywindows2000server.

>>

>> Server is not responding or is not considered suitable.

>>

>> [mywindows2003server] LDAP bind failed with error 31,

>>

>> A device attached to the system is not functioning..

>>

>> Server mywindows2000server is advertising as a global catalog, but

>>

>> it could not be verified that the server thought it was a GC.

>>

>> ......................... mywindows2000server failed test Advertising

>>

>> Starting test: KnowsOfRoleHolders

>>

>> [mywindows2003server] DsBind() failed with error -2146893022,

>>

>> The target principal name is incorrect..

>>

>> Warning: mywindows2003server is the Schema Owner, but is not

>> responding to DS RPC

>>

>> Bind.

>>

>> Warning: mywindows2003server is the Schema Owner, but is not

>> responding to LDAP B

>>

>> ind.

>>

>> Warning: mywindows2003server is the Domain Owner, but is not

>> responding to DS RPC

>>

>> Bind.

>>

>> Warning: mywindows2003server is the Domain Owner, but is not

>> responding to LDAP B

>>

>> ind.

>>

>> Warning: mywindows2003server is the PDC Owner, but is not responding

>> to DS RPC Bi

>>

>> nd.

>>

>> Warning: mywindows2003server is the PDC Owner, but is not responding

>> to LDAP Bind

>>

>> .

>>

>> Warning: mywindows2003server is the Rid Owner, but is not responding

>> to DS RPC Bi

>>

>> nd.

>>

>> Warning: mywindows2003server is the Rid Owner, but is not responding

>> to LDAP Bind

>>

>> .

>>

>> Warning: mywindows2003server is the Infrastructure Update Owner, but

>> is not respo

>>

>> nding to DS RPC Bind.

>>

>> Warning: mywindows2003server is the Infrastructure Update Owner, but

>> is not respo

>>

>> nding to LDAP Bind.

>>

>> ......................... mywindows2000server failed test

>> KnowsOfRoleHolders

>>

>> Starting test: RidManager

>>

>> [mywindows2000server] DsBindWithCred() failed with error -2146893022.

>> The target

>>

>> principal name is incorrect.

>>

>> ......................... mywindows2000server failed test RidManager

>>

>> Starting test: MachineAccount

>>

>> ......................... mywindows2000server passed test

>> MachineAccount

>>

>> Starting test: Services

>>

>> NETLOGON Service is paused on [mywindows2000server]

>>

>> ......................... mywindows2000server failed test Services

>>

>> Starting test: ObjectsReplicated

>>

>> ......................... mywindows2000server passed test

>> ObjectsReplicated

>>

>> Starting test: frssysvol

>>

>> Error: No record of File Replication System, SYSVOL started.

>>

>> The Active Directory may be prevented from starting.

>>

>> ......................... mywindows2000server passed test frssysvol

>>

>> Starting test: kccevent

>>

>> ......................... mywindows2000server passed test kccevent

>>

>> Starting test: systemlog

>>

>> ......................... mywindows2000server passed test systemlog

>>

>> Running enterprise tests on : mydomain.com

>>

>> Starting test: Intersite

>>

>> ......................... mydomain.com passed test Intersite

>>

>> Starting test: FsmoCheck

>>

>> ......................... mydomain.com passed test FsmoCheck

>>

>> C:\Documents and Settings\administrator.mydomain>

>>

>> NETDIAG

>>

>> C:\Documents and Settings\administrator.mydomain>netdiag

>>

>> ......................................

>>

>> Computer Name: mywindows2000server

>>

>> DNS Host Name: mywindows2000server.mydomain.com

>>

>> System info : Windows 2000 Server (Build 2195)

>>

>> Processor : x86 Family 6 Model 15 Stepping 8, GenuineIntel

>>

>> List of installed hotfixes :

>>

>> KB329115

>>

>> KB820888

>>

>> KB822343

>>

>> KB822831

>>

>> KB823182

>>

>> KB823559

>>

>> KB824105

>>

>> KB824141

>>

>> KB824146

>>

>> KB824151

>>

>> KB825119

>>

>> KB826232

>>

>> KB828028

>>

>> KB828035

>>

>> KB828741

>>

>> KB828749

>>

>> KB832353

>>

>> KB832359

>>

>> KB834707-IE6SP1-20040929.091901

>>

>> KB835732

>>

>> KB837001

>>

>> KB839643

>>

>> KB839645

>>

>> KB840315

>>

>> KB840987

>>

>> KB841356

>>

>> KB841533

>>

>> KB841872

>>

>> KB841873

>>

>> KB842526

>>

>> KB842773

>>

>> KB867282-IE6SP1-20050127.163319

>>

>> KB871250

>>

>> KB873333

>>

>> KB873339

>>

>> KB883935

>>

>> KB883939-IE6SP1-20050428.125228

>>

>> KB885250

>>

>> KB885834

>>

>> KB885835

>>

>> KB885836

>>

>> KB888113

>>

>> KB889293-IE6SP1-20041111.235619

>>

>> KB890046

>>

>> KB890047

>>

>> KB890175

>>

>> KB890859

>>

>> KB890923-IE6SP1-20050225.103456

>>

>> KB891711

>>

>> KB891781

>>

>> KB893066

>>

>> KB893086

>>

>> KB893756

>>

>> KB893803

>>

>> KB893803v2

>>

>> KB894320

>>

>> KB896358

>>

>> KB896422

>>

>> KB896423

>>

>> KB896424

>>

>> KB896688-IE6SP1-20051004.130236

>>

>> KB896727-IE6SP1-20050719.165959

>>

>> KB897715-OE6SP1-20050503.210336

>>

>> KB899587

>>

>> KB899588

>>

>> KB899589

>>

>> KB899591

>>

>> KB900725

>>

>> KB901017

>>

>> KB901214

>>

>> KB902400

>>

>> KB904368

>>

>> KB904706

>>

>> KB905414

>>

>> KB905495-IE6SP1-20050805.184113

>>

>> KB905749

>>

>> KB905915-IE6SP1-20051122.175908

>>

>> KB908519

>>

>> KB908523

>>

>> KB908531

>>

>> KB911280

>>

>> KB911564

>>

>> KB911567-OE6SP1-20060316.165634

>>

>> KB912812-IE6SP1-20060322.182418

>>

>> KB912919

>>

>> KB913580

>>

>> KB914388

>>

>> KB914389

>>

>> KB916281-IE6SP1-20060526.162249

>>

>> KB917008

>>

>> KB917159

>>

>> KB917422

>>

>> KB917537

>>

>> KB917736

>>

>> KB917953

>>

>> KB918118

>>

>> KB918899-IE6SP1-20060725.123917

>>

>> KB920213

>>

>> KB920670

>>

>> KB920683

>>

>> KB920685

>>

>> KB920958

>>

>> KB921398

>>

>> KB921883

>>

>> KB922582

>>

>> KB922616

>>

>> KB923191

>>

>> KB923414

>>

>> KB923694-OE6SP1-20061106.120000

>>

>> KB923810

>>

>> KB923980

>>

>> KB924191

>>

>> KB924270

>>

>> KB924667

>>

>> KB925398_WMP64

>>

>> KB925486-IE6SP1-20060918.120000

>>

>> KB925902

>>

>> KB926436

>>

>> KB927891

>>

>> KB928090-IE6SP1-20070125.120000

>>

>> KB928843

>>

>> KB929969-IE6SP1-20061220.120000

>>

>> KB930178

>>

>> KB931768-IE6SP1-20070219.120000

>>

>> KB931784

>>

>> KB932168

>>

>> KB933729

>>

>> KB935839

>>

>> KB935840

>>

>> KB935966

>>

>> KB936021

>>

>> KB937894

>>

>> KB938127-IE6SP1-20070626.120000

>>

>> KB938827

>>

>> KB941202-OE6SP1-20070820.120000

>>

>> KB941568

>>

>> KB941644

>>

>> KB941672

>>

>> KB941693

>>

>> KB942831

>>

>> KB943055

>>

>> KB943484

>>

>> KB943485

>>

>> KB944338

>>

>> KB945553

>>

>> KB947864-IE6SP1-20080215.120000

>>

>> KB948590

>>

>> KB948881-IE6SP1-20080313.120000

>>

>> KB950749

>>

>> Q147222

>>

>> Q828026

>>

>> Update Rollup 1

>>

>> Netcard queries test . . . . . . . : Passed

>>

>> Per interface results:

>>

>> Adapter : Local Area Connection 2

>>

>> Netcard queries test . . . : Passed

>>

>> Host Name. . . . . . . . . : mywindows2000server

>>

>> IP Address . . . . . . . . : 192.168.29.1

>>

>> Subnet Mask. . . . . . . . : 255.255.255.0

>>

>> Default Gateway. . . . . . : 192.168.29.254

>>

>> Dns Servers. . . . . . . . : 192.168.29.8

>>

>> 192.168.30.10

>>

>> AutoConfiguration results. . . . . . : Passed

>>

>> Default gateway test . . . : Passed

>>

>> NetBT name test. . . . . . : Passed

>>

>> [WARNING] At least one of the <00> 'WorkStation Service', <03>

>> 'Messenge

>>

>> r Service', <20> 'WINS' names is missing.

>>

>> WINS service test. . . . . : Skipped

>>

>> There are no WINS servers configured for this interface.

>>

>> Global results:

>>

>> Domain membership test . . . . . . : Passed

>>

>> NetBT transports test. . . . . . . : Passed

>>

>> List of NetBt transports currently configured:

>>

>> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>>

>> 1 NetBt transport currently configured.

>>

>> Autonet address test . . . . . . . : Passed

>>

>> IP loopback ping test. . . . . . . : Passed

>>

>> Default gateway test . . . . . . . : Passed

>>

>> NetBT name test. . . . . . . . . . : Passed

>>

>> [WARNING] You don't have a single interface with the <00> 'WorkStation

>> Servi

>>

>> ce', <03> 'Messenger Service', <20> 'WINS' names defined.

>>

>> Winsock test . . . . . . . . . . . : Passed

>>

>> DNS test . . . . . . . . . . . . . : Passed

>>

>> PASS - All the DNS entries for DC are registered on DNS server

>> '192.168.29.8' and other DCs also have some of the names registered.

>>

>> PASS - All the DNS entries for DC are registered on DNS server

>> '192.168.30.10

>>

>> ' and other DCs also have some of the names registered.

>>

>> Redir and Browser test . . . . . . : Passed

>>

>> List of NetBt transports currently bound to the Redir

>>

>> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>>

>> The redir is bound to 1 NetBt transport.

>>

>> List of NetBt transports currently bound to the browser

>>

>> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>>

>> The browser is bound to 1 NetBt transport.

>>

>> DC discovery test. . . . . . . . . : Passed

>>

>> DC list test . . . . . . . . . . . : Failed

>>

>> [WARNING] Cannot call DsBind to mywindows2003server.mydomain.com

>> (192.168.29.8). [sEC

>>

>> _E_WRONG_PRINCIPAL]

>>

>> Trust relationship test. . . . . . : Passed

>>

>> Secure channel for domain 'mydomain' is to

>> '\\mywindows2003server.mydomain.com'.

>>

>> Kerberos test. . . . . . . . . . . : Passed

>>

>> LDAP test. . . . . . . . . . . . . : Passed

>>

>> [WARNING] Failed to query SPN registration on DC

>> 'mywindows2003server.mydomain.com'.

>>

>> Bindings test. . . . . . . . . . . : Passed

>>

>> WAN configuration test . . . . . . : Skipped

>>

>> No active remote access connections.

>>

>> Modem diagnostics test . . . . . . : Passed

>>

>> IP Security test . . . . . . . . . : Passed

>>

>> IPSec policy service is active, but no policy is assigned.

>>

>> The command completed successfully

>>

>> C:\Documents and Settings\administrator.mydomain>

>>

>> repadmin /shorepl

>>

>> C:\Documents and Settings\administrator.mydomain>repadmin /showrepl

>>

>> Usage: repadmin <cmd> <args> [/u:{domain\\user}] [/pw:{password|*}]

>>

>> Supported <cmd>s & args:

>>

>> /sync <Naming Context> <Dest DSA> <Source DSA UUID> [/force] [/async]

>>

>> [/full] [/addref] [/allsources]

>>

>> /syncall <Dest DSA> [<Naming Context>] [<flags>]

>>

>> /kcc [DSA] [/async]

>>

>> /bind [DSA]

>>

>> /propcheck <Naming Context> <Originating DSA Invocation ID>

>>

>> <Originating USN> [DSA from which to enumerate host DSAs]

>>

>> /getchanges NamingContext [sourceDSA] [/cookie:<file>]

>>

>> /getchanges NamingContext [DestDSA] SourceDSAObjectGuid

>>

>> [/verbose] [/statistics]

>>

>> /showreps [Naming Context] [DSA [source DSA objectGuid]] [/verbose]

>>

>> [/unreplicated] [/nocache]

>>

>> /showvector <Naming Context> [DSA] [/nocache]

>>

>> /showmeta <Object DN> [DSA] [/nocache]

>>

>> /showtime <DS time value>

>>

>> /showmsg <Win32 error>

>>

>> /showism [<Transport DN>] [/verbose] (must be executed locally)

>>

>> /showsig [DSA]

>>

>> /showconn [DSA] [Container DN | <DSA guid>] (default is local site)

>>

>> /showcert [DSA]

>>

>> /queue [DSA]

>>

>> /failcache [DSA]

>>

>> /showctx [DSA] [/nocache]

>>

>> Note:- <Dest DSA>, <Source DSA>, <DSA> : Names of the appropriate

>> servers

>>

>> <Naming Context> is the Distinguished Name of the root of the NC

>>

>> Example: DC=My-Domain,DC=Microsoft,DC=Com

>>

>> C:\Documents and Settings\administrator.mydomain>

>>

>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

>> news:ff16fb66a420c8cab8012da08a1c@msnews.microsoft.com...

>>

>>> Hello Gary,

>>>

>>> If the server is not important and only for redundancy, the easiest

>>> way is to demote it and promote it again. But the question is, what

>>> is the reason for the replication problem. Maybe it occurs again. Can

>>> you post an unedited ipconfig /all so that we can exclude DNS

>>> problem. Also post a complete dcdiag, netdiag and repadmin /showrepl.

>>>

>>> Best regards

>>>

>>> Meinolf Weber

>>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>>> confers no rights.

>>> ** Please do NOT email, only reply to Newsgroups

>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>> I have some serious issues with our windows 2000 server.

>>>>

>>>> it is a domain controller, out 2003 server is the PDC with the FSMO

>>>> roles.

>>>>

>>>> it appears the 2000 server is no longer able to replicate with the

>>>> 2003 server as per below:

>>>>

>>>> Event Type: Error

>>>>

>>>> Event Source: Userenv

>>>>

>>>> Event Category: None

>>>>

>>>> Event ID: 1000

>>>>

>>>> Date: 7/18/2008

>>>>

>>>> Time: 4:59:56 PM

>>>>

>>>> User: NT AUTHORITY\SYSTEM

>>>>

>>>> Computer: mywindows2000server

>>>>

>>>> Description:

>>>>

>>>> Windows cannot determine the user or computer name. Return value

>>>> (-2146893022).

>>>>

>>>> here are the results for dcdiag:

>>>>

>>>> Performing initial setup:

>>>>

>>>> Done gathering initial info.

>>>>

>>>> Doing initial required tests

>>>>

>>>> Testing server: Default-First-Site-Name\mywindows2003server

>>>>

>>>> Starting test: Connectivity

>>>>

>>>> ......................... mywindows2003server passed test

>>>> Connectivity

>>>>

>>>> Doing primary tests

>>>>

>>>> Testing server: Default-First-Site-Name\mywindows2003server

>>>>

>>>> Starting test: Replications

>>>>

>>>> [Replications Check,mywindows2003server] A recent replication

>>>> attempt failed:

>>>>

>>>> From mywindows2000server to mywindows2003server

>>>>

>>>> Naming Context:

>>>> CN=Schema,CN=Configuration,DC=mydomain,DC=com

>>>> The replication generated an error (8456):

>>>>

>>>> The source server is currently rejecting replication requests.

>>>>

>>>> The failure occurred at 2008-07-19 10:52:51.

>>>>

>>>> The last success occurred at 2008-05-24 07:47:13.

>>>>

>>>> 1323 failures have occurred since the last success.

>>>>

>>>> Replication has been explicitly disabled through the server options.

>>>>

>>>> Active Directory doesnt work from the 2000 server, when I try to

>>>> open AD from the 2000 server it says:

>>>>

>>>> naming information cannot be located becasuse the target principal

>>>> name is not correct

>>>>

>>>> What do I need to do to fix this? If it was just another XP machine

>>>> I read that I could move it to a workgroup then add it back to the

>>>> domain to fix the event ID 1000 error, but this is a 2000 server

>>>> that is a domain controller.

>>>>

>>>> Would you demote it then do dcpromo?

>>>>

>

Posted July 22, 2008 · July 22, 2008

Re: windows cannot determine user or computer name - refers to windows2000 server

Re: windows cannot determine user or computer name - refers to windows2000 server

Gary wrote:

> thanks a lot for the tips.

>

> I should be able to look at this today.

>

> we have a limited number of servers, which is why WSUS is on this server.

> budget thing you know.

> :)

>

> gary

>

> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

> news:ff16fb66a43378cab94bb8f8f8bb@msnews.microsoft.com...

>> Hello Gary,

>>

>> Did you run the commands to correct replication? If not do it, either you

>> will get an error, or it should start.

>>

>> Make sure that the 2000 DC can ping all other DC's with ip address,

>> comuptername and FQDN.

>>

>> Check if the \\domainname\netlogon is accessible and c:\winnt\sysvol

>> folder exists and that you can access it to the deepest level.

>>

>> Running WSUS on a DC is not the best solution. Better run it on a memeber

>> server. A DC should only do it basic work as AD/DNS/GC and DHCP if used.

>>

>> Please post also an unedited ipconfig /all from the 2003 server. You have

>> also a DNS server in another subnet 192.168.30.10 ? Is that also a DC?

>>

>> Also have a deeper look into this articles, because some errors are also

>> in your outputs:

>> http://support.microsoft.com/kb/839880

>>

>> http://support.microsoft.com/kb/837513/en-us

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>

>>> well, I wouldnt say it was entirley unimportant, as it is our WSUS

>>> server,

>>> and hosts the corp antivirus management software, and a few printers

>>> are

>>> shared off of it.

>>> but as long as the other servers are running I am okay networking

>>> wise.

>>> if demoting it and promoting it back would work I am fine with that,

>>> but I am willing to look at anything to resolve this.

>>>

>>> here are the results from the test you suggested (I did notice

>>> something about inbound replication being disabled, and simply running

>>> the repadmin option, it couldnt be that simple could it?)

>>>

>>> dcdiag

>>> DC Diagnosis

>>> Performing initial setup:

>>>

>>> Done gathering initial info.

>>>

>>> Doing initial non skippeable tests

>>>

>>> Testing server: Default-First-Site-Name\mywindows2000server

>>>

>>> Starting test: Connectivity

>>>

>>> ......................... mywindows2000server passed test Connectivity

>>>

>>> Doing primary tests

>>>

>>> Testing server: Default-First-Site-Name\mywindows2000server

>>>

>>> Starting test: Replications

>>>

>>> [Replications Check,mywindows2000server] Inbound replication is

>>> disabled.

>>>

>>> To correct, run "repadmin /options mywindows2000server

>>> -DISABLE_INBOUND_REPL"

>>>

>>> [Replications Check,mywindows2000server] Outbound replication is

>>> disabled.

>>>

>>> To correct, run "repadmin /options mywindows2000server

>>> -DISABLE_OUTBOUND_REPL"

>>>

>>> ......................... mywindows2000server failed test Replications

>>>

>>> Starting test: NCSecDesc

>>>

>>> ......................... mywindows2000server passed test NCSecDesc

>>>

>>> Starting test: NetLogons

>>>

>>> ......................... mywindows2000server passed test NetLogons

>>>

>>> Starting test: Advertising

>>>

>>> Warning: DsGetDcName returned information for

>>> \\mywindows2003server.mydomain.com,

>>>

>>> when we were trying to reach mywindows2000server.

>>>

>>> Server is not responding or is not considered suitable.

>>>

>>> [mywindows2003server] LDAP bind failed with error 31,

>>>

>>> A device attached to the system is not functioning..

>>>

>>> Server mywindows2000server is advertising as a global catalog, but

>>>

>>> it could not be verified that the server thought it was a GC.

>>>

>>> ......................... mywindows2000server failed test Advertising

>>>

>>> Starting test: KnowsOfRoleHolders

>>>

>>> [mywindows2003server] DsBind() failed with error -2146893022,

>>>

>>> The target principal name is incorrect..

>>>

>>> Warning: mywindows2003server is the Schema Owner, but is not

>>> responding to DS RPC

>>>

>>> Bind.

>>>

>>> Warning: mywindows2003server is the Schema Owner, but is not

>>> responding to LDAP B

>>>

>>> ind.

>>>

>>> Warning: mywindows2003server is the Domain Owner, but is not

>>> responding to DS RPC

>>>

>>> Bind.

>>>

>>> Warning: mywindows2003server is the Domain Owner, but is not

>>> responding to LDAP B

>>>

>>> ind.

>>>

>>> Warning: mywindows2003server is the PDC Owner, but is not responding

>>> to DS RPC Bi

>>>

>>> nd.

>>>

>>> Warning: mywindows2003server is the PDC Owner, but is not responding

>>> to LDAP Bind

>>>

>>> .

>>>

>>> Warning: mywindows2003server is the Rid Owner, but is not responding

>>> to DS RPC Bi

>>>

>>> nd.

>>>

>>> Warning: mywindows2003server is the Rid Owner, but is not responding

>>> to LDAP Bind

>>>

>>> .

>>>

>>> Warning: mywindows2003server is the Infrastructure Update Owner, but

>>> is not respo

>>>

>>> nding to DS RPC Bind.

>>>

>>> Warning: mywindows2003server is the Infrastructure Update Owner, but

>>> is not respo

>>>

>>> nding to LDAP Bind.

>>>

>>> ......................... mywindows2000server failed test

>>> KnowsOfRoleHolders

>>>

>>> Starting test: RidManager

>>>

>>> [mywindows2000server] DsBindWithCred() failed with error -2146893022.

>>> The target

>>>

>>> principal name is incorrect.

>>>

>>> ......................... mywindows2000server failed test RidManager

>>>

>>> Starting test: MachineAccount

>>>

>>> ......................... mywindows2000server passed test

>>> MachineAccount

>>>

>>> Starting test: Services

>>>

>>> NETLOGON Service is paused on [mywindows2000server]

>>>

>>> ......................... mywindows2000server failed test Services

>>>

>>> Starting test: ObjectsReplicated

>>>

>>> ......................... mywindows2000server passed test

>>> ObjectsReplicated

>>>

>>> Starting test: frssysvol

>>>

>>> Error: No record of File Replication System, SYSVOL started.

>>>

>>> The Active Directory may be prevented from starting.

>>>

>>> ......................... mywindows2000server passed test frssysvol

>>>

>>> Starting test: kccevent

>>>

>>> ......................... mywindows2000server passed test kccevent

>>>

>>> Starting test: systemlog

>>>

>>> ......................... mywindows2000server passed test systemlog

>>>

>>> Running enterprise tests on : mydomain.com

>>>

>>> Starting test: Intersite

>>>

>>> ......................... mydomain.com passed test Intersite

>>>

>>> Starting test: FsmoCheck

>>>

>>> ......................... mydomain.com passed test FsmoCheck

>>>

>>> C:\Documents and Settings\administrator.mydomain>

>>>

>>> NETDIAG

>>>

>>> C:\Documents and Settings\administrator.mydomain>netdiag

>>>

>>> ......................................

>>>

>>> Computer Name: mywindows2000server

>>>

>>> DNS Host Name: mywindows2000server.mydomain.com

>>>

>>> System info : Windows 2000 Server (Build 2195)

>>>

>>> Processor : x86 Family 6 Model 15 Stepping 8, GenuineIntel

>>>

>>> List of installed hotfixes :

>>>

>>> KB329115

>>>

>>> KB820888

>>>

>>> KB822343

>>>

>>> KB822831

>>>

>>> KB823182

>>>

>>> KB823559

>>>

>>> KB824105

>>>

>>> KB824141

>>>

>>> KB824146

>>>

>>> KB824151

>>>

>>> KB825119

>>>

>>> KB826232

>>>

>>> KB828028

>>>

>>> KB828035

>>>

>>> KB828741

>>>

>>> KB828749

>>>

>>> KB832353

>>>

>>> KB832359

>>>

>>> KB834707-IE6SP1-20040929.091901

>>>

>>> KB835732

>>>

>>> KB837001

>>>

>>> KB839643

>>>

>>> KB839645

>>>

>>> KB840315

>>>

>>> KB840987

>>>

>>> KB841356

>>>

>>> KB841533

>>>

>>> KB841872

>>>

>>> KB841873

>>>

>>> KB842526

>>>

>>> KB842773

>>>

>>> KB867282-IE6SP1-20050127.163319

>>>

>>> KB871250

>>>

>>> KB873333

>>>

>>> KB873339

>>>

>>> KB883935

>>>

>>> KB883939-IE6SP1-20050428.125228

>>>

>>> KB885250

>>>

>>> KB885834

>>>

>>> KB885835

>>>

>>> KB885836

>>>

>>> KB888113

>>>

>>> KB889293-IE6SP1-20041111.235619

>>>

>>> KB890046

>>>

>>> KB890047

>>>

>>> KB890175

>>>

>>> KB890859

>>>

>>> KB890923-IE6SP1-20050225.103456

>>>

>>> KB891711

>>>

>>> KB891781

>>>

>>> KB893066

>>>

>>> KB893086

>>>

>>> KB893756

>>>

>>> KB893803

>>>

>>> KB893803v2

>>>

>>> KB894320

>>>

>>> KB896358

>>>

>>> KB896422

>>>

>>> KB896423

>>>

>>> KB896424

>>>

>>> KB896688-IE6SP1-20051004.130236

>>>

>>> KB896727-IE6SP1-20050719.165959

>>>

>>> KB897715-OE6SP1-20050503.210336

>>>

>>> KB899587

>>>

>>> KB899588

>>>

>>> KB899589

>>>

>>> KB899591

>>>

>>> KB900725

>>>

>>> KB901017

>>>

>>> KB901214

>>>

>>> KB902400

>>>

>>> KB904368

>>>

>>> KB904706

>>>

>>> KB905414

>>>

>>> KB905495-IE6SP1-20050805.184113

>>>

>>> KB905749

>>>

>>> KB905915-IE6SP1-20051122.175908

>>>

>>> KB908519

>>>

>>> KB908523

>>>

>>> KB908531

>>>

>>> KB911280

>>>

>>> KB911564

>>>

>>> KB911567-OE6SP1-20060316.165634

>>>

>>> KB912812-IE6SP1-20060322.182418

>>>

>>> KB912919

>>>

>>> KB913580

>>>

>>> KB914388

>>>

>>> KB914389

>>>

>>> KB916281-IE6SP1-20060526.162249

>>>

>>> KB917008

>>>

>>> KB917159

>>>

>>> KB917422

>>>

>>> KB917537

>>>

>>> KB917736

>>>

>>> KB917953

>>>

>>> KB918118

>>>

>>> KB918899-IE6SP1-20060725.123917

>>>

>>> KB920213

>>>

>>> KB920670

>>>

>>> KB920683

>>>

>>> KB920685

>>>

>>> KB920958

>>>

>>> KB921398

>>>

>>> KB921883

>>>

>>> KB922582

>>>

>>> KB922616

>>>

>>> KB923191

>>>

>>> KB923414

>>>

>>> KB923694-OE6SP1-20061106.120000

>>>

>>> KB923810

>>>

>>> KB923980

>>>

>>> KB924191

>>>

>>> KB924270

>>>

>>> KB924667

>>>

>>> KB925398_WMP64

>>>

>>> KB925486-IE6SP1-20060918.120000

>>>

>>> KB925902

>>>

>>> KB926436

>>>

>>> KB927891

>>>

>>> KB928090-IE6SP1-20070125.120000

>>>

>>> KB928843

>>>

>>> KB929969-IE6SP1-20061220.120000

>>>

>>> KB930178

>>>

>>> KB931768-IE6SP1-20070219.120000

>>>

>>> KB931784

>>>

>>> KB932168

>>>

>>> KB933729

>>>

>>> KB935839

>>>

>>> KB935840

>>>

>>> KB935966

>>>

>>> KB936021

>>>

>>> KB937894

>>>

>>> KB938127-IE6SP1-20070626.120000

>>>

>>> KB938827

>>>

>>> KB941202-OE6SP1-20070820.120000

>>>

>>> KB941568

>>>

>>> KB941644

>>>

>>> KB941672

>>>

>>> KB941693

>>>

>>> KB942831

>>>

>>> KB943055

>>>

>>> KB943484

>>>

>>> KB943485

>>>

>>> KB944338

>>>

>>> KB945553

>>>

>>> KB947864-IE6SP1-20080215.120000

>>>

>>> KB948590

>>>

>>> KB948881-IE6SP1-20080313.120000

>>>

>>> KB950749

>>>

>>> Q147222

>>>

>>> Q828026

>>>

>>> Update Rollup 1

>>>

>>> Netcard queries test . . . . . . . : Passed

>>>

>>> Per interface results:

>>>

>>> Adapter : Local Area Connection 2

>>>

>>> Netcard queries test . . . : Passed

>>>

>>> Host Name. . . . . . . . . : mywindows2000server

>>>

>>> IP Address . . . . . . . . : 192.168.29.1

>>>

>>> Subnet Mask. . . . . . . . : 255.255.255.0

>>>

>>> Default Gateway. . . . . . : 192.168.29.254

>>>

>>> Dns Servers. . . . . . . . : 192.168.29.8

>>>

>>> 192.168.30.10

>>>

>>> AutoConfiguration results. . . . . . : Passed

>>>

>>> Default gateway test . . . : Passed

>>>

>>> NetBT name test. . . . . . : Passed

>>>

>>> [WARNING] At least one of the <00> 'WorkStation Service', <03>

>>> 'Messenge

>>>

>>> r Service', <20> 'WINS' names is missing.

>>>

>>> WINS service test. . . . . : Skipped

>>>

>>> There are no WINS servers configured for this interface.

>>>

>>> Global results:

>>>

>>> Domain membership test . . . . . . : Passed

>>>

>>> NetBT transports test. . . . . . . : Passed

>>>

>>> List of NetBt transports currently configured:

>>>

>>> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>>>

>>> 1 NetBt transport currently configured.

>>>

>>> Autonet address test . . . . . . . : Passed

>>>

>>> IP loopback ping test. . . . . . . : Passed

>>>

>>> Default gateway test . . . . . . . : Passed

>>>

>>> NetBT name test. . . . . . . . . . : Passed

>>>

>>> [WARNING] You don't have a single interface with the <00> 'WorkStation

>>> Servi

>>>

>>> ce', <03> 'Messenger Service', <20> 'WINS' names defined.

>>>

>>> Winsock test . . . . . . . . . . . : Passed

>>>

>>> DNS test . . . . . . . . . . . . . : Passed

>>>

>>> PASS - All the DNS entries for DC are registered on DNS server

>>> '192.168.29.8' and other DCs also have some of the names registered.

>>>

>>> PASS - All the DNS entries for DC are registered on DNS server

>>> '192.168.30.10

>>>

>>> ' and other DCs also have some of the names registered.

>>>

>>> Redir and Browser test . . . . . . : Passed

>>>

>>> List of NetBt transports currently bound to the Redir

>>>

>>> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>>>

>>> The redir is bound to 1 NetBt transport.

>>>

>>> List of NetBt transports currently bound to the browser

>>>

>>> NetBT_Tcpip_{5A8EFB1E-A853-405F-8D10-693BBBF50258}

>>>

>>> The browser is bound to 1 NetBt transport.

>>>

>>> DC discovery test. . . . . . . . . : Passed

>>>

>>> DC list test . . . . . . . . . . . : Failed

>>>

>>> [WARNING] Cannot call DsBind to mywindows2003server.mydomain.com

>>> (192.168.29.8). [sEC

>>>

>>> _E_WRONG_PRINCIPAL]

>>>

>>> Trust relationship test. . . . . . : Passed

>>>

>>> Secure channel for domain 'mydomain' is to

>>> '\\mywindows2003server.mydomain.com'.

>>>

>>> Kerberos test. . . . . . . . . . . : Passed

>>>

>>> LDAP test. . . . . . . . . . . . . : Passed

>>>

>>> [WARNING] Failed to query SPN registration on DC

>>> 'mywindows2003server.mydomain.com'.

>>>

>>> Bindings test. . . . . . . . . . . : Passed

>>>

>>> WAN configuration test . . . . . . : Skipped

>>>

>>> No active remote access connections.

>>>

>>> Modem diagnostics test . . . . . . : Passed

>>>

>>> IP Security test . . . . . . . . . : Passed

>>>

>>> IPSec policy service is active, but no policy is assigned.

>>>

>>> The command completed successfully

>>>

>>> C:\Documents and Settings\administrator.mydomain>

>>>

>>> repadmin /shorepl

>>>

>>> C:\Documents and Settings\administrator.mydomain>repadmin /showrepl

>>>

>>> Usage: repadmin <cmd> <args> [/u:{domain\\user}] [/pw:{password|*}]

>>>

>>> Supported <cmd>s & args:

>>>

>>> /sync <Naming Context> <Dest DSA> <Source DSA UUID> [/force] [/async]

>>>

>>> [/full] [/addref] [/allsources]

>>>

>>> /syncall <Dest DSA> [<Naming Context>] [<flags>]

>>>

>>> /kcc [DSA] [/async]

>>>

>>> /bind [DSA]

>>>

>>> /propcheck <Naming Context> <Originating DSA Invocation ID>

>>>

>>> <Originating USN> [DSA from which to enumerate host DSAs]

>>>

>>> /getchanges NamingContext [sourceDSA] [/cookie:<file>]

>>>

>>> /getchanges NamingContext [DestDSA] SourceDSAObjectGuid

>>>

>>> [/verbose] [/statistics]

>>>

>>> /showreps [Naming Context] [DSA [source DSA objectGuid]] [/verbose]

>>>

>>> [/unreplicated] [/nocache]

>>>

>>> /showvector <Naming Context> [DSA] [/nocache]

>>>

>>> /showmeta <Object DN> [DSA] [/nocache]

>>>

>>> /showtime <DS time value>

>>>

>>> /showmsg <Win32 error>

>>>

>>> /showism [<Transport DN>] [/verbose] (must be executed locally)

>>>

>>> /showsig [DSA]

>>>

>>> /showconn [DSA] [Container DN | <DSA guid>] (default is local site)

>>>

>>> /showcert [DSA]

>>>

>>> /queue [DSA]

>>>

>>> /failcache [DSA]

>>>

>>> /showctx [DSA] [/nocache]

>>>

>>> Note:- <Dest DSA>, <Source DSA>, <DSA> : Names of the appropriate

>>> servers

>>>

>>> <Naming Context> is the Distinguished Name of the root of the NC

>>>

>>> Example: DC=My-Domain,DC=Microsoft,DC=Com

>>>

>>> C:\Documents and Settings\administrator.mydomain>

>>>

>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

>>> news:ff16fb66a420c8cab8012da08a1c@msnews.microsoft.com...

>>>

>>>> Hello Gary,

>>>>

>>>> If the server is not important and only for redundancy, the easiest

>>>> way is to demote it and promote it again. But the question is, what

>>>> is the reason for the replication problem. Maybe it occurs again. Can

>>>> you post an unedited ipconfig /all so that we can exclude DNS

>>>> problem. Also post a complete dcdiag, netdiag and repadmin /showrepl.

>>>>

>>>> Best regards

>>>>

>>>> Meinolf Weber

>>>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>>>> confers no rights.

>>>> ** Please do NOT email, only reply to Newsgroups

>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>> I have some serious issues with our windows 2000 server.

>>>>>

>>>>> it is a domain controller, out 2003 server is the PDC with the FSMO

>>>>> roles.

>>>>>

>>>>> it appears the 2000 server is no longer able to replicate with the

>>>>> 2003 server as per below:

>>>>>

>>>>> Event Type: Error

>>>>>

>>>>> Event Source: Userenv

>>>>>

>>>>> Event Category: None

>>>>>

>>>>> Event ID: 1000

>>>>>

>>>>> Date: 7/18/2008

>>>>>

>>>>> Time: 4:59:56 PM

>>>>>

>>>>> User: NT AUTHORITY\SYSTEM

>>>>>

>>>>> Computer: mywindows2000server

>>>>>

>>>>> Description:

>>>>>

>>>>> Windows cannot determine the user or computer name. Return value

>>>>> (-2146893022).

>>>>>

>>>>> here are the results for dcdiag:

>>>>>

>>>>> Performing initial setup:

>>>>>

>>>>> Done gathering initial info.

>>>>>

>>>>> Doing initial required tests

>>>>>

>>>>> Testing server: Default-First-Site-Name\mywindows2003server

>>>>>

>>>>> Starting test: Connectivity

>>>>>

>>>>> ......................... mywindows2003server passed test

>>>>> Connectivity

>>>>>

>>>>> Doing primary tests

>>>>>

>>>>> Testing server: Default-First-Site-Name\mywindows2003server

>>>>>

>>>>> Starting test: Replications

>>>>>

>>>>> [Replications Check,mywindows2003server] A recent replication

>>>>> attempt failed:

>>>>>

>>>>> From mywindows2000server to mywindows2003server

>>>>>

>>>>> Naming Context:

>>>>> CN=Schema,CN=Configuration,DC=mydomain,DC=com

>>>>> The replication generated an error (8456):

>>>>>

>>>>> The source server is currently rejecting replication requests.

>>>>>

>>>>> The failure occurred at 2008-07-19 10:52:51.

>>>>>

>>>>> The last success occurred at 2008-05-24 07:47:13.

>>>>>

>>>>> 1323 failures have occurred since the last success.

>>>>>

>>>>> Replication has been explicitly disabled through the server options.

>>>>>

>>>>> Active Directory doesnt work from the 2000 server, when I try to

>>>>> open AD from the 2000 server it says:

>>>>>

>>>>> naming information cannot be located becasuse the target principal

>>>>> name is not correct

>>>>>

>>>>> What do I need to do to fix this? If it was just another XP machine

>>>>> I read that I could move it to a workgroup then add it back to the

>>>>> domain to fix the event ID 1000 error, but this is a 2000 server

>>>>> that is a domain controller.

>>>>>

>>>>> Would you demote it then do dcpromo?

>>>>>

>>

>

I've made the point in several ngs that a DC doesn't require lot of

resources. If it's a second DC, you could get by (until you can get

funds for a "real" server) with a decent workstation.

--

Regards,

Hank Arnold

Microsoft MVP

Windows Server - Directory Services

Posted July 31, 2008 · July 31, 2008

Re: windows cannot determine user or computer name - refers to windows 2000 server

one question:

the windows 2000 server I am demoting is a global catalog server (but not

the only one, the 2003 server is also), should I remove it from being a

global catalog server before I demote it, or does it not matter?

gary

"Anthony [MVP]" <anthony@no-reply.com> wrote in message

news:OZe4enb6IHA.3672@TK2MSFTNGP04.phx.gbl...

> Yes,

> I would demote it, and then follow the instructions carefully for adding a

> new domain controller, especially regarding DNS.

> Anthony,

> http://www.airdesk.co.uk

>

> "Gary" <garym_dontspame@hotmail.com> wrote in message

> news:OGShiXb6IHA.4596@TK2MSFTNGP03.phx.gbl...

>>

>> I have some serious issues with our windows 2000 server.

>>

>> it is a domain controller, out 2003 server is the PDC with the FSMO

>> roles.

>>

>> it appears the 2000 server is no longer able to replicate with the 2003

>> server as per below:

>>

>> Event Type: Error

>>

>> Event Source: Userenv

>>

>> Event Category: None

>>

>> Event ID: 1000

>>

>> Date: 7/18/2008

>>

>> Time: 4:59:56 PM

>>

>> User: NT AUTHORITY\SYSTEM

>>

>> Computer: mywindows2000server

>>

>> Description:

>>

>> Windows cannot determine the user or computer name. Return value

>> (-2146893022).

>>

>> here are the results for dcdiag:

>>

>> Performing initial setup:

>>

>> Done gathering initial info.

>>

>> Doing initial required tests

>>

>> Testing server: Default-First-Site-Name\mywindows2003server

>>

>> Starting test: Connectivity

>>

>> ......................... mywindows2003server passed test

>> Connectivity

>>

>> Doing primary tests

>>

>> Testing server: Default-First-Site-Name\mywindows2003server

>>

>> Starting test: Replications

>>

>> [Replications Check,mywindows2003server] A recent replication

>> attempt failed:

>>

>> From mywindows2000server to mywindows2003server

>>

>> Naming Context: CN=Schema,CN=Configuration,DC=mydomain,DC=com

>>

>> The replication generated an error (8456):

>>

>> The source server is currently rejecting replication requests.

>>

>> The failure occurred at 2008-07-19 10:52:51.

>>

>> The last success occurred at 2008-05-24 07:47:13.

>>

>> 1323 failures have occurred since the last success.

>>

>> Replication has been explicitly disabled through the server

>> options.

>>

>> Active Directory doesnt work from the 2000 server, when I try to open AD

>> from the 2000 server it says:

>>

>> naming information cannot be located becasuse the target principal name

>> is not correct

>>

>> What do I need to do to fix this? If it was just another XP machine I

>> read that I could move it to a workgroup then add it back to the domain

>> to fix the event ID 1000 error, but this is a 2000 server that is a

>> domain controller.

>>

>> Would you demote it then do dcpromo?

>>

>

Posted August 1, 2008 · August 1, 2008

Re: windows cannot determine user or computer name - refers to windows 2000 server

Hello Gary,

If you are unable to demote it, uncheck the GC and try again.

Best regards

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> one question:

> the windows 2000 server I am demoting is a global catalog server (but

> not

> the only one, the 2003 server is also), should I remove it from being

> a

> global catalog server before I demote it, or does it not matter?

> gary

>

> "Anthony [MVP]" <anthony@no-reply.com> wrote in message

> news:OZe4enb6IHA.3672@TK2MSFTNGP04.phx.gbl...

>

>> Yes,

>> I would demote it, and then follow the instructions carefully for

>> adding a

>> new domain controller, especially regarding DNS.

>> Anthony,

>> http://www.airdesk.co.uk

>> "Gary" <garym_dontspame@hotmail.com> wrote in message

>> news:OGShiXb6IHA.4596@TK2MSFTNGP03.phx.gbl...

>>

>>> I have some serious issues with our windows 2000 server.

>>>

>>> it is a domain controller, out 2003 server is the PDC with the FSMO

>>> roles.

>>>

>>> it appears the 2000 server is no longer able to replicate with the

>>> 2003 server as per below:

>>>

>>> Event Type: Error

>>>

>>> Event Source: Userenv

>>>

>>> Event Category: None

>>>

>>> Event ID: 1000

>>>

>>> Date: 7/18/2008

>>>

>>> Time: 4:59:56 PM

>>>

>>> User: NT AUTHORITY\SYSTEM

>>>

>>> Computer: mywindows2000server

>>>

>>> Description:

>>>

>>> Windows cannot determine the user or computer name. Return value

>>> (-2146893022).

>>>

>>> here are the results for dcdiag:

>>>

>>> Performing initial setup:

>>>

>>> Done gathering initial info.

>>>

>>> Doing initial required tests

>>>

>>> Testing server: Default-First-Site-Name\mywindows2003server

>>>

>>> Starting test: Connectivity

>>>

>>> ......................... mywindows2003server passed test

>>> Connectivity

>>>

>>> Doing primary tests

>>>

>>> Testing server: Default-First-Site-Name\mywindows2003server

>>>

>>> Starting test: Replications

>>>

>>> [Replications Check,mywindows2003server] A recent replication

>>> attempt failed:

>>>

>>> From mywindows2000server to mywindows2003server

>>>

>>> Naming Context: CN=Schema,CN=Configuration,DC=mydomain,DC=com

>>>

>>> The replication generated an error (8456):

>>>

>>> The source server is currently rejecting replication requests.

>>>

>>> The failure occurred at 2008-07-19 10:52:51.

>>>

>>> The last success occurred at 2008-05-24 07:47:13.

>>>

>>> 1323 failures have occurred since the last success.

>>>

>>> Replication has been explicitly disabled through the server options.

>>>

>>> Active Directory doesnt work from the 2000 server, when I try to

>>> open AD from the 2000 server it says:

>>>

>>> naming information cannot be located becasuse the target principal

>>> name is not correct

>>>

>>> What do I need to do to fix this? If it was just another XP machine

>>> I read that I could move it to a workgroup then add it back to the

>>> domain to fix the event ID 1000 error, but this is a 2000 server

>>> that is a domain controller.

>>>

>>> Would you demote it then do dcpromo?

>>>

Sign In

windows cannot determine user or computer name - refers to windows 2000 server

Recommended Posts

Guest Gary

Popular Days

Popular Days

Guest Anthony [MVP]

Guest Meinolf Weber

Guest Gary

Guest Meinolf Weber

Guest Gary

Guest Hank Arnold (MVP)

Guest Gary

Guest Meinolf Weber

Similar Content

User Reboot Server

Cannot Apply Cumulative Updates to Windows Server with SQL installed

i want buy cal user for windows server 2022

ADK and Windows 2019 Server

Scheduled Task Not Starting on Windows Server 2022 Until User Logs In

Browse

Activity

Site Info