I'm not sure if they are really unusual behavior or not but, I like that word...
Here is my setup:
Location1: Pix 506 (192.168.1.254) setting in front of a 1750 router (192.168.1.1).
Location2: 1750 router (192.168.4.1).
The tunnel is between the PIX at Location1 and the 1750 router at Location2.
Anyway, I just (finally!!!) got a Site-To-Site vpn working yesterday. When I came in this morning it wasn't, I could ping Location2 ip's from Location1 but not the reverse. Magically, it started back up and is now working quite well at both ends of the tunnel.
Is this normal behavior? Did my incessant pinging 'jumpstart' the tunnel somehow? Is there a command I can use for that from the router. I used the "Show Crypto isakmp sa" command at the Location2 router and it indicated that the tunnel was up. State read "QM_IDLE". What does that mean.
All my DNS traffic that is generated at Location2 is being directed into the tunnel and out the router at Location1. This results in nasty "The page cannot be displayed." errors.
I did a tracert to " and the traffic is exited out of the router at Location1.
I did a tracert to 216.239.39.99 and the traffic is exited out of the local router here at Location2.
I figure this must be an access list problem but, can't figure it out. Here are my access lists:
**********************
access-list 100 permit ip any any
access-list 101 permit gre any host x.x.x.x
access-list 101 permit tcp any host x.x.x.x eq 1723
access-list 101 permit ip any host x.x.x.x
access-list 101 permit gre any any
access-list 101 permit udp any any eq isakmp
access-list 101 permit ip 192.168.1.0 0.0.0.255 192.168.4.0 0.0.0.255
access-list 101 permit tcp any any
access-list 101 permit icmp any any
access-list 101 permit esp any any
access-list 111 deny ip 192.168.4.0 0.0.0.255 192.168.1.0 0.0.0.255
access-list 111 permit ip 192.168.4.0 0.0.0.255 any
access-list 120 permit ip 192.168.4.0 0.0.0.255 192.168.1.0 0.0.0.255
****************************
access-list 120 is applied to the crypto map
access-group 111 to the route-map nonat
access-group 101 to the outside interface
If you can answer either question I'd be very obliged for the help.
Here is my setup:
Location1: Pix 506 (192.168.1.254) setting in front of a 1750 router (192.168.1.1).
Location2: 1750 router (192.168.4.1).
The tunnel is between the PIX at Location1 and the 1750 router at Location2.
Anyway, I just (finally!!!) got a Site-To-Site vpn working yesterday. When I came in this morning it wasn't, I could ping Location2 ip's from Location1 but not the reverse. Magically, it started back up and is now working quite well at both ends of the tunnel.
Is this normal behavior? Did my incessant pinging 'jumpstart' the tunnel somehow? Is there a command I can use for that from the router. I used the "Show Crypto isakmp sa" command at the Location2 router and it indicated that the tunnel was up. State read "QM_IDLE". What does that mean.
All my DNS traffic that is generated at Location2 is being directed into the tunnel and out the router at Location1. This results in nasty "The page cannot be displayed." errors.
I did a tracert to " and the traffic is exited out of the router at Location1.
I did a tracert to 216.239.39.99 and the traffic is exited out of the local router here at Location2.
I figure this must be an access list problem but, can't figure it out. Here are my access lists:
**********************
access-list 100 permit ip any any
access-list 101 permit gre any host x.x.x.x
access-list 101 permit tcp any host x.x.x.x eq 1723
access-list 101 permit ip any host x.x.x.x
access-list 101 permit gre any any
access-list 101 permit udp any any eq isakmp
access-list 101 permit ip 192.168.1.0 0.0.0.255 192.168.4.0 0.0.0.255
access-list 101 permit tcp any any
access-list 101 permit icmp any any
access-list 101 permit esp any any
access-list 111 deny ip 192.168.4.0 0.0.0.255 192.168.1.0 0.0.0.255
access-list 111 permit ip 192.168.4.0 0.0.0.255 any
access-list 120 permit ip 192.168.4.0 0.0.0.255 192.168.1.0 0.0.0.255
****************************
access-list 120 is applied to the crypto map
access-group 111 to the route-map nonat
access-group 101 to the outside interface
If you can answer either question I'd be very obliged for the help.