• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 682
  • Last Modified:

Windows Server 2003 64x becomes unresponsive but can still be pinged

I have been experiencing a random problem over the last 2 months or so.

My server is a Dell Server.  Server 2003 64x.  The server will randomly become unresponsive.  Maybe that's not the best way to put it.

The server (which provides print services) will stop responding to print requests and I won't be able to remote to it.  What's puzzling is that I can still ping the box and the users can still get to / sync their documents that are on a document redirect on that server.  

Attempts to perform a "shutdown -f -r -m \\machine_name" command from the other server in the domain results in no effect.  I end up having to do a hard restart of the machine.  Obviously this is not the best situation.

I've checked the Event Viewer and there is NOTHING that points to any system stopping errors.  I'm completely baffled on this one.  Any help from the community is much appreciated.  I'm open to anything - just don't tell me that I need to rebuild - PLEASE!!

The server is fully patched, and it has Symantec A/V running on it and is clear of all malware/adware.  I've run every scan available.  The drives aren't malfunctioning, and the memory tests within parameters.  See why I'm baffled?  I'll wait to hear from the experts.
0
pblende
Asked:
pblende
  • 3
  • 2
  • 2
  • +2
1 Solution
 
Radhakrishnan RITCommented:
First i would start from windows firewall, make sure it's stopped and disabled.
0
 
pwindellCommented:
I would say that is a "Call Microsoft" problem.

They can give you tools to monitor and test the machine that one one else can give you.  They also have troubleshooting resources and methods that no one else is going to have.
0
 
pblendeAuthor Commented:
I have the firewall disabled from the services.
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
pblendeAuthor Commented:
I will definitely keep the option open to bring Microsoft into the equation, but is there any other suggestions?  I'd like to save that as a last option.
0
 
pwindellCommented:
I understand :-)

But I don't see something obscure and untraceable like that getting a good solution here.
0
 
GlobaLevelCommented:
anyway to get someone to physically get into the box, and facto out RDC?  or try RDC with disabling the print svcs on the RDC...
0
 
Tony GiangrecoCommented:
I have the same problem with an old overloaded Windows 2003 server about twice a year wihen doing a reboot. It hangs when stopping services. I bo a cold boot and it's fine again. I think it's a hardware problem that is not trapped by the event logging.
0
 
GlobaLevelCommented:
It would definitely help if you rebooted more often, I reboot once a week! Windows OS has issues!
0
 
Tony GiangrecoCommented:
I restart all my servers 7 to 14 days on average.
0
 
pwindellCommented:
Mine go for months,..some nearly years without rebooting.  Contrary to popular belief it is not Windows that has the problems,...it is almost always flaws in the third party software running on the machines that cause Windows to have problems.

I reboot mine when Windows Updates forces me or in cases where some other maintenance causes it (which is rare on my servers).
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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