Windows 7 firewall exception incoming scope rule for different subnet

This one problem kept my win 7 PC from being able to be pinged and share files from incoming ubuntu PC on another LAN with a different subnet.

I have 2 lans, 2 routers, each using a different range of IP.
One is on 192.168.1.x
Other is on 192.168.200.x

I have a static route to direct packets from forward LAN to the other LAN. Only thing was Windows 7 kept blocking that route UNLESS the firewall for the private network was turned off. Even if you turn on sharing, etc... Windows 7 firewall only allows for the subnet LAN it exists on.

So you have to put in a rule and change the scope
The exception is to add your local lan ip range.
For me it scope exception is 192.168.200.0/24

screenshot and also shows the pings from ubuntu PC on different LAN works.

Click Action, new rule, then custom, keep clicking next till you get to scope. Under Local IP, enter your LAN as I did.
Apply it and it works.

That's good to know sdowney717, I wasn't sure if Windows could manage sharing between two different subnets but adding the subnet range to the firewall rules looks like it works pretty well for this.

You can also connect to both subnets with a single NIC by adding the secondary subnet to the advanced TCP/IP settings in IPv4 properties.

Is what you mean called binding an ip to a NIC?

If so, give me an example of what I would have entered for the nic card.
(Pictures help)

The win7 PC is on 192.168.200.30
Router2 is on 192.168.200.1

Router 1 is on 192.168.1.1
WAN ip for router2 which it gets automatically from router1 is 192.168.1.100
WAN port of router2 is plugged into LAN port of router1.

I left DHCP on for both routers. I assigned a manual IP to the win7 PC.

the static route from router1 is setup as

Dest IP 192.168.200.0
Subnet 255.255.255.0
Gateway IP 192.168.1.100

This lets router1 know that packets of 192.168.200.x need to go to the attached device router2 at 192.168.1.100

I had to yank a netgear router off my LAN and use a Verizon 7501 to get the static route to work. Fo some reason the WGT624v3 netgear always jumped IP when I setup a static route. I even tried forcing it manually and it would not work. Routers that dont route! Caused a lot of head scratching.

My router1 is a nice old Gateway G wireless router.

Pictures aren't really required, it's the same as setting up a static IP but you type both routes into the advanced TCP/IP settings for which ever adaptor you want to bind the subnets too.

For some reason you are saying WAN IP but the first one is a LAN IP.
WAN ip for router2 which it gets automatically from router1 is 192.168.1.100
WAN port of router2 is plugged into LAN port of router1.

Usually for dual router set up's you will want to disable DHCP on the secondary router but with your dual LAN's it might not work the same.

Normally you would plug the secondary router into the LAN port on the first router, then connect the other router's LAN port, LAN to LAN. But this would depend on what you are using the second router for.

This dual subnet network is rather strange, and I'm trying to figure out why someone would need to do this with all the available options for NTFS sharing.