Port Forwarding to Hyper-V in Server 2012?

[RADRaze2KX]

I'm attempting to create some small isolated servers for various tasks, one of which is a Mumble server (voice chat). It's not the first VM I've ever created, but it IS the first Hyper-V I've created in Server 2012.

My server isn't acting as a DHCP server, my router is. I've issued a static IP to my VM and set up port forwarding on my router. The VM is running XP Pro SP3 w/ Hyper-V Legacy Network Adapter (the standard one doesn't show up in the VM), the ports were opened in the client's Windows Firewall, and I've even tried turning the firewall off completely to the same effect - I can connect to the mumble server from the host machine using the local IP, but when I try to hit it from the internet it doesn't go through. I'm going through dyndns, and confirming it's got the right IP using whatismyip dot com. Whether I use the DynDNS address or the actual public address, the VM doesn't let a connection through. There is no AV/FW software installed in the client.

With VMWare this process would be no different than what I've already done. Do I need to open up the same ports on the host machine? Do I need to forward to the host's IP instead, then somehow redirect through the Hyper-V switch? What am I missing here??

 

[RADRaze2KX]

Nevermind. I guess the router was being ridiculous. It's got forwarding set up on three other ports and they're blocked as well. I removed then re-added the forwarding set up and it's working now. Maybe I should make my computer the DHCP server? Would this be a better idea? Then I could set up all the forwarding through the server, is that correct?

 

[R3d]

your forwarding is still setup through your firewall, if you moved the dhcp over to a server then you have a little more granular control over it. You'd also be better off on the server as you can then get dns running smoother internally.