Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Windows server 2003 stops responding to file open requests.

Posted on 2013-10-29
7
Medium Priority
?
262 Views
Last Modified: 2014-05-13
I have a 2003 server that just intermittently stops responding to file open requests from workstations.

i.e

* User tries to open a word document on the server and it just gets stuck at downloading word document.

* User tries to open a pdf document on the server and it just gets stuck.

* However users can copy files from the server locally. Just not open them.

This is happening across the board to all workstations however just to complicate matters, other servers can access this server fine.

Eventvwr is somewhat clean. There are some VSS errors and w32time errors.

Any help is appreciated!
0
Comment
Question by:Marshes
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 15

Expert Comment

by:Skyler Kincaid
ID: 39610626
What are the w32time errors? If they time on the server is differing greatly from the workstations it can cause all kinds of issues.

Do you see anything in the eventvwr of the workstations that are accessing the files?

Do the drives show any errors? If you open files on the local server do you have any problems.
0
 

Author Comment

by:Marshes
ID: 39610636
W32 Errors.
event id 17
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'Server1,0x1'. NtpClient will try the DNS lookup again in 120 minutes. The error was: No such service is known. The service cannot be found in the specified name space. (0x8007277

C)

Event ID 47
Time Provider NtpClient: No valid response has been received from  manually configured peer Server2,0x1 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer  with this DNS name.  


Event ID 29
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible.  No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
0
 

Author Comment

by:Marshes
ID: 39610640
No problems opening on the local drive. ( I can also open using another server to the troubled server ).

I was unable to gain access to any workstation as the clients had a hard time understanding how to install the remote app.

However I now have access to another workstation so will be able to view logs if this happens again.
0
Industry Leaders: 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!

 
LVL 15

Expert Comment

by:Skyler Kincaid
ID: 39610642
Do you know what the current configuration of your time services is?

If you open a command prompt and type:

w32tm /query /configuration it will tell you where it is pulling the time from.
0
 

Author Comment

by:Marshes
ID: 39612821
That time command did not work from the server. However the plot thickened this morning.

Again the server misbehaved this morning however this time I could not even open shares on the local server itself i.e if i went \\localhost it would just time out.

There were no automatic services that had not started.

I checked the share manager. This opened OK, one thing i noticed was that IPC$ share had 117 connections to it. While I know the client has many devices on site. This seems high.

Could be nothing.

any ideas?
0
 
LVL 15

Accepted Solution

by:
Skyler Kincaid earned 2000 total points
ID: 39612902
Replacing the server with a more modern operating system :)

It sounds like the server service is having issues. But without anything in the event logs it will be hard to narrow it down.

Um... The time could still be causing the problem.

maybe try this from a command line:

w32tm /query /status
0
 

Author Comment

by:Marshes
ID: 40063619
I should probably say the problem ended up being symantec antivirus.
Uninstalling that from the server fixed our problems.
0

Featured Post

Industry Leaders: 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!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Some time ago I faced the need to use a uniform folder structure that spanned across numerous sites of an enterprise to be used as a common repository for the Software packages of the Configuration Manager 2007 infrastructure. Because the procedu…
Know what services you can and cannot, should and should not combine on your server.
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…
Suggested Courses

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question