Problem with incoming conns on a bit more complex network. Any help is welcome.

Okay, I have a slightly more complex network at home so this is what is my problem, others can't connect to my server. Now is there something I missed or setup wrong or is there something more i should've set up.

[Router 1] needs to tell packets where to go. [Router 1] needs to be told to send traffic on that port to 192.168.0.10 ([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 192.168.1.10 - [PC 1] within that subnetwork.

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

options:

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 (192.168.0.10) from within router 1

OR

Configure DMZ on [Router 1] to point to 192.168.0.10 (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.

Do you have FIOS?
if you dont have FIOS just disregard this post.
And i applogize ahead of time for spelling/grammer mistakes. I am tired however i came across your thread and wanted to help.

For a more indepth guide scroll to the bottom and check on my links (highly advised)

If your answer to the above question is "Yes", I have a easier method that will eliminate the double NAT that you currently have configured.

I have the same setup FIOS with fios TV. Just so you know a little about me i have am minor in Computer Networking and im working on my bachelors in network security.
I have many servers that i run at my house so when i switched over to FIOS, as you can probably imagine the double NAT cause many issues for me.

What you are trying to do, will be 100% easier if you do the following.

Basically right now your internet and all that is probably setup using the MoCA connection (Media over coax). Basically in lamens terms, you have a box on the outside of your house called a ONT that your fiber line comes into. From there, the ONT throws all of your ethenet traffic on the cable coax throughout your house. That is what makes it possible for your TV set top boxes to get video on demand and TV guide informtaion. You also have a "router" that plugs into the COAX connection, and provides a wireless/wired connection to your computers for internet.

Inside of the ONT you will have a coax output and a cat5 ethernet output. Basically what you need to do is run a cat5 cable from the ONT on the side of your house, to Router 1. This is the router that you are trying to port forward all of your stuff through. You will need to call verizon and tell them that you would like to change the media type on your ONT from media over coax, to cat5 ethernet. Then that cat5 ethernet that you ran from the ONT to router 1 get plugged into the WAN port of that router. Basically what you are doing, is making Router 1 the most forward facing router in your network so that when you get a connection request form the outside, it gets routed correctly. Now as far as Router 2 goes (the one with the coax connection) YOU WILL STILL NEED TO HOOK THIS ROUTER UP!. Basically what you are going to do is hook up Router 2, off of Router 1. So bascially, backwards from how you currently have it.

The reason you need to do this is because the Router 2 is how all of your TV's set top boxes get there TV guide data and there video on demand. If you dont hang router 2 off of router 1 then your TV's will not function correctly.

Now its better to do it this way because you are not trying to forward special ports for your television. However you are trying to forward ports for other things in your house. By making router 1 your forward most facing router, it will eliminate many of the port frwarding problems you are having right now.

Here is a link to a more in-depth How-To to get it done. i would be happy to write it up for you however its 1:40 in the moring and i have to work at 8am :P

Here is the basic HOW-TO for your current setup. Keep in mind there is 4 parts depending on what services you currently have installed (example: Mediashare DVR)

It is OK to double NAT the FIOS router in this situation because it does not affect how tv guide, video on demand, medaishareDVR actually works. This is where it saves you the configuration nightmare of configuring both routers to pass the correct forwarded ports.

I hope this makes sense. If anyone spots a mistake in my revised drawing please feel free to call me out on it.

I have a similar setup, and the same problem. This is my first post, so bear with me. Before I set my network up as defined by MindScrew, can we narrow this down? I am sure I have missed something along the lines of port-forwarding.

Okay, I have a slightly more complex network at home so this is what is my problem, others can't connect to my server. Now is there something I missed or setup wrong or is there something more i should've set up.

I have a similar setup, and the same problem. This is my first post, so bear with me. Before I set my network up as defined by MindScrew, can we narrow this down? I am sure I have missed something along the lines of port-forwarding.

/etc/network/interfaces looks like

Code:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

Through eBox, I have an option of designating my eth0 interface as external.

Q: Running a server with XP Pro firewall on. If you are trying to run a server on XP Pro and have the XP Pro Firewall feature enabled then you must explicitly enable port 3784 for both UDP and TCP. Some firewall programs, like those that ship with Windows XP, do not have an option called "Both" or "UDP/TCP". In these cases you must create two entries in the firewall: One for UDP and another for TCP. This is easy enough to do by simply giving each entry a unique name such as Ventrilo TCP and Ventrilo UDP and assigning the appropriate network protocol to each one.
If you are running a local server you must have both UDP and TCP enabled for port 3784.