Forum Discussion
Disappearing drives
Hi
We are a small unit and have used an HP ProLiant Home Server 2011 for years.
Don't laugh; it has been the most reliable machine ever.
Recently we had a ransomware attack (my stupid fault) and although we recovered most data (Acronis) and the c: drive was not encrypted because it was not visible from the workstation that was hacked, the server is now misbehaving.
We changed passwords of course.
Normally the server sits in a cupboard with no screen and no keyboard / mouse etc. We access using RDP.
When installed in its usual place RDP may work for a few hours but then stops responding. However we can ping it Mapped drives also disappear with the usual "churn" on the windows screen.
Changing the patch cable and/or the port on the switch sometimes brings it back to life but usually we have to disconnect and re-connect it up to a screen, mouse and keyboard. On rebooting it after the move it takes a long time after Ctrl-Alt-Del to set up the user profile (normally it is instantaneous). While it has external peripherals connected it works.
On returning it to its usual location it works for a day then becomes inaccessible - pinging it still gives a reply. But RDP fails and drive mapping fails. The only way to bring it back to life is to displace it and reconnect the peripherals.
It must be a permissions issue but I am lost in space. Can anyone make any suggestions as to where and what to look for?
Thanks,
Jon
7 Replies
- You are asking on the "Windows Server Insider" Forum for the bleeding edge Server OS :D.
However, the symptom "need long after reboot to login" hints into the direction that ivp6 is disabled on the network adapters. Enable it on all network adapters and check.
If that does not fix it get a specialist, there are way too many other possibilities.Thanks. ivp6 - hmmm! That’s a big step because I suppose everything else on the network will have to change. And yes I fear you are correct; they are way too many options! 😞
- It does not mean you have to implement IPv6, except you have SoHo Router that uses IPv4 and IPv6 (Dual Stack) from your ISP and publish IPv6 DHCP to your internal network. Other than that IPv6 is required by Windows itself internally. no config needed it will use the fe80 adresses.
