So here is my issue, sounds easy. Sounded easy to me at first as well, and I am probably just overlooking something.. Butttt...
I have a pix 501(192.168.1.1)(192.168.1.x/24) ---> 2600 series router ---> P2P T-1 ---> 2600 series router(192.168.2.x/24) ---> Terminal Server(192.168.2.2/24)
Terminal Server can ping all clients on the 192.168.1.x network fine. It cannot ping the pix. Anything within the 192.168.1.x network can ping the pix just fine. Anything in the 192.168.2.x network cannot ping the pix. The pix cannot ping anything in the 192.168.2.x network.
So pretty much I have full convergence between the two networks with the exception of the pix talking to a different subnet other then its own internal subnet. Am I missing a security setting here? I have done /32 routes in the pix, I have done /24 routes.
A little something to add an extra twist. After putting in the /24 route to the PIX I am able to ping the TS 1 out of 4 tries and then it stops.
The end result is for RDP to be going through the pix to the secondary subnet to the TS server.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...