cisco systems vpn client tags: help desk
misterhaan
radar
|
subject: cisco systems vpn client
posted: 2:00:30 pm, oct 02, 2006
first of all, this is the only software i've ever installed that requires the folder it put in the start menu to still be there in order to run. thankfully you can at least set it to hidden so it doesn't show up. but i've known about that for years now. the new problem is that i've now installed cisco's vpn client on computers running agnitum's free outpost firewall, which causes problems. specifically, after connecting to work with the vpn client, i was unable to access anything at work unless i shut down outpost. so that worked, but it's annoying to shut it down all the time and i also want it to run -- that's why i installed it! after disconnecting from vpn, starting up outpost again tells me that i have other firewall software installed, and having two firewalls can either allow access for everything, deny access for everything, or cause basically any other problem you could imagine. since outpost is a nice program (very unlike cisco vpn), it offers details on what it found. apparently i have something from zone labs running under the service name "vsdatant" which outpost says it probably won't work with. i check services, and nothing that shows there is named vsdatant, so i open up a command prompt. "net stop vsdatant" gives me an error saying that it cannot be stopped (what?!?) but at least i know the service exists. "sc query vsdatant" tells me it thinks it's a kernel driver and that it can't be stopped or paused. turns out it can be deleted though! "sc delete vsdatant" and a reboot has solved my problem! surprisingly (and thankfully!), cisco vpn client doesn't care if you delete its firewall service even though it freaks out if you delete its start menu folder. please note that the above post is likely made up in its entirety. |
pm
www
quote|
misterhaan
radar
|
subject: re: cisco systems vpn client
posted: 1:03:43 pm, apr 24, 2007
the vpn client seems to re-create this service unless you delete / rename / move the files it uses. those files are vsdata.dll, vsdatant.sys, and vsinit.dll in %systemroot%\system32. edited by misterhaan, 1:04:03 pm, apr 24, 2007 please note that the above post is likely made up in its entirety. |
