How to solve problem with RPC service in hyperV console?

Question

RPC

Help, colleagues.
Domain controller 192.168.0.202 stopped opening via RDP. on his admin computer with RSAT got through the HyperV console. Specified which address to connect to, hyperV server 192.168.0.200 ... issued " Cannot connect to the RPC service on computer 192.168.0.200. Make sure the RPC service is running ". OK. I went via normal RDP to hyperV Server 2008 Core. Remote management is enabled in sconfig (in Configure Remote Management).
As a result, there is no Internet throughout the organization, since it’s not clear what happened to the domain controller and dns server 192.168.0.202, but it doesn’t open via RDP. the hypervisor swears at RPC, and there were all links to virtual machines (file, mail, workflow).
Ran cscipt Start_Coreconfig.wsf
the machines Main and SRVr2012 mail do not want to start in any way

Prescribed netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes
netsh advfirewall firewall set rule name="remote desktop (tcp-in)" new enable=Yes profile =domain
netsh advfirewall firewall set rule name="Remote Administration (RPC)" new enable=yes profile=
domain this is a gateway),
P.S2: The file server periodically opens via RDP, then again it cannot connect.
Help, pliz

Answer 1

Have you made sure that the RPC service is running?
What's going on in the Event Viewer?

Answer 2

Because there is nothing to do with the only DC on Hyper-V. And if you do, then you need a backup on another node or even an iron one.
If you need to decide quickly, then I recommend copying the virtual machine to another machine and running it there so that the people work. And then to understand why they do not start on core.
Also put 5nine Manager on it and you can normally manage virtual machines directly from the kernel.
Now is the time to start thinking about booking.