| Home | Register | Members | Search | Windows Vista Tips | File Database | Links |
 |
| Thread Tools | Display Modes |
|
Guest
Posts: n/a
|
|
|
|
||
|
|
| |
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
"stingray" <> wrote in message
news:... > well i only did that for troubleshooting purpose, (old ip of BDC) anything > else you want me to do ? as i did that & still the netlogon service is > paused after startup, also windows time service is stopped have to restart > it manualy. > > > thanks & regards Did you go through every folder and object in DNS and make sure the additional IP address no longer shows up? You have to check both the akesp.org zone and the _msdcs.akesp.org zone. Check every entry in each zone, expanding each folder. Also check the Nameservers tab and everything else in each zone's properties to make sure the additonal IP does not exist, including the "A" records. If it does, delete it. Once that is done, run: ipconfig /all net stop netlogon net start netlogon Then restart your machine to see if it still happens. Please post any eventID# errors in any of the event logs, whether this works or not. If it continues, I am going with what Meinolf said about the USN rollback issue, because you used a snapshot. As pointed out, snapshots are NOT supported, nor do they work. It is extremely difficult if not possible, to clean up a USN rollback issue from a snapshot restoration. That's why they are not supported. That standing recommendation for a DC is to always perform full backups of the system drive (C  and a System State backup. They work nicely each andeverytime you need to restore. -- Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution. Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer For urgent issues, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers. |
|
|
|
|
|||
|
Guest
Posts: n/a
|
Ace i did all that but still ....
here are some errous event log entries. ================================================== ==== Event Type: Error Event Source: Userenv Event Category: None Event ID: 1030 Date: 12/27/2009 Time: 9:24:06 AM User: NT AUTHORITY\SYSTEM Computer: MDOMAIN Description: Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ================================================== ================ Event Type: Error Event Source: NTDS General Event Category: Service Control Event ID: 2103 Date: 12/27/2009 Time: 9:23:30 AM User: NT AUTHORITY\ANONYMOUS LOGON Computer: MDOMAIN Description: The Active Directory database has been restored using an unsupported restoration procedure. Active Directory will be unable to log on users while this condition persists. As a result, the Net Logon service has paused. User Action See previous event logs for details. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ================================================== =================== Event Type: Error Event Source: DNS Event Category: None Event ID: 4010 Date: 12/27/2009 Time: 9:23:32 AM User: N/A Computer: MDOMAIN Description: The DNS server was unable to create a resource record for 0a205198-abb0-4734-83d0-0d66ac246cd1._msdcs.akesp.org. in zone akesp.org. The Active Directory definition of this resource record is corrupt or contains an invalid DNS name. The event data contains the error. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 7b 00 00 00 {... ================================================== ======================== Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13559 Date: 12/27/2009 Time: 9:24:08 AM User: N/A Computer: MDOMAIN Description: The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path. This was detected for the following replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file. [1] At the first poll which will occur in 5 minutes this computer will be deleted from the replica set. [2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ================================================== ================================ Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7023 Date: 12/27/2009 Time: 9:24:15 AM User: N/A Computer: MDOMAIN Description: The Windows Time service terminated with the following error: An attempt was made to logon, but the network logon service was not started. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ================================================== ===================================== Thanks & regards "Ace Fekay [MCT]" <> wrote in message news:... > "stingray" <> wrote in message > news:... >> well i only did that for troubleshooting purpose, (old ip of BDC) >> anything else you want me to do ? as i did that & still the netlogon >> service is paused after startup, also windows time service is stopped >> have to restart it manualy. >> >> >> thanks & regards > > Did you go through every folder and object in DNS and make sure the > additional IP address no longer shows up? You have to check both the > akesp.org zone and the _msdcs.akesp.org zone. Check every entry in each > zone, expanding each folder. Also check the Nameservers tab and everything > else in each zone's properties to make sure the additonal IP does not > exist, including the "A" records. If it does, delete it. > > Once that is done, run: > > ipconfig /all > net stop netlogon > net start netlogon > > Then restart your machine to see if it still happens. > > Please post any eventID# errors in any of the event logs, whether this > works or not. If it continues, I am going with what Meinolf said about the > USN rollback issue, because you used a snapshot. As pointed out, snapshots > are NOT supported, nor do they work. It is extremely difficult if not > possible, to clean up a USN rollback issue from a snapshot restoration. > That's why they are not supported. > > That standing recommendation for a DC is to always perform full backups of > the system drive (C and a System State backup. They work nicely each and> everytime you need to restore. > > -- > Ace > > This posting is provided "AS-IS" with no warranties or guarantees and > confers no rights. > > Please reply back to the newsgroup or forum for collaboration benefit > among responding engineers, and to help others benefit from your > resolution. > > Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA > 2003/2000, MCSA Messaging 2003 > Microsoft Certified Trainer > > For urgent issues, please contact Microsoft PSS directly. Please check > http://support.microsoft.com for regional support phone numbers. > > > |
|
|
|
|
|||
|
Guest
Posts: n/a
|
Hello Stingray,
Adding the other DCs ip address will not help for whatever reason you thought about. As stated in Event ID: 2103 the stopped netlogon states to the unsupported way of restore. So as you have only one DC i see not a way to restore the domain. Basically adding a DC to the domain when the problem exists will not help as you copy the existing AD database with the problem to the new server. For the event id 13559 see this articles, maybe they help you: http://support.microsoft.com/kb/819268 http://support.microsoft.com/kb/887440 In my opinion the best option is to start from scratch with the domain and make a new one with 2 DC/DNS/GC as recommended for failover and redundancy. Maybe you can create a trust to anew installed domain with different domain name and use ADMT to migrate the existing accounts and computers, but as there is this critical situation i am not sure if this will work. 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 > Ace i did all that but still .... > > here are some errous event log entries. > > ================================================== ==== > Event Type: Error > Event Source: Userenv > Event Category: None > Event ID: 1030 > Date: 12/27/2009 > Time: 9:24:06 AM > User: NT AUTHORITY\SYSTEM > Computer: MDOMAIN > Description: > Windows cannot query for the list of Group Policy objects. Check the > event > log for possible messages previously logged by the policy engine that > describes the reason for this. > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > ================================================== ================ > > Event Type: Error > Event Source: NTDS General > Event Category: Service Control > Event ID: 2103 > Date: 12/27/2009 > Time: 9:23:30 AM > User: NT AUTHORITY\ANONYMOUS LOGON > Computer: MDOMAIN > Description: > The Active Directory database has been restored using an unsupported > restoration procedure. > Active Directory will be unable to log on users while this condition > persists. As a result, the Net Logon service has paused. > > User Action > See previous event logs for details. > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > ================================================== =================== > Event Type: Error > Event Source: DNS > Event Category: None > Event ID: 4010 > Date: 12/27/2009 > Time: 9:23:32 AM > User: N/A > Computer: MDOMAIN > Description: > The DNS server was unable to create a resource record for > 0a205198-abb0-4734-83d0-0d66ac246cd1._msdcs.akesp.org. in zone > akesp.org. > The Active Directory definition of this resource record is corrupt or > contains an invalid DNS name. The event data contains the error. > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > Data: > 0000: 7b 00 00 00 {... > ================================================== ==================== > ==== > > Event Type: Error > Event Source: NtFrs > Event Category: None > Event ID: 13559 > Date: 12/27/2009 > Time: 9:24:08 AM > User: N/A > Computer: MDOMAIN > Description: > The File Replication Service has detected that the replica root path > has > changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". > If > this is an intentional move then a file with the name > NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path. > This was detected for the following replica set: > "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" > Changing the replica root path is a two step process which is > triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file. > > [1] At the first poll which will occur in 5 minutes this computer > will be > deleted from the replica set. > [2] At the poll following the deletion this computer will be re-added > to > the replica set with the new root path. This re-addition will trigger > a full > tree sync for the replica set. At the end of the sync all the files > will be at the new location. The files may or may not be deleted from > the old location depending on whether they are needed or not. > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > ================================================== ==================== > ============ > > Event Type: Error > Event Source: Service Control Manager > Event Category: None > Event ID: 7023 > Date: 12/27/2009 > Time: 9:24:15 AM > User: N/A > Computer: MDOMAIN > Description: > The Windows Time service terminated with the following error: > An attempt was made to logon, but the network logon service was not > started. > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > ================================================== ==================== > ================= > > Thanks & regards > > "Ace Fekay [MCT]" <> wrote in message > news:... > >> "stingray" <> wrote in message >> news:... >> >>> well i only did that for troubleshooting purpose, (old ip of BDC) >>> anything else you want me to do ? as i did that & still the netlogon >>> service is paused after startup, also windows time service is >>> stopped have to restart it manualy. >>> >>> thanks & regards >>> >> Did you go through every folder and object in DNS and make sure the >> additional IP address no longer shows up? You have to check both the >> akesp.org zone and the _msdcs.akesp.org zone. Check every entry in >> each zone, expanding each folder. Also check the Nameservers tab and >> everything else in each zone's properties to make sure the additonal >> IP does not exist, including the "A" records. If it does, delete it. >> >> Once that is done, run: >> >> ipconfig /all >> net stop netlogon >> net start netlogon >> Then restart your machine to see if it still happens. >> >> Please post any eventID# errors in any of the event logs, whether >> this works or not. If it continues, I am going with what Meinolf said >> about the USN rollback issue, because you used a snapshot. As pointed >> out, snapshots are NOT supported, nor do they work. It is extremely >> difficult if not possible, to clean up a USN rollback issue from a >> snapshot restoration. That's why they are not supported. >> >> That standing recommendation for a DC is to always perform full >> backups of the system drive (C and a System State backup. They work>> nicely each and everytime you need to restore. >> >> -- Ace >> >> This posting is provided "AS-IS" with no warranties or guarantees and >> confers no rights. >> >> Please reply back to the newsgroup or forum for collaboration benefit >> among responding engineers, and to help others benefit from your >> resolution. >> >> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & >> MCSA >> 2003/2000, MCSA Messaging 2003 >> Microsoft Certified Trainer >> For urgent issues, please contact Microsoft PSS directly. Please >> check http://support.microsoft.com for regional support phone >> numbers. >> |
|
|
|
|
|||
|
|
| |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Name resolution order in Windows 7 | Valdas Adomaitis | DNS Server | 7 | 01-20-2010 04:18 AM |
| I also have an error 646 in Windows update. Please help. | Jose | Windows Update | 12 | 01-09-2010 02:00 PM |
| Failed to initialize WU client: 0x8007277a | Venkata Sadineni | Windows Update | 4 | 11-10-2009 07:28 PM |
| Repair DNS 4010 events... | Jake | Windows Server | 1 | 11-04-2009 11:20 AM |
| Error Message Saying: "Your system could become unstable" | SpikeDelight | Windows Vista Performance | 8 | 02-19-2008 04:20 PM |
Linear Mode
