We have several remote offices that connect back to corporate via VPN tunnel using 3002 hardware client at remote sites that connects up to 3005. The ip space at remote offices is 10.6.x.x. The IP space at corporate is 10.5.4.x. Users at remote sites can get to everything here and at other remote sites.
We installed a DMZ here at corporate in the 192.168.1.x space and place web servers, etc. in it. Here at corp. we can get to the DMZ devices from our workstations, however the remote sites cannot. Also if I come in from home via software VPN client I cannot get to the DMZ devices.
I am hoping that this is something that can be fixed?
Can anyone help a poor windows 2000 admin pretending to be a cisco admin :)
Somewhere in all your PIX-configs there is an access-list that defines the traffic for the VPN tunnel. This traffic is to be exempted from NAT.
You have to add the 192.168.1.x range to this list. Depending on the the way your systems are set up, there could even be two access-lists. One to define the traffic destined for Internet, which is to be NATed (this list should EXclude the range that you use for remote offices), and another one which defines the traffic for the VPN. (this list should INclude the range that you use for remote offices) What you should do is find these lists and change them.
I really wish you a merry Christmas, preferrably not in config-mode!?
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...