Port-forwarding on the same internal network as a DC hub

[Hoffy 0]

Hi friends,

 

I run a file sharing hub on my university residence's LAN network, which runs mostly quite well, except that some users, including myself, fail to connect to any online users, when in active mode. This is probably a problem for everyone else because they're behind routers and they haven't opened up the hub's port (411) on their respective routers, but as operator of the DC hub, the problem is a little different for me.

 

My network is set up as follows:

 

Wall port ___> [Ethernet cable] ___> Belkin router (F9K1002 v3) ~~~ [Wi-Fi] ~~~ My PC (192.168.2.3)

                                                                 ___> [Ethernet cable] ___> PC running Ynhub (192.168.2.2)

 

In order to connect users, naturally, I had to open up port 411 to 192.168.2.2, but my personal computer is left having to survive in passive mode, because, as I have come to discover, it is logically impossible to forward a port to two private IP addresses on the same internal network. So then, how do I activate active mode for my PC? My guess is that I need to reconfigure the entire set-up somehow, but my research hasn't yet revealed a clear solution.

 

Thus I am here! Any help would be greatly appreciated!

[Mek 13]

No, you don't need to forward the HUB port to the computer where you are running the client. You only need to forward the TCP and UDP ports specified in the client, in Active mode setting (generally these can be 411 anyway but it's recommended to choose them as >10000).

Your PC needs to be configured for active mode as follows:

- Check option: Firewall with manual port forwarding

- External / WAN IP should be the one that the Belkin router has on its external interface (on the ethernet cable from wall port)

- TCP and UDP ports should be forwarded from the router to your PC (192.168.2.3) and set up in Active mode setting.