Originally Posted By: PandaBear
I think I can guess where the problem is now. You are nesting one router in another and both are on default setting (my assumption since both router is on Netgear ssid). If this is the case, check the subnet the router is on and see if they are identical (i.e. 192.168.1.1 on the gateway), if it is, you need to change one of them. Having identical subnet on both WAN and LAN sides would not work.
Personally I think having serial NAT is fine if you set it up correctly and the intention is to protect the smaller subnet from the bigger subnet. I do that on my network that is shared with another household. We trust each other to share an outbound connection but not enough to access each others' computer.
Your previous router that just work may be from a brand that uses a different default setting (i.e. SMC using a subnet of 192.168.123.254 for gateway).
With a decent piece of hardware (I'm using a Juniper SSG 5 right now) you can setup a whole host of different subnets all behind the same gateway, all having NAT performed on them by the same device. This allows for network separation, individual security policies, QoS parameters and the like without having to resort to performing serial NAT, which CAN cause headaches. Headaches like the OP is experiencing which I assume is due to exactly what you are describing: He has overlapping subnets; 192.168.0.0/24 is being NAT'd through a network which is also 192.168.0.0/24. The gateway IP's would be the same and would cause some excitement for the devices depending on what they are running for software.
I understand the "cost" aspect of somebody wanting to use inexpensive hardware, whilst achieving network isolation and why using serial NAT is a convenience in that regard. However as I think you and I have been over before, it is not a "recommended" configuration for a variety of reasons.