Sorry if this is a double post - hit return by accident!

Based on the suggestions given for a prior post I made re: providing
access to a game server from both
the LAN and WAN, I setup my game box as follows:

NIC 1 (LAN) 192.168.0.100/255.255.255.0/no default G/W
NIC 2 (WAN) 192.168.1.100/255.255.255.0/192.168.1.1 default G/W

NIC 1 is connected to a D-Link DGL-4300 router.
This router has a route entry for destination
192.168.1.100/255.255.255.0 using 192.168.0.100 for G/W

NIC 2 is connected to the WAN via a linksys befsx41. The ports used by
the game server are forwarded
to IP 192.168.1.100 (the 'internal' NIC for the WAN).

The game server is bound to the IP for NIC 2 (192.168.1.100).

Everything works as I expect for the game - that is, my external
players can get to the server via the WAN IP
of the Linksys router, and the internal players can get to the server
directly via IP 192.168.1.100, and I'm
protected from WAN attacks via the linksys firewall.

The only thing that is not working as I'd expect is access to the
router configuration pages themselves.

get ping responses.

or get ping responses.
In other words, access to ip 192.168.1.1 from the 192.168.0.XXX network
is not functional.

I'm sure this is a simple configuration change, but I've been banging
around on this for a few hours and
wonder if anyone could help point me in the right direction.

Thanks
Rob

You have two seperate subnets set up - 192.168.0.xx and 192.168.1.xxx.
Each subnet needs a gateway to connect with traffic outside of it.  You
have established no gateway for the 192.168.0.xxx, therefore it can't
connect to anything outside of the 192.168.0.xxx subnet.

My (limited) understanding is that there should only be one default
g/w, and it is used for both nics. If I add a default g/w to the
192.168.0 subnet, be it 192.168.1.1 or 192.168.0.1, the game server
stops accepting connections from the wan side, or the net dies
completely on the machine (e.g., no web access, etc.)
Any further thoughts appreciated!

Rob

heycarnut wrote:
Subnets are logical divisions of networks.  As far as your computer
attached to the 192.168.0.xxx network is concerned, until it gets a
gateway, it can't send any traffic to 192.168.1.1.    The .1.x side
should be able to send traffic to the .0.x , because it has a gateway.
It won't be able to recieve traffic back, though.  The .0.x side can
talk to the game server's .0.100 card, and other machines on the .0.x
side, but to nothing outside of it.  Check it out and confirm what I'm
saying is true by using a packet sniffer.

Freddy Froglok wrote:
Before I read this, I did exactly that yesterday, after teaching myself
a bit more about this stuff.
You were, of course , correct. I added the G/W to the 192.168.0.0 NIC.
Still no go. Then it hit me like a hammer - I needed to also add a
static route to the linksys router for the 192.168.0.0 net using
192.168.1.100 as the G/W.
All is groovy now. Thanks for kick starting the thinking process for
me.

Rob

Accessing a printer on PC from laptop through a network
Networking domain and non-domain PCs together
Networking, but can only access via IP address
Ping timed out
Slow opening files across the network
Computer Name Problems
Network Bridging 2 Computers
Creating a Newtork - What do I need?
xp pro, domain, roaming profile
networking