About a week or so ago, our users could not authenticate to one of our SQL 
databases.  [The SQL Database is fine and I don't think has an issue.]  I did 
not find any errors in logs.  I restarted the SQL Server services, but it did 
not correct the issue.

Checking a little further, I notice I could not see any users or computers 
or any other AD objects.  As a test, I tried to add a new user, but I could 
not.  After rebooting the server, all users and computers were again listed 
in Active Directory.  [Users could once again authenticate to the SQL 
Database.]

We haven't added a new user or computer for a couple of months.  Everything 
was working find.  I can't think of any changes which we made that affected 
AD.  There are no disk or other hardware issues.  We have plenty of hard 
drive space.

Each time we cannot see the users and computers in AD, we reboot the server 
and AD is restored.

Is AD corrupted?  Is there a utility to check AD for corruption?

Is there a KB which addresses this issue?

Was there a Microsoft Update in the past couple of weeks which could have 
affected AD?

Thank you for your help, Ed Podowski

epodowski wrote:
> About a week or so ago, our users could not authenticate to one of
> our SQL databases.  [The SQL Database is fine and I don't think has
> an issue.]  I did not find any errors in logs.  I restarted the SQL
> Server services, but it did not correct the issue.
>
> Checking a little further, I notice I could not see any users or
> computers or any other AD objects.  As a test, I tried to add a new
> user, but I could not.  After rebooting the server, all users and
> computers were again listed in Active Directory.  [Users could once
> again authenticate to the SQL Database.]
>
> We haven't added a new user or computer for a couple of months.
> Everything was working find.  I can't think of any changes which we
> made that affected AD.  There are no disk or other hardware issues.
> We have plenty of hard drive space.
>
> Each time we cannot see the users and computers in AD, we reboot the
> server and AD is restored.
>
> Is AD corrupted?  Is there a utility to check AD for corruption?
>
> Is there a KB which addresses this issue?
>
> Was there a Microsoft Update in the past couple of weeks which could
> have affected AD?
>
> Thank you for your help, Ed Podowski

My WAG would be DNS troubles. Check the event logs for directory services, 
run the SBS BPA, and when / if it happens again, try a dcdiag /c /v and post 
the results.



-- 
/kj 

kj,

That was a great WAG!

Several weeks ago we created a new top level SharePoint which resolved to 
the same IP address as the companyweb.  It was about this time we noticed 
this issue.  I am not sure if this was the problem, but as soon as we deleted 
the top level site, the problem seems to resolve itself.

Thank you very much for taking the time to answer our post.  Right now I 
think our problem is solved.

Thank you,
Ed Podowski

"kj [SBS MVP]" wrote:

> epodowski wrote:
> > About a week or so ago, our users could not authenticate to one of
> > our SQL databases.  [The SQL Database is fine and I don't think has
> > an issue.]  I did not find any errors in logs.  I restarted the SQL
> > Server services, but it did not correct the issue.
> >
> > Checking a little further, I notice I could not see any users or
> > computers or any other AD objects.  As a test, I tried to add a new
> > user, but I could not.  After rebooting the server, all users and
> > computers were again listed in Active Directory.  [Users could once
> > again authenticate to the SQL Database.]
> >
> > We haven't added a new user or computer for a couple of months.
> > Everything was working find.  I can't think of any changes which we
> > made that affected AD.  There are no disk or other hardware issues.
> > We have plenty of hard drive space.
> >
> > Each time we cannot see the users and computers in AD, we reboot the
> > server and AD is restored.
> >
> > Is AD corrupted?  Is there a utility to check AD for corruption?
> >
> > Is there a KB which addresses this issue?
> >
> > Was there a Microsoft Update in the past couple of weeks which could
> > have affected AD?
> >
> > Thank you for your help, Ed Podowski
> 
> My WAG would be DNS troubles. Check the event logs for directory services, 
> run the SBS BPA, and when / if it happens again, try a dcdiag /c /v and post 
> the results.
> 
> 
> 
> -- 
> /kj 
> 
> 
> .
> 

Not sure how the sharepoint site got in the way, but happy the "WAG"  led 
you to an apparent resolution.

epodowski wrote:
> kj,
>
> That was a great WAG!
>
> Several weeks ago we created a new top level SharePoint which
> resolved to the same IP address as the companyweb.  It was about this
> time we noticed this issue.  I am not sure if this was the problem,
> but as soon as we deleted the top level site, the problem seems to
> resolve itself.
>
> Thank you very much for taking the time to answer our post.  Right
> now I think our problem is solved.
>
> Thank you,
> Ed Podowski
>
> "kj [SBS MVP]" wrote:
>
>> epodowski wrote:
>>> About a week or so ago, our users could not authenticate to one of
>>> our SQL databases.  [The SQL Database is fine and I don't think has
>>> an issue.]  I did not find any errors in logs.  I restarted the SQL
>>> Server services, but it did not correct the issue.
>>>
>>> Checking a little further, I notice I could not see any users or
>>> computers or any other AD objects.  As a test, I tried to add a new
>>> user, but I could not.  After rebooting the server, all users and
>>> computers were again listed in Active Directory.  [Users could once
>>> again authenticate to the SQL Database.]
>>>
>>> We haven't added a new user or computer for a couple of months.
>>> Everything was working find.  I can't think of any changes which we
>>> made that affected AD.  There are no disk or other hardware issues.
>>> We have plenty of hard drive space.
>>>
>>> Each time we cannot see the users and computers in AD, we reboot the
>>> server and AD is restored.
>>>
>>> Is AD corrupted?  Is there a utility to check AD for corruption?
>>>
>>> Is there a KB which addresses this issue?
>>>
>>> Was there a Microsoft Update in the past couple of weeks which could
>>> have affected AD?
>>>
>>> Thank you for your help, Ed Podowski
>>
>> My WAG would be DNS troubles. Check the event logs for directory
>> services, run the SBS BPA, and when / if it happens again, try a
>> dcdiag /c /v and post the results.
>>
>>
>>
>> --
>> /kj
>>
>>
>> .

-- 
/kj