Re: Windows server 2003 randomly failing
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Sun, 6 Jan 2008 16:36:30 -0500
In news:7DFDCD37-0AF6-455F-B4D9-6B404849273A@xxxxxxxxxxxxx,
dDan <dDan@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Thanks for your reply.
Another piece of information that may be useful is that once the
server starts failing, if I look in the Computer Management console
under Shared Folders > Sessions, the # of open files is often listed
as extremely high for all users (often thousands). If I then look in
Shared Folders > Open Files, the user only has 1 or 2 files open.
The DC is managing DNS for the domain. All clients and the server
have the DC listed as their primary DNS server. This is our only DC.
I've run dcdiag and netdiag, both of which seemed to be error-free.
Here's the output of IPCONFIG /all:
IPCONFIG
=========================================
Windows IP Configuration
Host Name . . . . . . . . . . . . : server1
Primary Dns Suffix . . . . . . . : pclnetwork.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : pclnetwork.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com Gigabit LOM (3C940)
Physical Address. . . . . . . . . : 00-0E-A6-23-3C-8E
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
=========================================
Thanks again and I look forward to any further input you might have.
The ipconfig looks pretty good. The only thing in this configuration is to
replace the loopback address with the actual DC's IP; 192.168.1.10. That got
in there because dcpromo sets it up that way. I would also suggest to create
a reverse zone for 192.168.1.x and allow updates in it. That takes care of a
few minor issues.
I assume this DC was a fresh install with a fresh brand new domain based on
the loopback being present. Or was it upgraded?
But of course that wouldn't explain the numerous sessions and the slowness.
Do you have an antivirus solution as well as an antispyware solution in
place? Have you ran a scan or ethier? Even if you have one antispyware
solution, such as Windows Defender, I would also suggest to download the
freeware version of Adaware and run a scan.
Are there any event log errors pertaining to ATAPI errors?
What type of clients are connecting? Are they 2000, XP, Vista? Any legacy
clients or Macs?
What applications are installed on this DC? Exchange? Third party apps such
as an ERP, financial apps, etc?
Run a packet capture, such as Netmon or Wireshark and look at traffic coming
to and from the server. Also run TCPView (free download) and see what ports
are open and what executables are listening. If there are any rogue apps
running that may be eating up diskspace or sessions (possibly), such as a
hijacked ftp app (servU, warFTP, etc), should show up.
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations
.
- References:
- Re: Windows server 2003 randomly failing
- From: Meinolf Weber
- Re: Windows server 2003 randomly failing
- From: dDan
- Re: Windows server 2003 randomly failing
- Prev by Date: Re: Windows server 2003 randomly failing
- Next by Date: Re: Windows server 2003 randomly failing
- Previous by thread: Re: Windows server 2003 randomly failing
- Next by thread: Re: windows/nt backup email alerting software?
- Index(es):
Relevant Pages
|