I have the exact same issue as
http://groups.google.com/group/micro...2343b0e7075ca3

--- Extract from that posting --
We have a customer with SBS2003 and every week or so the server fails
to
accept network connections. Clients are unable to Terminal Service
into the
server, log on to the domain, map drives and open outlook. There are
no
third party applications running scans or backups at this time so I am
discounting these as the cause of the issues. I have checked the AT
scheduled tasks and there is nothing. After a reboot the server works
fine
for a number of days 6-10, or so and then it all happens again.


Below are the first errors from each event log after I believe the
server
went off line.


Application Log:
Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 12/03/2006
Time: 04:37:16
User: N/A
Computer: P1SVR


Description: LDAP Bind was unsuccessful on directory
p1svr.p1international.local for distinguished name ''. Directory
returned
error:?.34] Unavailable.


System Log:
Event Type: Error
Event Source: Application Popup
Event Category: None
Event ID: 333
Date: 12/03/2006
Time: 04:38:14
User: N/A
Computer: P1SVR


Description: An I/O operation initiated by the registry failed
unrecoverably. The registry could not read in, or write out, or flush,
one
of the files that contain the system's image of the registry.


Directory Service Log:
Event Type: Error
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1126
Date: 12/03/2006
Time: 12:24:26
User: NT Authority\system
Computer: P1SVR


Description: Active directory was unable to establish a connection with
the
global catalog.


Additional Data
Error value: 9852 No DNS servers configured for local system.
Internal ID: 3200d11
User Action: Make sure a global catalog is available in the forest, and
is
reachable from this domain controller. You may use the nltest utility
to
diagnose this problem.


DNS Server Log:
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date: 12/03/2006
Time: 03/50:38
User: N/A
Computer: P1SVR


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) us "". The event
data
contains the error.


Data:
0000: 51 00 00 00


-- End of extract --

of course the servernames are different, but the errors are the same.

I have a single SBS 2003 DC, dual homed (one NIC in direction of the
internet, the other one directed to the internal network)

DCDiag looks fine, netdiag looks fine as well. No errors there.

When using replmon to troubleshoot replication, it all returns OK's as
well. (When testing the replication and FSMO roles etc).

So I believe that AD replication works fine...

Still, everything runs fine for 6 days, then starts returning these
errors after which the server continues to accept connections for about
half a day and then dies. I've set up an automatic reboot to take place
every 6 days for the moment, but I still need to get this issue
resolved.

Any ideas on how to move forward?

Thanks!

"Xtophe" <xtophedee@gmail.com> wrote in message
news:1145018466.802988.153900@g10g2000cwb.googlegr oups.com...
Check for memory leaks.

No apparent memory leaks exist - after 5 days, there's still 2GB free
mem on the server.

Check for memory leaks in kernel-mode Non-Paged Pool by drivers. Symptoms
sound the same. These are pretty insidious because user-mode looks all fine
so you mistakenly think something is wrong with Windows.

http://blogs.msdn.com/david.wang/arc...s_Refused.aspx
For example, when IIS6 is running on such a server, it would run fine for X
days at a time and then all of a sudden stop responding to requests.
Exchange, Outlook, and Terminal Services would also stop responding, even
though the server is powered and running. A variety of bad 3rd party drivers
from popular software packages have been identified as culprits... network
card drivers, antivirus systems, backup applications, etc have all been
guilty.

3rd party apps don't have to be running at the moment of failure; they just
have to be installed and active during that time period.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Xtophe" <xtophedee@gmail.com> wrote in message
news:1145022222.101706.192600@u72g2000cwu.googlegr oups.com...