Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Sun, 24 Jul 2005 23:51:25 -0400
In news:8125B88F-FFC6-45F4-AEBC-7991F28650E6@xxxxxxxxxxxxx,
Tony <Tony@xxxxxxxxxxxxxxxxxxxxxxxxx> stated, which I then commented on
below:
> ceisvr net start:
> These Windows services are started:
>
> Application Layer Gateway Service
> Automatic Updates
> Certificate Services
> COM+ Event System
> Computer Browser
> Cryptographic Services
> DHCP Client
> DHCP Server
> Distributed File System
> Distributed Transaction Coordinator
> DNS Client
> DNS Server
> Error Reporting Service
> Event Log
> File Replication Service
> Help and Support
> HP Web Jetadmin
> Indexing Service
> Intersite Messaging
> IPSEC Services
> Kerberos Key Distribution Center
> License Logging
> Logical Disk Manager
> Microsoft Search
> MSSQL$ACT7
> Net Logon
> Network Connections
> Network DDE
> Network DDE DSDM
> Network Location Awareness (NLA)
> NT LM Security Support Provider
> Plug and Play
> Print Spooler
> Protected Storage
> Remote Access Connection Manager
> Remote Procedure Call (RPC)
> Remote Registry
> Routing and Remote Access
> Secondary Logon
> Security Accounts Manager
> Server
> Shell Hardware Detection
> SNMP Service
> System Event Notification
> Task Scheduler
> TCP/IP NetBIOS Helper
> Telephony
> Terminal Services
> Windows Internet Name Service (WINS)
> Windows Management Instrumentation
> Windows Time
> Wireless Configuration
> Workstation
>
> The command completed successfully.
>
> Expedition Net Start:
> These Windows services are started:
>
> Application Experience Lookup Service
> Application Management
> Automatic Updates
> COM+ Event System
> Cryptographic Services
> DCOM Server Process Launcher
> Distributed File System
> Distributed Transaction Coordinator
> DNS Client
> DNS Server
> Error Reporting Service
> Event Log
> FTP Publishing Service
> Help and Support
> HTTP SSL
> IIS Admin Service
> Indexing Service
> Intersite Messaging
> IPSEC Services
> Kerberos Key Distribution Center
> Logical Disk Manager
> Message Queuing
> Message Queuing Triggers
> Microsoft POP3 Service
> MySQL
> Net Logon
> Network Connections
> Network Location Awareness (NLA)
> NT LM Security Support Provider
> Plug and Play
> Print Spooler
> Protected Storage
> Remote Administration Service
> Remote Procedure Call (RPC)
> Remote Registry
> Remote Server Manager
> Secondary Logon
> Security Accounts Manager
> Server
> Shell Hardware Detection
> Simple Mail Transfer Protocol (SMTP)
> Simple TCP/IP Services
> SNMP Service
> System Event Notification
> Task Scheduler
> TCP/IP NetBIOS Helper
> Terminal Services
> Web Element Manager
> WebTool
> Windows Management Instrumentation
> Windows Time
> Wireless Configuration
> Workstation
> World Wide Web Publishing Service
>
> The command completed successfully.
>
> Orion Net Start:
> These Windows 2000 services are started:
>
>
> Alerter
> Automatic Updates
> ColdFusion MX Application Server
> ColdFusion MX ODBC Agent
> ColdFusion MX ODBC Server
> COM+ Event System
> Computer Browser
> DHCP Client
> DHCP Server
> Distributed File System
> Distributed Link Tracking Client
> Distributed Link Tracking Server
> Distributed Transaction Coordinator
> DNS Client
> DNS Server
> Event Log
> File Replication Service
> Indexing Service
> Internet Authentication Service
> Intersite Messaging
> Kerberos Key Distribution Center
> License Logging Service
> Logical Disk Manager
> Machine Debug Manager
> Message Queuing
> Microsoft Search
> MSSQL$ACT7
> MSSQLSERVER
> Net Logon
> Network Connections
> NT LM Security Support Provider
> NVIDIA Driver Helper Service
> Plug and Play
> Print Spooler
> Protected Storage
> Remote Access Connection Manager
> Remote Procedure Call (RPC)
> Remote Procedure Call (RPC) Locator
> Remote Registry Service
> Removable Storage
> Routing and Remote Access
> RunAs Service
> Security Accounts Manager
> Server
> Simple TCP/IP Services
> SNMP Service
> System Event Notification
> Task Scheduler
> TCP/IP NetBIOS Helper Service
> Telephony
> Terminal Services
> WebTool
> Windows Internet Name Service (WINS)
> Windows Management Instrumentation
> Windows Management Instrumentation Driver Extensions
> Windows Time
> Workstation
>
> The command completed successfully.
>
> ndscmd /enumzones results:
> ceisvr:
> Enumerated zone list:
>
> Zone count = 4
>
> Zone name Type Storage Properties
>
> . Cache AD-Legacy
> _msdcs.compuexec.com Primary AD-Forest Secure Aging
> 50.168.192.in-addr.arpa Primary AD-Legacy Update Rev
> Aging compuexec.com Primary AD-Domain
> Secure Aging
>
> Command completed successfully.
>
>
> Orion:
> Enumerated zone list:
>
> Zone Count = 6.
>
> . 0 DS Up=0
>
> 0.in-addr.arpa 1 file Rev Auto Up=0
>
> 127.in-addr.arpa 1 file Rev Auto Up=0
>
> 255.in-addr.arpa 1 file Rev Auto Up=0
>
> 50.168.192.in-addr.arpa 1 DS Rev Up=1 Aging
>
> compuexec.com 2 file Up=0
>
> Command completed successfully.
>
>
> expedition:
> Enumerated zone list:
>
> Zone count = 4
>
> Zone name Type Storage Properties
>
> . Cache AD-Legacy
> _msdcs.compuexec.com Primary AD-Forest Secure Aging
> 50.168.192.in-addr.arpa Primary AD-Legacy Update Rev
> Aging compuexec.com Primary AD-Domain
> Secure Aging
>
> Command completed successfully.
>
> Thanks again for your (and Todd's) continued support.
>
> At this point I am extremely frustrated. Is there an easy way to just
> delete all of the DNS services and start over? Would we be able to
> recreate all the user accounts and thereby able to again access our
> local profiles at the desktop?
The DHCP Client service on Expedition is not started. I understand that
Expedition is not a DHCP client, but this services is actually a REQUIREMENT
for dynamic registration. Please turn it on.
Going thru the other services running, they seem fine.I am wondering, in
case I missed anything, did you disable any other services?
Also, what worries me is Cold Fusion on Orion:
> ColdFusion MX Application Server
> ColdFusion MX ODBC Agent
> ColdFusion MX ODBC Server
The reason, if I understand ColdFusion, is ColdFusion is an X.500 Directory
service (which is exactly what Active Directory is). If it is using it's
directory service, it also uses port 389. This can be a cause of confusion
and conflict with a domain controller. Can you look into that please?
The zone look good too. What I need to see is a list of the records under
the _msdcs folder, specifically what exactly does it show for the _msdcs.gc
records? They indicate what the GCs are for the forest.
And yes, you can delete the records and start over. Easy:
1. Delete the records in the zone (you don't have to delete the zone itself)
2. Delete the netlogon.dns and netlogon.bak files in the system32\config
folder on each DC
3. Run ipconfig /registerdns on each DC
4. Restart the netlogon service on each DC. You can do that in a CMD prompt:
net stop netlogon
net start netlogon
5. Check the zone to see if the data for each DC gets registered correctly.
Ace
Ace
.
- Follow-Ups:
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Tony
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- References:
- DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Tony
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Todd J Heron
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Tony
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Tony
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Todd J Heron
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Ace Fekay [MVP]
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Todd J Heron
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Ace Fekay [MVP]
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Tony
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Ace Fekay [MVP]
- Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- From: Tony
- DNS CORRUPT AND ALL SYSTEMS DOWN
- Prev by Date: Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- Next by Date: Re: Event ID 4016 after domain controller upgrade to Windows server 20
- Previous by thread: Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- Next by thread: Re: DNS CORRUPT AND ALL SYSTEMS DOWN
- Index(es):
Relevant Pages
|