Linux firewalls on Hyper-V can't connect to external network

Hi Experts

I have a Hyper-V server at a data center (collocated) on which I'm trying to install a Linux firewall to handle security and simple port forwarding.

- I'm using a legacy network adapter
- I have checked with the hosting company: IP address, mask, broadcast and gateway all correct.
- My internal (green) virtual network is working flawlessly on (, no physical NIC
- My external (red) isn't working. I can ping to it from my hyper-v on same subnet but I can't ping anything from it (it can ping its own public IP). It's on IP ( with broadcast and gateway
- I've also tried Smoothwall, Edian, Monowall, Ubuntu ... all same result

Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kerem ERSOYPresidentCommented:

It does not seem to me that this is an issue with the firewall itself. If nobody could ping it it might be an issue with default gateway. Please make sure that the default gateway points to a valid address.

The default gateway over your host most have the DG located over the segment same as your RED interface otherwise it can not route the traffic.

RogerIvyAuthor Commented:
KeremE, I'm wondering if the issue isn't related to the Hyper-v/Linux setup because:
1. All my windows VMs are able to be set up with external NICS (therefore public IPs) and can ping, browse etc.
2. None of my Linux VMs can use an external NIC (with public IP).

In theory the DG is working - for Windows VMs anyway.

What I don't know is:
- Is the problem with my overall system?
- Is it possible that the hosting company (data center) have a strange setup that Windows doesn't mind and Linux can't work with?
Pierre FrançoisSenior consultantCommented:
If it is possible on a Hyper-V to change the way the virtual NIC adapters are defined, try other settings: bridged, NAT, internal network, and so on. Normally, bridged should do the job.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RogerIvyAuthor Commented:
Pfrancois, I've made several changes to the setup without success. There is a limit to what I can do because I don't want to lock myself out of the server.

I may try that when I am physically at the server.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Distributions

From novice to tech pro — start learning today.