10-13-2004 01:59 PM
We are expeiencing a very strange issue and any insight would be appreciated. Here's the scenario, then I'll describe the problem.
Store #1
XP Computer = 192.168.4.11 connects to
Adtran router = 192.168.4.1 connects to
SBC 64k Frame to
Home Office WAN Router = 192.168.0.1 with a gateway of last resort = 192.168.0.90
which is the address of the pix which sends all internet traffic to the 64.x.x.x address (external)
All the sudden Store one can not access the internet. It can however access other stores and HO with no trouble. When I try to ping or use IE at the store, it resolves the address, but just times out.
In the pix there is the following line to take all internet traffic from the stores and foward it to external side of the pix and out the internet
route 192.168.0.0 255.255.0.0 64.x.x.x 1
Like i said this worked fine until today. We are at a loss.
Please help!
Solved! Go to Solution.
10-13-2004 02:58 PM
Let's see if we can help.
The route statement that you shared with us does not appear to be correct.
Your route statements should most likely look like this:
route 0.0.0.0 0.0.0.0 64.x.x.x 1 <--- tells the Pix to use the outside network as gateway of last resort
route 192.168.4.0 255.255.255.0 192.168.0.1 <--- tells the Pix that the 192.168.4.0 exists on the inside interface
Does this make sense?
You would have additional route statements for other internal networks pointing to a device on the inside like the 192.168.0.1 HO WAN Router so the Pix knows how to route packets to them.
Maybe you can share with us the "show route" statement so we can help you determine if this is indeed the cause.
thanks
peter
10-13-2004 02:58 PM
Let's see if we can help.
The route statement that you shared with us does not appear to be correct.
Your route statements should most likely look like this:
route 0.0.0.0 0.0.0.0 64.x.x.x 1 <--- tells the Pix to use the outside network as gateway of last resort
route 192.168.4.0 255.255.255.0 192.168.0.1 <--- tells the Pix that the 192.168.4.0 exists on the inside interface
Does this make sense?
You would have additional route statements for other internal networks pointing to a device on the inside like the 192.168.0.1 HO WAN Router so the Pix knows how to route packets to them.
Maybe you can share with us the "show route" statement so we can help you determine if this is indeed the cause.
thanks
peter
10-13-2004 05:35 PM
Thanks! I removed my statement and added yours for the 192.168.4.x network and the 20 other stores and everything works great!
route inside 192.168.1.0 255.255.255.0 192.168.0.1 1
route inside 192.168.2.0 255.255.255.0 192.168.0.1 1
route inside 192.168.3.0 255.255.255.0 192.168.0.1 1
route inside 192.168.4.0 255.255.255.0 192.168.0.1 1
route inside 192.168.5.0 255.255.255.0 192.168.0.1 1
route inside 192.168.6.0 255.255.255.0 192.168.0.1 1
route inside 192.168.7.0 255.255.255.0 192.168.0.1 1
route inside 192.168.8.0 255.255.255.0 192.168.0.1 1
route inside 192.168.9.0 255.255.255.0 192.168.0.1 1
route inside 192.168.10.0 255.255.255.0 192.168.0.1 1
route inside 192.168.11.0 255.255.255.0 192.168.0.1 1
route inside 192.168.12.0 255.255.255.0 192.168.0.1 1
route inside 192.168.13.0 255.255.255.0 192.168.0.1 1
route inside 192.168.14.0 255.255.255.0 192.168.0.1 1
route inside 192.168.15.0 255.255.255.0 192.168.0.1 1
route inside 192.168.16.0 255.255.255.0 192.168.0.1 1
route inside 192.168.17.0 255.255.255.0 192.168.0.1 1
route inside 192.168.18.0 255.255.255.0 192.168.0.1 1
route inside 192.168.19.0 255.255.255.0 192.168.0.1 1
route inside 192.168.20.0 255.255.255.0 192.168.0.1 1
Thanks again!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide