Re: Net logon error event id:3096

Hi

I ran a DCdiag in problematic Server and below is the result of the same


Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine yblrtgswip1, is a DC.
* Connecting to directory service on server yblrtgswip1.
* Collecting site info.
* Identifying all servers.
* Found 3 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\YBLRTGSWIP1
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... YBLRTGSWIP1 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\YBLRTGSWIP1
Starting test: Replications
* Replications Check
......................... YBLRTGSWIP1 passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=nds,DC=com
* Security Permissions Check for
CN=Configuration,DC=nds,DC=com
* Security Permissions Check for
DC=nds,DC=com
......................... YBLRTGSWIP1 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... YBLRTGSWIP1 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\rtgscl2.nds.com,
when we were trying to reach YBLRTGSWIP1.
Server is not responding or is not considered suitable.
The DC YBLRTGSWIP1 is advertising itself as a DC and having a DS.
The DC YBLRTGSWIP1 is advertising as an LDAP server
The DC YBLRTGSWIP1 is advertising as having a writeable directory
The DC YBLRTGSWIP1 is advertising as a Key Distribution Center
The DC YBLRTGSWIP1 is advertising as a time server
The DS YBLRTGSWIP1 is advertising as a GC.
......................... YBLRTGSWIP1 failed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=RTGSCL1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nds,DC=com
Role Domain Owner = CN=NTDS
Settings,CN=RTGSCL1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nds,DC=com
Role PDC Owner = CN=NTDS
Settings,CN=RTGSCL1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nds,DC=com
Role Rid Owner = CN=NTDS
Settings,CN=RTGSCL1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nds,DC=com
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=RTGSCL1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nds,DC=com
......................... YBLRTGSWIP1 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 4103 to 1073741823
* rtgscl1.nds.com is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 3603 to 4102
* rIDNextRID: 3603
* rIDPreviousAllocationPool is 3603 to 4102
......................... YBLRTGSWIP1 passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/yblrtgswip1.nds.com/nds.com
* SPN found :LDAP/yblrtgswip1.nds.com
* SPN found :LDAP/YBLRTGSWIP1
* SPN found :LDAP/yblrtgswip1.nds.com/NDS
* SPN found :LDAP/c41dc9e2-86f7-4c67-a04b-fd28bda62610._msdcs.nds.com
* SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/c41dc9e2-86f7-4c67-a04b-fd28bda62610/nds.com
* SPN found :HOST/yblrtgswip1.nds.com/nds.com
* SPN found :HOST/yblrtgswip1.nds.com
* SPN found :HOST/YBLRTGSWIP1
* SPN found :HOST/yblrtgswip1.nds.com/NDS
* SPN found :GC/yblrtgswip1.nds.com/nds.com
......................... YBLRTGSWIP1 passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
* Checking Service: TrkSvr
* Checking Service: NETLOGON
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... YBLRTGSWIP1 passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
YBLRTGSWIP1 is in domain DC=nds,DC=com
Checking for CN=YBLRTGSWIP1,OU=Domain Controllers,DC=nds,DC=com in
domain DC=nds,DC=com on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=YBLRTGSWIP1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nds,DC=com in domain CN=Configuration,DC=nds,DC=com on 1 servers
Object is up-to-date on all servers.
......................... YBLRTGSWIP1 passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service Event log test
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034FD
Time Generated: 12/26/2006 20:05:59
Event String: File Replication Service is initializing the

system volume with data from another domain

controller. Computer YBLRTGSWIP1 cannot become a

domain controller until this process is complete.

The system volume will then be shared as SYSVOL.



To check for the SYSVOL share, at the command

prompt, type:

net share



When File Replication Service completes the

initialization process, the SYSVOL share will

appear.



The initialization of the system volume can take

some time. The time is dependent on the amount of

data in the system volume, the availability of

other domain controllers, and the replication

interval between domain controllers.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 12/26/2006 20:07:45
Event String: The File Replication Service is having trouble

enabling replication from \\rtgscl2.nds.com to

YBLRTGSWIP1 for c:\winnt\sysvol\domain using the

DNS name \\rtgscl2.nds.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

\\rtgscl2.nds.com from this computer.

[2] FRS is not running on \\rtgscl2.nds.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.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 12/26/2006 20:15:45
Event String: The File Replication Service is having trouble

enabling replication from RTGSCL1 to YBLRTGSWIP1

for c:\winnt\sysvol\domain using the DNS name

rtgscl1.nds.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

rtgscl1.nds.com from this computer.

[2] FRS is not running on rtgscl1.nds.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.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 12/26/2006 20:15:45
Event String: The File Replication Service is having trouble

enabling replication from RTGSCL2 to YBLRTGSWIP1

for c:\winnt\sysvol\domain using the DNS name

rtgscl2.nds.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

rtgscl2.nds.com from this computer.

[2] FRS is not running on rtgscl2.nds.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.
......................... YBLRTGSWIP1 passed test frssysvol
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15
minutes.
......................... YBLRTGSWIP1 passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... YBLRTGSWIP1 passed test systemlog

Running enterprise tests on : nds.com
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope

provided by the command line arguments provided.
......................... nds.com passed test Intersite
Starting test: FsmoCheck
GC Name: \\rtgscl2.nds.com
Locator Flags: 0xe00001fc
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Time Server Name: \\rtgscl2.nds.com
Locator Flags: 0xe00001fc
Preferred Time Server Name: \\rtgscl2.nds.com
Locator Flags: 0xe00001fc
KDC Name: \\rtgscl2.nds.com
Locator Flags: 0xe00001fc
......................... nds.com failed test FsmoCheck


Pls help me i strucked very badly...

Regards
Mahesh



"myweb" wrote:

Hello myweb,

Please post also an ipconfig -all from both of your DC's.

Best regards

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



Hello Mahesh.A,

Did your services like DFS,FRS are running? Pleaser post also the
additional error ID's from Event viewer, about the Group policy.

Best regards

myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
Hi

New DC DNS is pointing to existing DC only but still i am facing
problem and also sysvol is not shared, if share this manually, gets
unshared after restart.

"myweb" wrote:

Hello Mahesh.A,

Your new DC's DNS is pointing to which DC? Let him point to the old
one to connect to the domain properly.

Best regards

myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
Hi
We have a windows 2000 Integrated DNS Domain and i have installed
new
Win2K
Server and promoted as ADC in existing Domain.During the DCPROMo it
went
smoothly and completed successfully and when i restarted Server
found
error
in system event with event id 3096,which says that unable to find
Domain
Controller for this Domain.
Observations
1)Error in System Event with event id 3096, unable to find Domain
Controller
for this Domain.
2)Sysyvol is not shared and policy/scripts are not copied to sysvol
from
root DC.
3)Domain Controller Security Policy Not opening, gives error that
failed to
open Group Policy Object,you dont have permission to open, even the
id
logged
is Administrator with Domain Admin,Schema Admin and Enterprise
Admin
Regrds
Mahesh
3)



.

Relevant Pages

  • Re: AD does not start
    ... member server ... "Directory Services Restore Mode (Windows 2000 domain controllers only)" ... Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDS Replication
    ... The replication generated an error: ... The RPC server is unavailable.. ... Starting test: CrossRefValidation ... Domain controllers that do not replicate in a timely manner may ...
    (microsoft.public.windows.server.active_directory)
  • Re: Clients (random ones) unable to login to domain, reboot, then can?
    ... replication failure, and then repromote the sever back to being a DC. ... This network has 2 domain controllers, but 1 has been out of sync for ... Remote Desktop to the server, no problems, log out, and yet STILL ... Windows boots up like normal, prompts for name, pass, domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2003 Server function level could not be raised
    ... which DNS servers the DCs point toward ... Event Source: NTDS Replication ... information from a number of domain controllers. ... This server is the owner of the following FSMO role, ...
    (microsoft.public.windows.server.setup)
  • Re: GP to force Daily Restart
    ... The Security System could not establish a secured connection with the server ldap/DC01.corp.com/corp.com@xxxxxxxxx No authentication protocol was available. ... The network path was not found. ... domain controllers log these events every five minutes. ... every computer on the network must use DNS servers that can resolve SRV ...
    (microsoft.public.windows.server.sbs)