View Single Post
Old 01-17-2010, 03:22 AM   #5
Junior Member
Join Date: Aug 2009
Posts: 1

when someone tries to make a connection into a service on [PC 1], the steps it needs to goes through are as follows after entering the network from the ISP:

External to your network: Dynamic IP -> Entrance to [Router 1] on port XXXX

[Router 1] needs to tell packets where to go. [Router 1] needs to be told to send traffic on that port to ([Router 2]'s ip on that subnetwork)

Leaves [Router 1] to enter [Router 2] on port XXXX

[Router 2] as you say is configured to forward anything received on port XXXX to - [PC 1] within that subnetwork.

without telling router 1 where an incoming connection needs to go, they will be ignored completely


Port forwarding (which is not necessarily a part of Router firewalls)
Enable port XXXX to be forwarded to [Router 2]'s IP on that network ( from within router 1


Configure DMZ on [Router 1] to point to (Router 2's ip on that subnetwork) - this will forward all incoming traffic to Router 2, removing the need for configuring port forwarding for any additional apps

a possible reason other applications that 'require' port forwarding work while others don't is possibly their implementation of NAT - some programs may be able to take care of the port forwarding themselves through [Router 1] if it allows them. not all applications can do this.
Wolfric is offline