Windows cannot determine the user or computer name

  • Thread starter Thread starter Chris Hall
  • Start date Start date
C

Chris Hall

Greetings,

I had posted previously concerning this error (Event ID:1000; Source:
Userenv) in the Active Directory forum and after trying to get this
resolved, was told to try my post here. The original post is subject:Windows
cannot determine the user or computer name; Date: 4/26/05. Below is the a
portion of the conversation...

Per Paul's suggestion, I reviewed some info from Eventid.com. Two kb
articles were mentioned: Q328691 & Q257623. I've verified there are no
viruses/trojans and the DNS suffix is correct (ipconfig /all shows the
proper suffix, which also shows up correctly in the dns zone). This server
is a DC and is replicating without a problem. I had a DNS issue recently,
but that is resolved. All srv records are in the dns zone. When I run
dcdiag, all tests pass, except I do get a strange error message during the
frs test:

Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... DC3 passed test frssysvol

Looking at the event log of this server, I have received several 13508 error
messages, the latest being on 4/27.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 3/24/2005
Time: 6:01:53 PM
User: N/A
Computer: DC3
Description:
The File Replication Service is having trouble enabling replication from DC1
to DC3 for c:\winnt\sysvol\domain using the DNS name DC1.Domain.com. FRS
will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1.Domain.com from this
computer.
[2] FRS is not running on DC1.Domain.com.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Data:
0000: 05 00 00 00 ....

I have verified my dns setup: only one dns server listed in TCP/IP
properties on all three DCs (no ISP DNS listed). And as mentioned above, the
appropriate srv & host records are recorded in the zone.

I have discovered that this error is happening on three member servers as
well and that the date when these errors were first logged are the same on
all.

Sorry for the length of the post. Very confused....
 
someone39 said:
Greetings,

I had posted previously concerning this error (Event ID:1000;
Source:
Userenv) in the Active Directory forum and after trying to get
this
resolved, was told to try my post here. The original post is
subject:Windows
cannot determine the user or computer name; Date: 4/26/05.
Below is the a
portion of the conversation...

Per Paul's suggestion, I reviewed some info from Eventid.com.
Two kb
articles were mentioned: Q328691 & Q257623. I've verified
there are no
viruses/trojans and the DNS suffix is correct (ipconfig /all
shows the
proper suffix, which also shows up correctly in the dns zone).
This server
is a DC and is replicating without a problem. I had a DNS
issue recently,
but that is resolved. All srv records are in the dns zone.
When I run
dcdiag, all tests pass, except I do get a strange error
message during the
frs test:

Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... DC3 passed test frssysvol

Looking at the event log of this server, I have received
several 13508 error
messages, the latest being on 4/27.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 3/24/2005
Time: 6:01:53 PM
User: N/A
Computer: DC3
Description:
The File Replication Service is having trouble enabling
replication from DC1
to DC3 for c:winntsysvoldomain using the DNS name
DC1.Domain.com. FRS
will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1.Domain.com
from this
computer.
[2] FRS is not running on DC1.Domain.com.
[3] The topology information in the Active Directory for this
replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After
the problem
is fixed you will see another event log message indicating
that the
connection has been established.
Data:
0000: 05 00 00 00 ....

I have verified my dns setup: only one dns server listed in
TCP/IP
properties on all three DCs (no ISP DNS listed). And as
mentioned above, the
appropriate srv & host records are recorded in the zone.

I have discovered that this error is happening on three member
servers as
well and that the date when these errors were first logged are
the same on
all.

Sorry for the length of the post. Very confused....
Click to expand...

Hi,

It seems that this is may be a Computer error rather than a DC
problem. There may be one computer in your Domain with a corrupted
computer name. Here are some MS articles you haven’t posted.

http://support.microsoft.com/default.aspx?scid=kb;en-us;329708
http://support.microsoft.com/default.aspx?scid=kb;en-us;261007
http://support.microsoft.com/default.aspx?scid=kb;en-us;810402

You didn’t mention the OS of the clients. Do you have any with a
Firewall like XP SP2 or Norton Internet Security.

Go to the DC and the DNS server and type ipconfig /flushdns. Also go
to the Reverse Lookup Zone and delete all the entries. Often I get
incorrect IP’s in the reverse zone that cause me lots of problems.

It is definitely DNS related although it may not be related to the DC.

Just to be on the safe side I would delete the DNS records and then go
to the DC’s and type ipconfig /flushdns and then ipconfig /registerdns


Cheers,

Lara
 
Lara,
Thanks for the response.

I'm confused. The errors mentioned are showing up in Event Viewer on a DC
and three member servers, not on clients....All servers are Windows 2000 and
clients are W2KPRO. We do have some 98 machines, but none that are logging
into the domain. We are not using Norton Internet Security 2002 or have any
XP boxes logging into the domain--with or without the f/w enabled. We are
using McAfee Vscan 8i, which does some cool things...port blocking,
etc...DNS settings have been confirmed. We had a previous issue with DNS,
but that has been resolved for a few weeks now and everything appears to be
fine (replication).

If there is a way to resolve this without dcpromoing my DC3, I'd certainly
rather do that. However, I do want to get this resolved....I can try
dis-joining/re-joining a member server from the domain to see if this
resolves the problem on it.

Any other suggestions?

lforbes said:
someone39 said:
Greetings,

I had posted previously concerning this error (Event ID:1000;
Source:
Userenv) in the Active Directory forum and after trying to get
this
resolved, was told to try my post here. The original post is
subject:Windows
cannot determine the user or computer name; Date: 4/26/05.
Below is the a
portion of the conversation...

Per Paul's suggestion, I reviewed some info from Eventid.com.
Two kb
articles were mentioned: Q328691 & Q257623. I've verified
there are no
viruses/trojans and the DNS suffix is correct (ipconfig /all
shows the
proper suffix, which also shows up correctly in the dns zone).
This server
is a DC and is replicating without a problem. I had a DNS
issue recently,
but that is resolved. All srv records are in the dns zone.
When I run
dcdiag, all tests pass, except I do get a strange error
message during the
frs test:

Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... DC3 passed test frssysvol

Looking at the event log of this server, I have received
several 13508 error
messages, the latest being on 4/27.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 3/24/2005
Time: 6:01:53 PM
User: N/A
Computer: DC3
Description:
The File Replication Service is having trouble enabling
replication from DC1
to DC3 for c:winntsysvoldomain using the DNS name
DC1.Domain.com. FRS
will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1.Domain.com
from this
computer.
[2] FRS is not running on DC1.Domain.com.
[3] The topology information in the Active Directory for this
replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After
the problem
is fixed you will see another event log message indicating
that the
connection has been established.
Data:
0000: 05 00 00 00 ....

I have verified my dns setup: only one dns server listed in
TCP/IP
properties on all three DCs (no ISP DNS listed). And as
mentioned above, the
appropriate srv & host records are recorded in the zone.

I have discovered that this error is happening on three member
servers as
well and that the date when these errors were first logged are
the same on
all.

Sorry for the length of the post. Very confused....
Click to expand...

Hi,

It seems that this is may be a Computer error rather than a DC
problem. There may be one computer in your Domain with a corrupted
computer name. Here are some MS articles you haven't posted.

http://support.microsoft.com/default.aspx?scid=kb;en-us;329708
http://support.microsoft.com/default.aspx?scid=kb;en-us;261007
http://support.microsoft.com/default.aspx?scid=kb;en-us;810402

You didn't mention the OS of the clients. Do you have any with a
Firewall like XP SP2 or Norton Internet Security.

Go to the DC and the DNS server and type ipconfig /flushdns. Also go
to the Reverse Lookup Zone and delete all the entries. Often I get
incorrect IP's in the reverse zone that cause me lots of problems.

It is definitely DNS related although it may not be related to the DC.

Just to be on the safe side I would delete the DNS records and then go
to the DC's and type ipconfig /flushdns and then ipconfig /registerdns


Cheers,

Lara
Click to expand...
 
Back
Top