M
MadDog1964
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....
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....