by wintpe » Aug 17th, '13, 16:36
ok.
can i ask does this problem only come about when the cisco vpn is loaded or is it always.
in case you missed the line that said, cisco vpn brings up rules to block local access.
so lets say that your cisco vpn is not quite setup right and your local access gets blocked as soon as you
load cisco vpn that may be the perception.
have you tried disabling the systems firewall before you bring up the vpn, because if the cisco vpn which uses port 5000 by
default to reach the listening daemon at your emploers site cant get there, then the vpn tunnel may never let any traffic through.
also with routing , its a two way thing, ie you have a route that says where your traffic should go, ie through the tun0 device or whatever cisco uses these days, but the other end also needs a route back.
telnet can usualy tell if theres a route there but not back, as if it hangs, but does nothing else it will usualy indicate the route there is ok, if its says destination unreachable, then it usualy indicates that the route there is at fault, you can use telnet with almost any port on the other end, as you can with a similar tool "nc" or netcat
regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.