I recently set up a site-to-site between Company A's PIX (outside int 206.139.x.x) and Company B's PIX (outside int 205.144.x.x). The intended goal was to allow for 15 machines on Company A's internal network (10.6.x.x) to access a machine on Company B's internal network (10.5.x.x).
When I initially set this up, I also added a static route on the PIX, since it is the default gateway, to ensure clients in Company A know the route to access the machine on Company B, and was able to access the machine on Company B without any problems.
I recently received a call that Company A cannot access the machine at Company B. Upon looking at Company A's PIX, I noticed the static route was gone. I have tried adding it, but to no avail.
What should the proper syntax be for this static route? I'm thinking that maybe I'm having abrain freeze here.
Using the "sho cry is sa" command, I can see the tunnel is established and idle. I cannot ping any IP's on the other network from the firewall, or any of the 15 machines even if I add a static route locally.
Any ideas on what it may be or how I can pinpoint this issue?
When I initially set this up, I also added a static route on the PIX, since it is the default gateway, to ensure clients in Company A know the route to access the machine on Company B, and was able to access the machine on Company B without any problems.
I recently received a call that Company A cannot access the machine at Company B. Upon looking at Company A's PIX, I noticed the static route was gone. I have tried adding it, but to no avail.
What should the proper syntax be for this static route? I'm thinking that maybe I'm having abrain freeze here.
Using the "sho cry is sa" command, I can see the tunnel is established and idle. I cannot ping any IP's on the other network from the firewall, or any of the 15 machines even if I add a static route locally.
Any ideas on what it may be or how I can pinpoint this issue?