Simple routing problem?

[jedimaster100]

Hi all. Something I seem to be misunderstanding. Here is my setup.

I have a windows server running with 2 NICs. One (192.168.1.1/255.255.255.0) is connected to a switch where all the PCs in the LAN are located. This has RRAS, AD, DHCP and DNS running. RRAS is configured with NAT and allowing the LAN on NIC1 access to internet through NIC2.

The other NIC (192.168.11.2/255.255.255.0) is connected to the Netgear DG834G router (192.168.11.1/255.255.255.0). I have set up a static route as follows:
Destination: 192.168.1.0/255.255.255.0, Gateway, 192.168.11.2, Metric 2.

I also have some laptops which connect wirelessly and are given IPs off the Netgear router's DHCP 192.168.11.10-254. Laptops are able to ping both 192.168.11.1 and 192.168.11.2. However, if I try to ping 192.168.1.1, then I get request timed out.

Using the Diagnostics page on the router, I try to ping IP 192.168.1.1 with the same 100% packets loss error. What am I doing wrong?

 

[tkrl26]

Seems like your answer is in here somewhere.http://technet.microsoft.com/en-us/library/cc787456%28WS.10%29.aspx

NIC2 is not allowing traffic past it, so you need to configure it to allow traffic through.

 

[jedimaster100]

Seems like your answer is in here somewhere.http://technet.microsoft.com/en-us/library/cc787456%28WS.10%29.aspx

NIC2 is not allowing traffic past it, so you need to configure it to allow traffic through.

Thanks. I've tried adding a static route in RRAS as follows:
Interface NIC2, Destination: 192.168.1.0/255.255.255.0, Gateway: 192.168.1.1

But results are still the same. Any ideas please?

 

[jedimaster100]

Hmmm. It's as tkrl26 said. This is a defacto security feature whereby since the idea is additional security through 2 NICs, allowing the NIC connected to the router access to the LAN, might as well set up the LANs to connect directly to the router anyways...