If anyone can help me out on this issue, it would be greatly appreciated. It's given me over a week of grief, and I still can't find the reason.
This is my basic setup:
1) Windows 2008 R2 Host Server
2) Host server has 1 NIC, but 5 IP addresses bound to the NIC (for example purposes call this public IP's 55.55.55.55 through 55.55.55.59)
3) RRAS is setup on the Host Server
4) Hyper-V is running on host with 5 VM's
What I have accomplished:
A) 3 VM's on internal network through RRAS can access internet, and RDP port forwarding from the 55.55.55.55 on different ports. For example, I can RDP into each of the three with 55.55.55.55:1003, 55.55.55.55:1004, 55.55.55.55:1005. They all forward to internal IP on a Hyper-V internal switch to individual VM's, 2.10.10.10, 2.10.10.11, 2.10.10.12, respectively to each VM's port 3389. This works. But when I try to setup a TCP connection this way, and listen on the VM, my application does get any traffic. The same application setup on the host server works.
b) For the other 2 VM's on the internal network, I tried to setup a public IP address through RRAS from an address pool, with the public IP addresses reserved. When I do this, I don't need to forward the RDP port (for example). I can just Windows remote desktop login with 55.55.55.58 or 55.55.55.59 on port 3389. However, when I try a non-standard port for my TCP application on a port such as 2001, my application cannot get traffic.
I tried in RRAS to port forward as well the 2001 port, but I can't get any traffic. I tried also portproxy using netsh to define the listening and connecting ports, but this didn't help as well.
c) I added the inbound rules to both host and VM's for port 2001 to allow connections, and even disabled the Windows firewall just to make sure there isn't anything blocking the port.
d) I am able to setup on standard port 23, for example, a telnet service on the VM's. And this works fine. I don't have to do configure at all, even forward port 23 from the public to internal network. But when I try to setup telnet service to listen on port 2001, this doesn't work. No traffic is forwarded.
----
Why is it that I can listen and telnet into the VM's on port 23, and yet when I try to do the same on a non-standard port 2001, the traffic doesn't forward into the VM? This is the same problem I am having with my application trying to get forwarded traffic on a port such as 2001.
Again, thank you advance for considering my case, and I would be very grateful if anyone can guide me or solve this issue.