Lost connection to the server when stopping the virtual server firewall service

Question

firewall

Good time of the day!

When configuring access to MS SQL 2008 R2 on a virtual server MS 2008 R2, at the moment the firewall service was stopped (in order to check that the connection problem with MSSQL lies in it), the server disconnected and stopped pinging. There is no physical access to the server, the admin will be available only tomorrow and the work is on (the whole night is still ahead). In this regard, the question is, why did such a problem arise?
ps In the firewall setup program itself on the virtual server, it was already stopped, but it was started in the services (apparently the specifics of the virtual server), that the virtual server found out after the problem arose. Does this mean that the firewall of the virtual servers is blocked by the firewall settings of the main server from which the virtual server was created? This idea arose after opening the MSSQL ports in the virtual server, but access to the server was not opened, and the firewall service in the services was launched.
Tried googling the issue but couldn't find anything. Please do not kick too much, I am not an admin, there were no such problems on ordinary servers, but I encountered a virtual one for the first time.

Answer 1

1. In fact, a virtual server for the end user is no different from ordinary hardware, except that its “hardware” can be plastically changed by an administrator who has access to the hardware server on which virtual machines are located, depending on requirements, for example, it can be added /remove RAM, drives or network cards
2. In a situation of “games” with a firewall, the scheduler usually sets a task for rollback / reboot within 5-10 minutes after the start of the operation to change its configuration.
3. Try to connect to the server through the "Computer Management" snap-in and configure at least the service back.
4. You can try the remote registry again, configure the firewall
5. You can also remotely control the settings of the same firewall.
6. Get to the powershell/telnet console -> reboot.
This is what I just remembered offhand

Answer 2

Regarding the firewall and MS SQL - why go there and turn off the running service if you can go into its settings and add a normal rule for accessing MS SQL on the network.
For such idiotic shutdowns of “regularly operating services and services” in normal companies, they deprive them of bonuses and expel them to advanced training courses at their own expense, especially if the server is in business operation, read in production, and they can also deduct the amount for downtime from the salary of the “dropped” business service.
Therefore, in general, virtual machines were invented to make a test infrastructure separated from the business and break it as you like. And then with a slight movement, one command and a minute time, again get a clean, prepared environment for work / tests.

Answer 3

clear boom wait