• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Hyper V and Port Forwarding

J

jadams

2[H]4U
Joined
Mar 14, 2010
Messages
4,086
Any idea what the problem is with port forwarding to a VM in hyper-v?

I know for a FACT that i have port forwarding setup correctly on my router. To test this I forwarded 3389 to the Host server and it connects perfectly. I change the IP address to forward it to the VM in hyper-V and no dice.

Every single security measure off turned OFF in the VM. No firewall, no AV, nothing! And the VM is configured to allow remote connections.

I have read on the internet that some other people are also having problems with this same thing. Their replies usually have people scratching their heads with replies like "its just a VM, and it shouldnt matter".

What about the guys here? Any idea at all? This is bugging the hell out of me.
 
What all have you tried to far? How many NICs do you have setup for your Hyper-V system? Are you trying to setup forwarding to the correct NIC?
I might suggest trying something like setting up an FTP server or telnet server and forwarding those ports to your VM. See if you get the response you're expecting. If so then the problem is probably with your router, if not then it's a firewall issue.

One other thing I would suggest is to make sure you're forwarding to the IP address of the Hyper-V guest and not the host.
 
Last edited:
The Host server has ONE NIC, and the VM's virtual nic is bridged to it. The router and other clients on the LAN can ping these VM's as well as rdp to them. As for router/firewall, I'm using pfsense. I'm at a loss how port forwarding works for the Host server, but if i change the address for the port to be forwarded to that of a VM it doesnt work.

I dont see how setting up a ftp server or telnet server will net me any different results than opening the port for rdp. I had ventrilo setup on port 3784 and im getting the same issue.
 
Last edited:
I am running 100+ hyper-vs and have never encountered any such issues. Something with the way your bridged adapter is setup must be interfering. Additions up to date?
 
I've been running multiple VMs separating out functions to different VMs with regular consumer grade D-Link routers since MS released Virtual Server 2005. I've never had any issues.

I did have some performance issues when moving from 2008 Hyper-V to 2008 R2 Hyper-V, but that was due to large TCP offload being turned on by default with 2k8 R2 where it had been turned off before with 2k8 for the same NIC in my host. Disabled it again, and all my issues were resolved.

You may want to try turning off some of the offload functions on your host NIC. I've seen that fix a lot of weird behavior on MS OSs.
 
You must log in or register to reply here.
Back
Top