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

Uploading Files Hangs Windows 2008 Server Service

This one is VERY interesting.

I have a Windows 2008 server that functions fine UNTIL someone tries to upload a file to a remote server on the web.  Here's the scenerio:

A Windows XP computer uploads a file to a website (claims file).  This file is sitting on the W2K8 box and is accessed via a map drive on the Windows XP machine.  The upload goes fine.

They then try to upload another file and that is when the network seems to "hang."  In researching and narrowing it down, it is actually the Server service on the W2K8 box that hangs.  There are no error messages in Event Viewer and the service doesn't "stop" it shows running.  But when you try to restart the service, it hangs in trying to be stopped.

Solution:  Reboot the server (Not a good solution, obviously)

This happens on every workstation in the office.  It also happens when you try to upload the file to a different website.

Anyone got any ideas?

rpierce1373
0
rpierce1373
Asked:
rpierce1373
1 Solution
 
Darius GhassemCommented:
Are you running Symantec Endpoint?

Here are some other options to disable as well that have helped fixed these types of issues.

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_26176031.html

Make sure you go to the Properties of the NIC disable Large Send Offload on the properties under Advanced.

Reboot the server
0
 
MSFT_NET_SEECommented:
Looking at Symanec is a great idea. You have to be running a version that is supported on 2008, which for Endpoint Protection is MR4 or above. The Symantec issue usually takes a few hours after a reboot to manifest itself, but not always. You will usually know if Symantec is an issue if XP/2003 systems are affected but Vista/2008 systems are not.

There are also known issues with other third-party filter drivers and tdx.sys, so I would make sure that if you are running any AV software to install: http://support.microsoft.com/kb/2029048.

I would also make sure the system is running the latest firmware and driver updates from the hardware manufacture, especially if you are running Broadcom NICs.
0
 
rpierce1373IT ManagerAuthor Commented:
Actually, the problem ended up being the folder on the server that we were connecting to had an issue either on the HD or security.  Either way, we rebooted the server, renamed the folder, put a new folder in with the same name & everything worked like a charm.

Thanks for the suggestions!
0
 
ee_autoCommented:
Question PAQ'd and stored in the solution database.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now