Windows server 2003 randomly failing

  • Thread starter Thread starter dDan
  • Start date Start date
D

dDan

Guest
I've scoured the web for information on this but with no errors reported in
the event viewer I'm finding it a little difficult to know where to start.

Basically, our Windows Server 2003 server seems to randomly stop responding
correctly. By this, I mean users cant log on to the domain, access any shares
etc.

The server itself doesn't actually hang, in that I can still navigate around
Windows, however it does appear to be very unresponsive (for example, if i
click START, it might take 5 minutes or so to show up). The server and all
clients also fail when updating group policy.

Restarting the server fixes everything, but then it happens again a
seemingly random amount of time later (normally 2-3 days).

It stopped happening for a while, until a couple of days ago when the C
drive ran out of space. I've cleared 2gb of space but the random hanging has
started happening again.

Any suggestions would be very much appreciated.
 
Re: Windows server 2003 randomly failing

Sounds like a memory leak. I'd start with the app that consumed all the disk
space.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"dDan" wrote:
> I've scoured the web for information on this but with no errors reported
> in
> the event viewer I'm finding it a little difficult to know where to start.
>
> Basically, our Windows Server 2003 server seems to randomly stop
> responding
> correctly. By this, I mean users cant log on to the domain, access any
> shares
> etc.
>
> The server itself doesn't actually hang, in that I can still navigate
> around
> Windows, however it does appear to be very unresponsive (for example, if i
> click START, it might take 5 minutes or so to show up). The server and all
> clients also fail when updating group policy.
>
> Restarting the server fixes everything, but then it happens again a
> seemingly random amount of time later (normally 2-3 days).
>
> It stopped happening for a while, until a couple of days ago when the C
> drive ran out of space. I've cleared 2gb of space but the random hanging
> has
> started happening again.
>
> Any suggestions would be very much appreciated.
 
Re: Windows server 2003 randomly failing

Hello dDan,

Logon problems and also access problems to shares etc. can have a DNS problem.
So please give a short description about your DNS setup and post an unedited
ipconfig /all here.

Did you also run dcdiag and netdiag on the DC to check for errors?

Is it the only DC or do you have more then one?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

> I've scoured the web for information on this but with no errors
> reported in the event viewer I'm finding it a little difficult to know
> where to start.
>
> Basically, our Windows Server 2003 server seems to randomly stop
> responding correctly. By this, I mean users cant log on to the domain,
> access any shares etc.
>
> The server itself doesn't actually hang, in that I can still navigate
> around Windows, however it does appear to be very unresponsive (for
> example, if i click START, it might take 5 minutes or so to show up).
> The server and all clients also fail when updating group policy.
>
> Restarting the server fixes everything, but then it happens again a
> seemingly random amount of time later (normally 2-3 days).
>
> It stopped happening for a while, until a couple of days ago when the
> C drive ran out of space. I've cleared 2gb of space but the random
> hanging has started happening again.
>
> Any suggestions would be very much appreciated.
>
 
Re: Windows server 2003 randomly failing

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.

"Meinolf Weber" wrote:

> Hello dDan,
>
> Logon problems and also access problems to shares etc. can have a DNS problem.
> So please give a short description about your DNS setup and post an unedited
> ipconfig /all here.
>
> Did you also run dcdiag and netdiag on the DC to check for errors?
>
> Is it the only DC or do you have more then one?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
>
> > I've scoured the web for information on this but with no errors
> > reported in the event viewer I'm finding it a little difficult to know
> > where to start.
> >
> > Basically, our Windows Server 2003 server seems to randomly stop
> > responding correctly. By this, I mean users cant log on to the domain,
> > access any shares etc.
> >
> > The server itself doesn't actually hang, in that I can still navigate
> > around Windows, however it does appear to be very unresponsive (for
> > example, if i click START, it might take 5 minutes or so to show up).
> > The server and all clients also fail when updating group policy.
> >
> > Restarting the server fixes everything, but then it happens again a
> > seemingly random amount of time later (normally 2-3 days).
> >
> > It stopped happening for a while, until a couple of days ago when the
> > C drive ran out of space. I've cleared 2gb of space but the random
> > hanging has started happening again.
> >
> > Any suggestions would be very much appreciated.
> >

>
>
>
 
Re: Windows server 2003 randomly failing

Thanks for your reply.

In all honesty, I'm not sure what consumed all the disk space. I was away
from the machine itself and it was being very unresponsive over Remote
Desktop, so I just deleted a few unnecessary files and restarted it.

Considering the random nature of the fault a memory leak does seem likely.
Any further advice on how I could go about troubleshooting this?

Thanks again.

"Dave Patrick" wrote:

> Sounds like a memory leak. I'd start with the app that consumed all the disk
> space.
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "dDan" wrote:
> > I've scoured the web for information on this but with no errors reported
> > in
> > the event viewer I'm finding it a little difficult to know where to start.
> >
> > Basically, our Windows Server 2003 server seems to randomly stop
> > responding
> > correctly. By this, I mean users cant log on to the domain, access any
> > shares
> > etc.
> >
> > The server itself doesn't actually hang, in that I can still navigate
> > around
> > Windows, however it does appear to be very unresponsive (for example, if i
> > click START, it might take 5 minutes or so to show up). The server and all
> > clients also fail when updating group policy.
> >
> > Restarting the server fixes everything, but then it happens again a
> > seemingly random amount of time later (normally 2-3 days).
> >
> > It stopped happening for a while, until a couple of days ago when the C
> > drive ran out of space. I've cleared 2gb of space but the random hanging
> > has
> > started happening again.
> >
> > Any suggestions would be very much appreciated.

>
 
Re: Windows server 2003 randomly failing

Hello dDan,

Looks ok, only one suggestion, change the loopback ip address 127.0.0.1 to
the real ip from the DNS server. If you ever will add a second DNS server
you will get problems.

What's about the network setup, how are the machines connected (switches
etc.)? If switches are used how are they configured? Do you use the latest
NIC drivers?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

> 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
Folders>> high for
Folders>>
> 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.
>
> "Meinolf Weber" wrote:
>
>> Hello dDan,
>>
>> Logon problems and also access problems to shares etc. can have a DNS
>> problem. So please give a short description about your DNS setup and
>> post an unedited ipconfig /all here.
>>
>> Did you also run dcdiag and netdiag on the DC to check for errors?
>>
>> Is it the only DC or do you have more then one?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
>>> I've scoured the web for information on this but with no errors
>>> reported in the event viewer I'm finding it a little difficult to
>>> know where to start.
>>>
>>> Basically, our Windows Server 2003 server seems to randomly stop
>>> responding correctly. By this, I mean users cant log on to the
>>> domain, access any shares etc.
>>>
>>> The server itself doesn't actually hang, in that I can still
>>> navigate around Windows, however it does appear to be very
>>> unresponsive (for example, if i click START, it might take 5 minutes
>>> or so to show up). The server and all clients also fail when
>>> updating group policy.
>>>
>>> Restarting the server fixes everything, but then it happens again a
>>> seemingly random amount of time later (normally 2-3 days).
>>>
>>> It stopped happening for a while, until a couple of days ago when
>>> the C drive ran out of space. I've cleared 2gb of space but the
>>> random hanging has started happening again.
>>>
>>> Any suggestions would be very much appreciated.
>>>
 
Re: Windows server 2003 randomly failing

In news:7DFDCD37-0AF6-455F-B4D9-6B404849273A@microsoft.com,
dDan <dDan@discussions.microsoft.com> 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
 
Re: Windows server 2003 randomly failing

Well this sounds suspicious or maybe the windows partition is too small in
the first place? If there was no room for the page file then this may make
some sense.

A snapshot of the Task Manager|Processes tab just after startup for later
comparison may help.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"dDan" wrote:
> Thanks for your reply.
>
> In all honesty, I'm not sure what consumed all the disk space. I was away
> from the machine itself and it was being very unresponsive over Remote
> Desktop, so I just deleted a few unnecessary files and restarted it.
>
> Considering the random nature of the fault a memory leak does seem likely.
> Any further advice on how I could go about troubleshooting this?
>
> Thanks again.
 
Re: Windows server 2003 randomly failing

Well this sounds suspicious or maybe the windows partition is too small in
the first place? If there was no room for the page file then this may make
some sense.

A snapshot of the Task Manager|Processes tab just after startup for later
comparison may help.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
Microsoft Security At Home - Help Prevent Identity Theft, Spyware & Viruses

"dDan" wrote:
> Thanks for your reply.
>
> In all honesty, I'm not sure what consumed all the disk space. I was away
> from the machine itself and it was being very unresponsive over Remote
> Desktop, so I just deleted a few unnecessary files and restarted it.
>
> Considering the random nature of the fault a memory leak does seem likely.
> Any further advice on how I could go about troubleshooting this?
>
> Thanks again.
We are having almost the exact same issue. We currently have 2 Domain Controllers Running Windows server 2003 and a Storage server running Windows Server 2003. Just last week Our Art Deparment which runs on MAC OSX 10.4 systems were reporting disconnections to the shares on our storage server. Shortly after this happend, the shares locked up for all users accross the company, so for our windows users as well. During this time if we checked the Session Log for the Shares Under Computer management, it would show the Apple OSX Computers had Thousands of Files open Under the "Open files" column.


So for us, it appears only the Mac OSX computers will show a incorrect amount of Open Files. Dont know if your company Is having this problem with Windows Comptuers and Mac?
We are at a lost as well. we are awaiting on information back from microsoft for any suggestions. We already have double, tripple checked all network settings as well as upgraded the NIC Drivers on the Storage Server. Two Theories we have, is it could have somthing to do with netbios and the Macs, or Windows Server thinking there is a Denial of service attack, so it shuts down the shares (From reccording all of the thousands of open files) but this still doesnt explain Why certain systems show The Large Open File Amount. That is the key to finding the problem...
 
RE: Windows server 2003 randomly failing

Thanks to everyone who replied to this topic, and apologies if I didn't
respond to any posts. All suggestions were gratefully received.

To update; this issue seems to have been fixed by disabling Shadow Copies.

"dDan" wrote:

> I've scoured the web for information on this but with no errors reported in
> the event viewer I'm finding it a little difficult to know where to start.
>
> Basically, our Windows Server 2003 server seems to randomly stop responding
> correctly. By this, I mean users cant log on to the domain, access any shares
> etc.
>
> The server itself doesn't actually hang, in that I can still navigate around
> Windows, however it does appear to be very unresponsive (for example, if i
> click START, it might take 5 minutes or so to show up). The server and all
> clients also fail when updating group policy.
>
> Restarting the server fixes everything, but then it happens again a
> seemingly random amount of time later (normally 2-3 days).
>
> It stopped happening for a while, until a couple of days ago when the C
> drive ran out of space. I've cleared 2gb of space but the random hanging has
> started happening again.
>
> Any suggestions would be very much appreciated.
 
Re: Windows server 2003 randomly failing

In news:6A9AB2F0-9104-4DBB-BB2F-D88E7C6E382E@microsoft.com,
dDan <dDan@discussions.microsoft.com> typed:
> Thanks to everyone who replied to this topic, and apologies if I
> didn't respond to any posts. All suggestions were gratefully received.
>
> To update; this issue seems to have been fixed by disabling Shadow
> Copies.
>


Thanks for the update. Unusual to find that Shadow copies did this, but I am
happy you have resolved the issue.

Ace
 
Back
Top