Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

DCDIAG's kccevent test fails

Hello,

We have a very simple network with a single Microsoft Small Business Server 2003, which is acting as the DC and provides DNS, DHCP, SQL Server 2005, and IIS (as well as other) services.  Our users are able to log in out of their desktop computers, but a web application that we are using will randomly fail AD authentication, even though the users can log into their workstations.  I have been investigating this issue, which seems to be related to LDAP or DNS.  When I ran DCDIAG, the kccevent test failed with the following message:
-----------------------------------------------
A Warning event occured.  EventID: 0x800004C0
Event String: Internal event: An LDAP Client connection was closed because of an error.
Client Id: 12168
Additional Data: Error Value: 995.  The I/O operation has been aborted because of either a thread exit or an application request.
-------------------------------------------------
I've cleared the Kerberos cache and have reviewed DNS configuration.  When I do an nslookup on our DC object GUID._msdcs.OURDOMAIN.org, the IP address of our DC is returned, but the non-authoritative answer is our WAN IP Address, which is used for our SBS e-mail server.  I do not know whether or not this is an issue.  I've attached images of our DNS configuration as well as the results of nslookup for your review.

I have scoured the Internet for ideas about how to correct the error that I've mentioned, but haven't found an answer for a simple, single DC situation.  I am also unsure whether the results of my nslookup are correct.  The first part seems good, but the non-authoritative answer seems strange to me.  I'd really appreciate any help.

Thanks,

Mike
nslookuptest.txt
DNSInfo.jpg
0
mjgardne
Asked:
mjgardne
  • 3
1 Solution
 
ChiefITCommented:
Multihomed can certainly be an issue:
0
 
ChiefITCommented:
It looks like you are having a problem with the SRV records of DNS. You might want to  check this out.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23356031.html
0
 
ChiefITCommented:
Mike:

I don't think you are out of the woods yet. So, I would like to stick with you.

Multihomed servers could appear to work for a couple minutes, days, weeks months or years and not seem to have a problem. As soon as NIC one is busy, and your clients revert to NIC 2 or IP2, you will have the same problems.

Can you tell me what the seocnd nic is used for? Most domains one really need one nic per server. Disabling the Second NIC and eleviating the problems associated with a muli-homed server could prevent from future problems.

0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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