Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 269
  • Last Modified:

Network connectivity dropping off momentarily when accessing server shares/programs.

Hi Experts!

I've got a Windows 2003 Server that we just did work on that's acting up.

The work performed was the server had a RAID1 and one of the drives was failed, and the other one was one it's way out.  So, I used Acronis software to clone the one good failing drive to a new RAID 1 array.  Which worked fine.

However, after doing that, whenever the network shares are accessed in a "stressed" manner (copying files, etc).  (It's infrequently triggered by just viewing the shares.)  Or, when we run a server based application that accesses data from the server, the server network connection STOPS for a brief period of time.  If I'm running "ping -t" to/from the server, it stops for about 2-3 failures of the ping and then starts back up.  I've replaced the switch, the cable, and the NIC in the server to no effect.

The problem didn't exist before I cloned the server.  I've ran a chkdsk and a defrag.

Unsure of what else to check.  Any help would be much appreciated.

Thanks!
0
tganus
Asked:
tganus
  • 2
  • 2
1 Solution
 
Tony GiangrecoCommented:
It sounds like the load placed on your server while accessing shares is taking a high amount of resources which cuts out access to other resources like access the web. Open task manager and keep the performance tab open while accessing a network share.

See if the server response time takes a hit. I suspect it will go high and possibly spike at 80% or higher.
0
 
btdownloads7Commented:
I think that it has to do with your original failing drives. It's very possible that some data may have been corrupted if only 1 drive was left in the array, and it was already failing. So, if any of the OS system files were corrupted (either originally or during the cloning process), then the whole OS would be compromised. And so, whenever data needs to be read from the array, it uses too many resources and the server becomes unavailale on the network.
0
 
Tony GiangrecoCommented:
Did you resolve the problem?
0
 
tganusAuthor Commented:
We eventually found the machine had bad RAM, causing the file issues. It degraded to the point it wouldn't boot properly and so began hardware testing.
0
 
tganusAuthor Commented:
This was found to be the root cause of ongoing problems after the drive replacement.
0
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now