Pulling my hair out because I thought this would be easy. Boy was I wrong.
Here goes my setup:
Installed 2 NICs, both with IPs setup properly
Went into the registry in enabled Ip Forwarding, and a ipconfig /all reports Ip forwarding as yes.
NIC #1:
IP 10.176.251.50
SM: 255.255.255.0
GW: 10.176.251.150
NIC#2
IP: 204.224.246.200
SM: 255.255.255.0
No gateway.
The NIC on the 10.xxx side is able to ping all of the 10.xxx address on the network. The Nic on the 204 side is also able to ping everything on the 204.xxx network
Now, on a PC on the 10.176.251.xxx side, I entered a route add command as follows:
route add 204.224.246.0 mask 255.255.255.0
This allows me to ping the NIC#2 on the server, but nothing else on the 204 side, just the 204.224.246.200 NIC on the server. This is killing me since I feel clueless and info on the net doesnt seem to address this problem. Even reproduced the failures with my system at home. Frustrated!!
Here goes my setup:
Installed 2 NICs, both with IPs setup properly
Went into the registry in enabled Ip Forwarding, and a ipconfig /all reports Ip forwarding as yes.
NIC #1:
IP 10.176.251.50
SM: 255.255.255.0
GW: 10.176.251.150
NIC#2
IP: 204.224.246.200
SM: 255.255.255.0
No gateway.
The NIC on the 10.xxx side is able to ping all of the 10.xxx address on the network. The Nic on the 204 side is also able to ping everything on the 204.xxx network
Now, on a PC on the 10.176.251.xxx side, I entered a route add command as follows:
route add 204.224.246.0 mask 255.255.255.0
This allows me to ping the NIC#2 on the server, but nothing else on the 204 side, just the 204.224.246.200 NIC on the server. This is killing me since I feel clueless and info on the net doesnt seem to address this problem. Even reproduced the failures with my system at home. Frustrated!!