Go Premium for a chance to win a PS4. Enter to Win

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

Problems with shares after power loss to Server 2008

I have been presented with a Windows 2008 standard server (HP Proliant M350 G6) that has had power loss after an extended power outage where the UPS drained out. I am in Melbourne Australia and we have been dealing with floods and power outages for the last few weeks.

Server shares seems to be misbehaving. On any workstation, and irrespective of the logged on user, a mapped share (set by batch script and previously working fine) will display upon an initial attempt to open it: "An error occurred while reconnecting X to \\servername\path. Microsoft Windows Network : the local device name is already in use... etc".  A second subsequent attempt to connect a few seconds later, is successful.
Then, upon attempting to open, drag or copy/paste documents from the share to the workstation the following errors occur:
drag or copy/paste - "cannot copy filename: cannot read from the source file or disk."
open (i.e. word document) - "could not open filename".
I have checked with the user as administrator, even taken ownership of the share and files folders recursively.
I would live some advice on how to restore the behaviour of my shares?
0
paddygreenhood
Asked:
paddygreenhood
  • 3
  • 2
1 Solution
 
ToxaconCommented:
Is the network functioning properly?
0
 
paddygreenhoodAuthor Commented:
In respect of the above, No.
However, the workstation could join the domain, internet connectivity exists. I rejoined the WS to exchange on same server (single server environment) but found it prudent to set up a fresh outlook profile and upon reconnection found that it was very slow getting the mail to flow back to the workstation.
Another workstation (posted in a separate thread) cannot rejoin the domain at all.
DNS and DHCP services on server are reporting ok.
0
 
ToxaconCommented:
If you have a managed switch, can you check the error rates on the ports? Especially the port(s) the server is connected to.
0
 
paddygreenhoodAuthor Commented:
No managed switch, just a single DC with 4 clients.
Found the ntfs sharing servoce needed restarting. That, plus a reboot, and I am running again.
0
 
paddygreenhoodAuthor Commented:
Found my own solution, see above...
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

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