Routing to a computers outside the firewall ?

The router has to know that the 10.0.0.3 subnet is on the same side of the route. I assume it is a linksys or similar device. If it is you will have to add a route to tell it how to get there.

Do I add the route to the DSL router?
because I already add the route to the Firewall and it didn't do any good...

From my machine(192.168.0.7) I can get to the Internet,
but I can't ping the DSL router either...
My gateway is the firewall(192.168.0.1),
the firewall's gateway is the DSL Router...

Ok, you have a firewall between you and a dsl router. and the webserver is on the other side of the firewall but behind the DSL router?

What kind of firewall is it? Can it ping the webserver? Can the webserver ping the DSL router? Can the webserver ping the firewall (check logs if it doesnt reply)? Just trying to get a visual of what you are working with.

SJ,

?1 NetGear
?2 No
?3 Yes
?4 No
Log shows no pings

Cool thanks...

What message do you get when the Web server tries to ping the firewall?  What is the IP address of the external interface on the firewall?  What is the default gateway for the Web server?

DR,

?1 Request timed out.
?2 10.0.0.45
?3 10.0.0.1

Thanks

What's the default gateway for the Web server?

I answered that just above...

Ok, I'm going to try a diagram here to make sure we are all on the same page.

client 192.168.0.7
webserver 10.0.0.3
firewall ?192.168.0.1? and 10.0.0.45 <clarify this pls
dsl router ? and ?  (i assume 10.0.0.1 and something from your ISP)

client ---------->firewall--------->DSL Router
                              |
                          webserver

From the client PC can you ping the firewall and the DSL router or get to the net on the other side of the router.

Other than ping can you access the webserver with browser etc? Is the netgear "firewall" a simple NAT router? Model # on it?

That's a good idea; I'll try to diagram it,

client(192.168.0.7)<---->(192.168.0.1)Firewall(10.0.0.45)<--------WebServer(10.0.0.3)--------->(10.0.0.1)Router(ISP_DHCP)

Client can see the Internet, but can't ping 10.0.0.1 or 10.0.0.3

Thanks Guys....

From the client if you try to goto http://10.0.0.3 or are you trying by name? What happens? Are there any other services on that box you can try to connect to? SSH, telnet, terminal services? It doesnt sound like the firewall is blocking outbound ports and shouldnt need a route to get there since its local to him. Does the firewall have any rules regarding ICMP?

Here's what I think is happening.  You send a packet from your client to the Web server.  Your Web server responds.  Since the client is on a different subnet, it sends its response to the DSL router (its default gateway).  The DSL router sees that the packet is for a non-routable IP address directly connected to it, and discards it.  Can you set up a packet capture on the Web server to verify that the pings are reaching it?  Can your DSL router log packets it drops as unroutable.

Some possible solutions:
1) Do either your DSL router or firewall allow you to name a DMZ port or address?  (If you can give make and model, we can look that up online.)
2) You could make 10.0.0.45 the default gateway for the Web server, but then it will probably become unavailable to the Internet, which I'm assuming you don't want.
3) Put your Web server inside your firewall, then configure the firewall to forward all packets coming to port 80 to the Web server (look in the documentation for setting up a "virtual server").

Now why doesn't the router respond to pings from the client?  Siliconjunkie's idea of the firewall preventing ICMP packets is the most likely, but could it be that the router is set not to respond to pings?

Maverick5:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1 
EXPERTS:
Post your closing recommendations!  No comment means you don't care.