Firewall – Hyper-V disable internal firewall

firewallhyper-v

How can I disable a firewall on my internal network?

Problem

I have a Hyper-V on a Windows Server 2012 R2 with one VM, when I disable the firewall I can get internet on my VM, but when I turn on firewall, internet doesn't work. On my VM I can ping 8.8.8.8 and I can ping my gateway address too. (my server had always internet)

Note I try to disable internal like that but it's don't work too : http://www.altaro.com/hyper-v/wp-content/uploads/2015/01/RRAS-Firewall-Adapter-Selection.png

I need allow some rule on my firewall with advanced.

If you need more information leave a comment, thanks for your help.

Best Answer

From your last comment, I believe that you problem is DNS, and not the firewall service.

The prove for this theory is that when you configure the VMs with the Google Public DNS servers 8.8.8.8 they work fine, but when you configure them to use the IP address 192.168.1.254 (which I can't tell if its the IP address of the host server or your gateway), name resolution fails and you don't get internet access.

You either need to fix the DNS on the gateway (if the IP address 192.168.1.254 is the gateway) or install DNS and configure it on your host server (if the IP address 192.168.1.254 is your host server)

Here's a good link on what DNS does, and how you can install and configure it inside your network: https://technet.microsoft.com/en-us/library/cc794771

Related Solutions

Issue resolving names on Hyper-V guest with Routing and Remote Access

Can you ping anything outside of the private network? If you can't then you are missing the default gateway/RRAS. Most likely you will need to enable RRAS on your host to provide routing services. It's silly easy to install and get working.

Firewall – Virtualized firewall under Hyper-V

What Wesley said... Plus a diagram:

              +----------------------------------+
              |    +----------+   +---------+    |     +----+ +----+ +----+
              |    | pfSense  |   | Host OS |    |     |    | |    | |    |
              |    |          |   |         |    |     | PC | | PC | | PC |
              |    +----------+   +---------+    |     |    | |    | |    |
              |         ^   ^          ^         |     +----+ +----+ +----+
              |         |   +------+   |         |        ^      ^      ^
              |         |          |   |         |        |      |      |
              |         V          V   V         |        V      V      V
+--------+    +---+   +-------+  +-------+   +---+      +-----------------+
|Internet|<-->|WAN|<->|WAN NET|  |LAN NET|<->|LAN|<----+|    LAN SWITCH   |
+--------+    +---+   +-------+  +-------+   +---+      +-----------------+
              |          Hyper-V Host            |
              +----------------------------------+

It's actually possible to use the same NIC on the Hyper-V Host for both WAN and LAN, but you'll need to setup vLANs and need a switch that supports them. It gets messy quickly and NICs are fairly cheap. A note on NIC chips, get a good one, like Intel, Broadcom, etc. Stay away from Realtek, Marvel, and most of the on-board chips on cheaper and DIY motherboards. They're nothing but trouble for virtualized environments.

Also, keep in mind that Hyper-V is a bare-metal Hypervisor. It is NOT a service that runs in Windows. What used to be the Windows installation on the machine becomes a special VM. This will not appear to be the case for simplicity and usability reasons, but comes into play when you do things like setup the Hyper-V Networking.

Best Answer

Related Solutions

Issue resolving names on Hyper-V guest with Routing and Remote Access

Firewall – Virtualized firewall under Hyper-V

Related Topic