Intanto ecco qui numerosi i messaggi di errore nel log di Windows... TERRORE!!!!

------------------
Application LOG
------------------
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 24/09/2006
Time: 15.51.09
User: NT AUTHORITY\SYSTEM
Computer: NOMESERVER
Description:
Windows cannot determine the user or computer name. Return value (-2146893022).
** Questo errore viene riportato ogni 5-10 minuti **
-----------

------------------
System LOG
------------------
Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 3034
Date: 26/09/2006
Time: 11.56.04
User: N/A
Computer: NOMESERVER
Description:
The redirector was unable to initialize security context or query context attributes.
Data:
0000: 00 00 08 00 02 00 56 00 ......V.
0008: 00 00 00 00 da 0b 00 80 ......?
0010: 00 00 00 00 22 03 09 80 ...."..?
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 7d 04 00 00 22 03 09 80 }..."..?
** Questo errore viene riportato una o due volte al minuto **
------------

Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1051
Date: 26/09/2006
Time: 11.14.33
User: N/A
Computer: NOMESERVER
Description:
The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: nomedominio.
Data:
0000: 00 00 00 00 ....
** Questo messaggio viene riportato una volta ogni tanto **
-------------

Event Type: Error
Event Source: IAS
Event Category: None
Event ID: 3
Date: 26/09/2006
Time: 10.00.31
User: N/A
Computer: NOMESERVER
Description:
Access request for user nomeutentex was discarded.
Fully-Qualified-User-Name = NOMEDOMINIO\nomeutentex
NAS-IP-Address = 192.168.192.254
NAS-Identifier = <not present>
Called-Station-Identifier = <not present>
Calling-Station-Identifier = <not present>
Client-Friendly-Name = FireWall
Client-IP-Address = 192.168.192.254
NAS-Port-Type = <not present>
NAS-Port = 1621
Reason-Code = 6
Reason = The server is unavailable.
** Questo messaggio viene riportato ogni volta che qualcuno cerca di connettersi alla VPN del Router Cisco **
------------------

------------------
Directory Service LOG
------------------
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1130
Date: 26/09/2006
Time: 8.56.33
User: N/A
Computer: NOMESERVER
Description:
The automatic topology generator was unable to complete the topology for site CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=nomedominio, error code 7, and internal id f08028f.
** Questo messaggio viene riportato ogni 15 minuti **
--------------------

Event Type: Warning
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1173
Date: 25/09/2006
Time: 15.16.38
User: Everyone
Computer: NOMESERVER
Description:
Internal event: Exception e0010004 has occurred with parameters -510 and 0 (Internal ID 2020743).
** Questo messaggio veniva riportato ieri ogni 15 minuti, poi ha smesso ed è stato sostituito da quello sopra (NTDS KCC): forse è da quel momento che non fa proprio più aprire l'active directory...? **
------------------

Event Type: Information
Event Source: NTDS ISAM
Event Category: Online Defragmentation
Event ID: 700
Date: 26/09/2006
Time: 1.21.09
User: N/A
Computer: NOMESERVER
Description:
NTDS (288) Online defragmentation is beginning a full pass on database 'C:\WINNT\NTDS\ntds.dit'.
** Questo lo ha dato all'una e mezza di notte **
------------------

Event Type: Error
Event Source: NTDS ISAM
Event Category: Online Defragmentation
Event ID: 705
Date: 26/09/2006
Time: 1.21.12
User: N/A
Computer: NOMESERVER
Description:
NTDS (288) Online defragmentation of database 'C:\WINNT\NTDS\ntds.dit' terminated prematurely after encountering unexpected error -510. The next time online defragmentation is started on this database, it will resume from the point of interruption.
** E questo lo ha dato 3 secondi dopo **
-----------------

------------------
DNS Server LOG
------------------
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date: 25/09/2006
Time: 14.04.32
User: N/A
Computer: NOMESERVER
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The event data contains the error.
Data:
0000: 52 00 00 00 R...
** Questo messaggio viene registrato ogni 3-4 secondi!! **
--------------

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 3000
Date: 25/09/2006
Time: 14.04.58
User: N/A
Computer: NOMESERVER
Description:
The DNS server is logging numerous run-time events. For information about these events, see previous DNS Server event log entries. To prevent the DNS Server from clogging server logs, further logging of this event and other events with higher Event IDs will now be suppressed.
** Che bellezza! **
-----------------

Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 3150
Date: 25/09/2006
Time: 14.26.27
User: N/A
Computer: NOMESERVER
Description:
The DNS server wrote version 20 of zone nomedominio to file nomedominio.dns.
** Questo compare ogni tanto **
-----------------

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4013
Date: 25/09/2006
Time: 18.40.53
User: N/A
Computer: NOMESERVER
Description:
The DNS server was unable to open the Active Directory. This DNS server is configured to use directory service information and can not operate without access to the directory. The DNS server will wait for the directory to start. If the DNS server is started but the appropriate event has not been logged, then the DNS server is still waiting for the directory to start.
Data:
0000: e5 03 00 00 ...
------------------

------------------
File Replication Service LOG
------------------
Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13516
Date: 07/09/2006
Time: 12.02.14
User: N/A
Computer: NOMESERVER
Description:
The File Replication Service is no longer preventing the computer NOMESERVER from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
Type "net share" to check for the SYSVOL share.
** EEH??????????? !!! ?????? Questo lo scriveva ogni tanto**
------------------

Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13501
Date: 07/09/2006
Time: 12.41.35
User: N/A
Computer: NOMESERVER
Description:
The File Replication Service is starting.
-----------------

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13562
Date: 07/09/2006
Time: 12.42.03
User: N/A
Computer: NOMESERVER
Description:
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller nomeserver.nomedominio for FRS replica set configuration information.
Could not find computer object for this computer. Will try again at next polling cycle.
-------------------

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 07/09/2006
Time: 12.47.34
User: N/A
Computer: NOMESERVER
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
** Questo messaggio lo dava una decina di giorni fa **
------------

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13562
Date: 25/09/2006
Time: 16.09.10
User: N/A
Computer: NOMESERVER
Description:
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller nomeserver.nomedominio for FRS replica set configuration information.

Could not bind to a Domain Controller. Will try again at next polling cycle.
** Questo è stato l'ultimo messaggio registrato nel log "File Replication Service", risale a ieri pomeriggio. **



AAARGH! Salvatemi!!!