Hi all,
Thanks in advance for any help. I have this one tunnel that for some reason drops a portion of our network either after a day or 2. After a reboot all is ok for a few days. Here is the scenario. I have a 10.150.0.0 network with a mask of 255.255.0.0 on the main site where the VPN Concentrator is ( Cisco 3000 series)we have tunnel established to a remote site that uses 192.168.1.0 thru 192.168.1.254 range of addresses. The gateway out of our main network is to the gateway at 10.150.1.24 but traffic from the 192.168.1 network is routed out through the vpn appliance to 10.150.1.25. After a fresh reboot of the concentrator I can ping any thing on the 10.150.0.0 network, but when the network has issues I cannot ping anything in the 10.150.1.1 - 10.150.1.254 range.
Also nothing on the 10.150.1.1 - 254 can ping anything on the 192.168.1.0 network. but anything above the 10.150.1.254 network range can ping to the other machines located on that tunnel. We use a combination of Tunnels and clients connecting to the concentrator. All addresses that use the client to login are using NAT back to them. This has just started and I have looked at the config to see if anything has changed. Nothing has changed on the vpn with the exception of 1 tunnel being added that doesnt have any addresses in the 192.168. range. Any ideas would be appreciated. My first inclination is to reassign the addresses at the 192.168.1 network since there are only a few of them, but will wait to see if anyone else has had anything similar. Thanks a heap for any help.
G8orade
Thanks in advance for any help. I have this one tunnel that for some reason drops a portion of our network either after a day or 2. After a reboot all is ok for a few days. Here is the scenario. I have a 10.150.0.0 network with a mask of 255.255.0.0 on the main site where the VPN Concentrator is ( Cisco 3000 series)we have tunnel established to a remote site that uses 192.168.1.0 thru 192.168.1.254 range of addresses. The gateway out of our main network is to the gateway at 10.150.1.24 but traffic from the 192.168.1 network is routed out through the vpn appliance to 10.150.1.25. After a fresh reboot of the concentrator I can ping any thing on the 10.150.0.0 network, but when the network has issues I cannot ping anything in the 10.150.1.1 - 10.150.1.254 range.
Also nothing on the 10.150.1.1 - 254 can ping anything on the 192.168.1.0 network. but anything above the 10.150.1.254 network range can ping to the other machines located on that tunnel. We use a combination of Tunnels and clients connecting to the concentrator. All addresses that use the client to login are using NAT back to them. This has just started and I have looked at the config to see if anything has changed. Nothing has changed on the vpn with the exception of 1 tunnel being added that doesnt have any addresses in the 192.168. range. Any ideas would be appreciated. My first inclination is to reassign the addresses at the 192.168.1 network since there are only a few of them, but will wait to see if anyone else has had anything similar. Thanks a heap for any help.
G8orade