Application Hang

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We've recently installed Windows Server 2008 and are now experiencing some problems with application hangups.

The server is a domain server with a few shared files and folders. No applications are installed on the server.

Periodically, someone updating one of the shared files from a client PC will cause a lockup. The event viewer on the client PC shows Application Hang. There are no events showing on the server for the time of the "incident". All shares on the server lock at that time and the only way out is to reboot the server.


Additional information that may or may not be related. Our router is acting as DHCP server for the entire LAN. The DHCP server on the domain server is disabled through services and unauthorized.

Any suggestions as to what could be causing the lockups?


.

Relevant Pages

  • RE: Access Denied on XP shared tree
    ... I have a large nuber of shared files on the server for the other two ... all of the files work fine on the server PC. ... The same shared files behave the same way on both of the client PC's. ...
    (microsoft.public.windowsxp.general)
  • Access Denied on XP shared tree
    ... I have a large nuber of shared files on the server for the other two ... all of the files work fine on the server PC. ... The same shared files behave the same way on both of the client PC's. ...
    (microsoft.public.windowsxp.general)
  • Re: nfs mount not working
    ... Modify settings or unsubscribe at: ... i reset the read write persmissions for the shared files on the server. ...
    (Ubuntu)
  • Shared Files self delete
    ... I run a small office network about 10 pc. ... We were running windows SBS ... 2 hours later "shared files gone!". ... Server, ...
    (microsoft.public.windowsxp.general)
  • File access on a UNC-path using impersonation in ASP.NET
    ... shared files, if the user looking at the page has access to them. ... However this only works when I call the page from the server it is located ... calling it as "127.0.0.1/mypage.aspx" from the server won't work. ... correct username both when run on the server and also called from a browser ...
    (microsoft.public.dotnet.framework.aspnet.security)