09-17-2009 03:03 AM
Hello;
We configured a new VPN tunnel on our VPN concentrator 3005. Local IP address for this tunnel 10.0.0.100/32 and we named this as X_local. There was another network-list names as Y_local which also has 10.0.0.100/32. After we configured the new tunnel, the old tunnel become problematic. 10.0.0.100 couldn't reach remote network and the old tunnel didn't become UP. We logged out from the new tunnel then the old one started working. Now two of them are working. However i think we should know reason of this problem for a better workaround. Anyone knows reason???
Add-on: The old one becomes UP, but we have to wait for a while(10-20 ping timeouts). When we log out the new one, it becomes UP after one timeout.
09-17-2009 08:36 AM
Hello,
On the VPN concentrator, you can use the same network list "X-Local" for the new tunnel as well. If you use that, does it have any issues.
Thanks
Gilbert
09-17-2009 09:57 PM
Yes, i tried it.
I think there is a bug. i will upgrade it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide