Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 467
  • Last Modified:

Multiple errors and inability to ping after SSL install

SBS 2003. Purchased and installed an SSL Cert.  System reported it successful.  Still couldn't sync with PDA.  PDA reported invalid cert and ID's the self cert that remained from before.  
So I rebooted.  I now get multiple errors listed below.  I can no longer ping a workstation or the router or connect to the internet.   IP address, etc on the NIC seem as they have always been.

The following were from the Applications and DNS folders in Events.  The warnings did not appear immediately after the errors.  May or not be related, but I included them in case they were.

Talk to me like a 3rd grader!

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:40:55 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.Freedus.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            5/12/2011
Time:            10:40:55 PM
User:            N/A
Computer:      DELL1420
Description:
Process MAD.EXE (PID=3248). All Domain Controller Servers in use are not responding:
dell1420.Freedus.local
 

Event Type:      Information
Event Source:      ESENT
Event Category:      General
Event ID:      101
Date:            5/12/2011
Time:            10:40:56 PM
User:            N/A
Computer:      DELL1420
Description:
lsass (536) The database engine stopped.

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:01 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.Freedus.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:02 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.Freedus.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            5/12/2011
Time:            10:41:02 PM
User:            N/A
Computer:      DELL1420
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            5/12/2011
Time:            10:41:08 PM
User:            N/A
Computer:      DELL1420
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:10 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.Freedus.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:11 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.Freedus.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:12 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.Freedus.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:14 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.Freedus.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            5/12/2011
Time:            10:41:14 PM
User:            N/A
Computer:      DELL1420
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.


Event Type:      Information
Event Source:      ESENT
Event Category:      General
Event ID:      100
Date:            5/12/2011
Time:            10:43:35 PM
User:            N/A
Computer:      DELL1420
Description:
lsass (536) The database engine 5.02.3790.3959 started.


DNS

Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4015
Date:            5/12/2011
Time:            10:41:04 PM
User:            N/A
Computer:      DELL1420
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

           
Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4011
Date:            5/12/2011
Time:            10:41:04 PM
User:            N/A
Computer:      DELL1420
Description:
The DNS server was unable to add or write an update of domain name dell1420 in zone Freedus.local to the Active Directory.  Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "". The event data contains the error.



Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4011
Date:            5/12/2011
Time:            10:41:04 PM
User:            N/A
Computer:      DELL1420
Description:
The DNS server was unable to add or write an update of domain name freedus in zone Freedus.local to the Active Directory.  Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "". The event data contains the error.


Event Type:      Information
Event Source:      DNS
Event Category:      None
Event ID:      2
Date:            5/12/2011
Time:            10:44:31 PM
User:            N/A
Computer:      DELL1420
Description:
The DNS server has started.


Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      6702
Date:            5/12/2011
Time:            10:44:32 PM
User:            N/A
Computer:      DELL1420
Description:
DNS server has updated its own host (A) records.  In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update.  An error was encountered during this update, the record data is the error code.
 
If this DNS server does not have any DS-integrated peers, then this error
should be ignored.
 
If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.
 
To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact.  (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner.  It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.


0
Fritters
Asked:
Fritters
  • 3
1 Solution
 
FrittersAuthor Commented:
Additional info:  While the three items I thought were remnants of old Self Certs created in bygone days because the text "self cert" appeared in the titles, when I View Certificates in properties of each, it says that each is issued by the Commercial Cert.  
0
 
FrittersAuthor Commented:
The information in the main query is incorrect.  Some things fixed and I don't want to confuse the issue.  I am reposting.
0
 
FrittersAuthor Commented:

Multiple errors and inability to ping after SSL install
 

SBS 2003. Purchased and installed an SSL Cert.  System reported it successful.  Still couldn't sync with PDA.  PDA reported invalid cert and ID's the self cert that remained from before.  
So I rebooted.  I now get multiple errors listed below.  I can no longer ping a workstation or the router or connect to the internet.   IP address, etc on the NIC seem as they have always been.

The following were from the Applications and DNS folders in Events.  The warnings did not appear immediately after the errors.  May or not be related, but I included them in case they were.

Talk to me like a 3rd grader!

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:40:55 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.xxxxxx.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            5/12/2011
Time:            10:40:55 PM
User:            N/A
Computer:      DELL1420
Description:
Process MAD.EXE (PID=3248). All Domain Controller Servers in use are not responding:
dell1420.xxxxxx.local
 

Event Type:      Information
Event Source:      ESENT
Event Category:      General
Event ID:      101
Date:            5/12/2011
Time:            10:40:56 PM
User:            N/A
Computer:      DELL1420
Description:
lsass (536) The database engine stopped.

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:01 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.xxxxxx.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:02 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.xxxxxx.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            5/12/2011
Time:            10:41:02 PM
User:            N/A
Computer:      DELL1420
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            5/12/2011
Time:            10:41:08 PM
User:            N/A
Computer:      DELL1420
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:10 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.xxxxxx.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:11 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.xxxxxx.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:12 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.xxxxxx.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            5/12/2011
Time:            10:41:14 PM
User:            N/A
Computer:      DELL1420
Description:
LDAP Bind was unsuccessful on directory dell1420.xxxxxx.local for distinguished name ''. Directory returned error:[0x51] Server Down.    


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            5/12/2011
Time:            10:41:14 PM
User:            N/A
Computer:      DELL1420
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.


Event Type:      Information
Event Source:      ESENT
Event Category:      General
Event ID:      100
Date:            5/12/2011
Time:            10:43:35 PM
User:            N/A
Computer:      DELL1420
Description:
lsass (536) The database engine 5.02.3790.3959 started.


DNS

Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4015
Date:            5/12/2011
Time:            10:41:04 PM
User:            N/A
Computer:      DELL1420
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

           
Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4011
Date:            5/12/2011
Time:            10:41:04 PM
User:            N/A
Computer:      DELL1420
Description:
The DNS server was unable to add or write an update of domain name dell1420 in zone xxxxxx.local to the Active Directory.  Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "". The event data contains the error.



Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4011
Date:            5/12/2011
Time:            10:41:04 PM
User:            N/A
Computer:      DELL1420
Description:
The DNS server was unable to add or write an update of domain name xxxxxx in zone xxxxxx.local to the Active Directory.  Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "". The event data contains the error.


Event Type:      Information
Event Source:      DNS
Event Category:      None
Event ID:      2
Date:            5/12/2011
Time:            10:44:31 PM
User:            N/A
Computer:      DELL1420
Description:
The DNS server has started.


Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      6702
Date:            5/12/2011
Time:            10:44:32 PM
User:            N/A
Computer:      DELL1420
Description:
DNS server has updated its own host (A) records.  In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update.  An error was encountered during this update, the record data is the error code.
 
If this DNS server does not have any DS-integrated peers, then this error
should be ignored.
 
If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.
 
To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact.  (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner.  It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now