When stopping the service firewall virtual servers lost connection to the server

Good time of day!

When setting up access to MS SQL 2008 R2 on a virtual server MS 2008 R2, in the time of a stop of service of the firewall (to test that the connection problem with MSSQL lies in it) the server has terminated the connection and stopped pingomatic. Physical access to the server admin will be available only tomorrow and the work is (the whole night still in front). In this regard, the question of why this problem occurs?
p. S. In the program settings of the firewall on the virtual server it was already stopped but the services run (apparently the specific virtual server), that server is a virtual found out after the problem occurred. Does this mean that virtual servers firewall blocked by the firewall settings of the server from which the virtual server was created? The idea arose after open MSSQL ports in virtual server but access server is not opened, and the firewall service in the services was launched.
Tried to Google the problem but nothing worthwhile is not found. The request strongly not to kick, admin are not on the normal servers, no such problems arose and faced virtual the first time.
October 3rd 19 at 03:54
3 answers
October 3rd 19 at 03:56
1. Virtual server, in fact to the end user nothing from normal hardware is no different, except that his"hardware" can easily be changed by an administrator with access to the hardware server on which the virtual machines, depending on requirements, for example, can be added to/removed memory, drives, or network cards
2. In a situation of "games" with built-in firewall typically, the planner aiming for rollback/reboot within 5-10 minutes after the start of the operation for changing its configuration.
3. Try to connect to the server via the snap-in "computer Management" and reconfigurate at least the service back.
4. Remote registry, you can try again, reconfigurate firewall
5. You can still remote control to jiggle the settings of that firewall.
6. To get to the powershell/telnet console -> restart.

This is the point that I remembered offhand
October 3rd 19 at 03:58
At powodu firewall and MS SQL — why was it necessary to go there and turn OFF a running service, if you can go to its settings and add the normal rule for access to MS SQL in the network.
Over here such here idiotic shutdown "operating regular services" in normal companies denied bonuses, and kicked in a refresher course at his own expense, especially if the server is in the business of operation, read in production, and even deduct the amount for the simple of s/n is "dropped" business service.
Therefore, in General, and invented virtual machines, to make separated from the business test infrastructure and to break it somehow. And then a slight movement, one team, minute and time again to get a clean, prepared environment for work/tests.
no, the server is not in production, just the admin ran away early. Nothing terrible has happened. - Mara_Grant commented on October 3rd 19 at 04:01
October 3rd 19 at 04:00
it is clear, boom to wait

Find more questions by tags Firewall