Need Help!!! Multihomed Server

I have a Windows 2003 server that has 2 NICS. 1 is for
the WAN (has the gateway) The other is for the LAN (does
not have the gateway, 192.168.2.X) My problem is that
the remote networks connecting to the 192.168.2.x network
can ping all servers and equipment that have their LAN
gateway of 192.168.2.1. The problem server that is
multihomed and has the gateway assigned to the WAN NIC
does not respond to the remote networks that are not
assigned the 192.168.2.x, such as the 192.168.4.x - etc.
If I disable the WAN NIC and assign a gatway of
192.168.2.1 to the LAN Nic the remote networks can ping
192.168.2.21. I would like to know if there is a way to
fix this routing issue with a simple static route. If
you need more information please email me @ chrisb@t3-
tech.com.

The ping reply will go out over the WAN link, because that is where its
default route points. You should be able to fix it with a static route to
redirect all local traffic to the gateway at 192.168.2.1 . eg

192.168.0.0 255.255.0.0 192.168.2.1

"Cbdrako99" <(E-Mail Removed)> wrote in message
news:1b5c701c4509d$21cbfa00$(E-Mail Removed)...
> I have a Windows 2003 server that has 2 NICS. 1 is for
> the WAN (has the gateway) The other is for the LAN (does
> not have the gateway, 192.168.2.X) My problem is that
> the remote networks connecting to the 192.168.2.x network
> can ping all servers and equipment that have their LAN
> gateway of 192.168.2.1. The problem server that is
> multihomed and has the gateway assigned to the WAN NIC
> does not respond to the remote networks that are not
> assigned the 192.168.2.x, such as the 192.168.4.x - etc.
> If I disable the WAN NIC and assign a gatway of
> 192.168.2.1 to the LAN Nic the remote networks can ping
> 192.168.2.21. I would like to know if there is a way to
> fix this routing issue with a simple static route. If
> you need more information please email me @ chrisb@t3-
> tech.com.