Tagged with cisco - Community Forum

Shimo 3.0.3 error: Server asked us to download and run a 'Cisco Secure Desktop' trojan http://www.chungwasoft.com/support/community/discussion/180/shimo-3.0.3-error-server-asked-us-to-download-and-run-a-cisco-secure-desktop-trojan Mon, 14 May 2012 18:01:02 -0400 edlitmus 180@/support/community/discussions

Error: Server asked us to download and run a 'Cisco Secure Desktop' trojan.

This facility is disabled by default for security reasons, so you may wish to enable it.

Does anyone know a work around or fix?

]]> Problem with VPN _after_ connecting http://www.chungwasoft.com/support/community/discussion/389/problem-with-vpn-_after_-connecting Mon, 10 Dec 2012 10:23:42 -0500 AndyAkins 389@/support/community/discussions I confess that I am not a network guru, and its possible that this is not Shimo's problem, but something else.

I turned to Shimo because we were having a lot of problems with Lion's native VPN connecting to the two VPNs we're required to use. _When_ the native connected, it worked great - the problem is there would be times (a lot) where it would not connect... we would have to reboot our laptops and try again before it would take. We are connecting, in this case, to a Cisco 3000 VPN Concentrator (so IPSec, not AnyConnect).

Enter Shimo. After instaling it and trying it a few times, we were very pleased that it connected every time. No worries. And ssh'ing and doing most of our work worked perfectly. _Except_:

Using the OSX native, when it connected, we could still browse sites like Google and such - although we were doing it across the vpn network (because their Web Filters would occasionally block some sites, we have no such filters on our network).

Using Shimo, we can no longer do this. We can connect to all internal (secure) network sites, but for some reason, we're not getting through to outside sites.

]]> Could not write the required config file. http://www.chungwasoft.com/support/community/discussion/365/could-not-write-the-required-config-file. Tue, 16 Oct 2012 14:31:31 -0400 johntdyer 365@/support/community/discussions I get the following when I try to get Shimo to use the OSX VPN Client:

2012-10-16 14:29:21.502 Shimo[69105:c07] Requesting Authentication for Modes: 16382 / 6172 (NUAuthenticationController.m:524)
2012-10-16 14:29:21.502 Shimo[69105:c07] Modes after Profile check: 8188 / 6172 (NUAuthenticationController.m:547)
2012-10-16 14:29:21.631 Shimo[69105:c07] Modes after Keychain check: 8184 / 6172 (NUAuthenticationController.m:553)
2012-10-16 14:29:36.752 Shimo[69105:c07] NOTIFICATION: Could not write the required config file. (NUShimoFunctions.m:26)

This is on Shima 3.2.2 on OSX 10.8. Anyone have any idea what this is about?

-John

]]> Disconnects every 50 minutes or so http://www.chungwasoft.com/support/community/discussion/251/disconnects-every-50-minutes-or-so Thu, 09 Aug 2012 17:03:58 -0400 mdzwarts 251@/support/community/discussions I'm using Nat Traversal, IPSec over TCP. Backendservice vpnc (open source alternative). Group authentication. No cisco client installed.

In 10.6 and 10.7 native, disconnectivity issues could be fixed by fooling racoon in /var/run/racoon, but in 10.8 this seems to be quite different again. So both Shimu and the internal racoon are not really working well for me.

]]> Connection stalling with vpnc http://www.chungwasoft.com/support/community/discussion/202/connection-stalling-with-vpnc Tue, 10 Jul 2012 16:39:13 -0400 bafflegab 202@/support/community/discussions When I am connected to certain sites via IPSec (vpnc), things seem to work normally up to a point, but then different activities will cause connections to stall, and some to not work at all. I just upgraded to 3.0.10 over the weekend, but I also had this problem with v2.x.

Example: I can ssh into a host and navigate around, but when I do an 'ls' in a directory with a lot of files or run a program like top, the connection stalls and is basically dead. An MSTS connection usually works fine over the same tunnel, but connecting to web GUIs (like VMware ESXi host page) usually does not. If I disconnect and connect with the Cisco VPN client, everything works fine.

The common factor appears to be connecting to an ASA, but not all ASAs. Oddly, on some of the ASAs that are working, the ASA is logging that my client has sent oversize chunks or packets, but I experience no problems. On the ASAs that aren't working, I don't see this message, I just have the problem.

For one bad site, I tried to switch to the MacOS X backend, but it doesn't seem to work at all - when I can get it to connect, it doesn't set up a proper route for 10.0.0.0/24 (the primary remote LAN) and sets up 10.0.0./31 instead. Is that a known issue?

My suspicion is that this is a problem with vpnc detecting the tunnel-MTU with certain versions of ASA. Are there any parameters to pass to vpnc that can override the detected MTU for the tunnel, or another way to troubleshoot what's going on?

]]> MacOS X internal VPN killed by Shimo 3.0.3 install http://www.chungwasoft.com/support/community/discussion/179/macos-x-internal-vpn-killed-by-shimo-3.0.3-install Mon, 14 May 2012 16:58:22 -0400 mschicker 179@/support/community/discussions After entering all passwords and passphrases the connection runs through, but no target machine can be reached at all (by IP)

2012-05-14 22:55:36 State changed to: Contacting

2012-05-14 22:55:36 State changed to: Negotiating

2012-05-14 22:55:36 Password:

2012-05-14 22:55:37 State changed to: Connected

2012-05-14 22:55:37 Bound to address 192.168.14.191

2012-05-14 22:55:38 phase1_up starting...

2012-05-14 22:55:38 UNIQUE_IDENTIFIER = 4DEBA03E

2012-05-14 22:55:38 LOCAL_ADDR = 172.20.10.2

2012-05-14 22:55:38 LOCAL_PORT = 4500

2012-05-14 22:55:38 REMOTE_ADDR = 87.145.52.***

2012-05-14 22:55:38 REMOTE_PORT = 4500

2012-05-14 22:55:38 DEFAULT_GW = 172.20.10.1

2012-05-14 22:55:38 INTERNAL_ADDR4 = 192.168.14.191

2012-05-14 22:55:38 INTERNAL_DNS4 = 192.168.14.3

2012-05-14 22:55:38 INTERNAL_DNS4_LIST = 192.168.14.3

2012-05-14 22:55:38 INTERNAL_WINS4 = 192.168.14.3

2012-05-14 22:55:38 INTERNAL_WINS4_LIST = 192.168.14.3

2012-05-14 22:55:38 INTERFACE = en0

2012-05-14 22:55:38 Up to two 'No such key' warnings are normal and may be ignored

2012-05-14 22:55:38 Saved the DNS and WINS configurations for later use

If I try now to use the Mac OS original VPN feature it only comes up with "An unrecoverable error occured. Verify your settings a try reconnecting." In system log the following messages appear:

14.05.12 22:54:27,844 configd: IPSec connecting to server video.c-s-s.de

14.05.12 22:54:27,844 configd: SCNC: start, triggered by System Events, type IPSec, status 0

14.05.12 22:54:28,055 configd: IPSec Controller: cannot connect racoon control socket (errno = 61)

14.05.12 22:54:28,055 configd: IPSec Controller: cannot create racoon control socket

14.05.12 22:54:28,055 configd: IPSec Controller: restart failed

14.05.12 22:54:28,056 configd: IPSec disconnecting from server 87.145.52.187

So I cannot use any VPN connection anymore -> worst case!

Please help me out, what did go wrong? And why is my MAC OS X VPN broken?

Kind regards,

Markus

]]> Shimo 3 vpnc vendor configuration http://www.chungwasoft.com/support/community/discussion/165/shimo-3-vpnc-vendor-configuration Thu, 03 May 2012 09:51:05 -0400 tsw 165@/support/community/discussions

I've upgraded to Shimo3 (3.0.2) and it seems that the old config that I've had no longer works with this version (worked well on 2.x).

I believe the problem is with the "Vendor cisco" configuration in expert view. The endpoint is a juniper device and it seems it is quite picky about that.

If I try to change the expert config to "Vendor netscreen" it will duplicate the "Vendor" setting with both cisco and netscreen set.

Running vpnc from cli works correctly and I get the same error messages (Rejected and IKE packet on .... from .... to ... with cookies .... and .... because an Initial Phase 1 packet arrived from and unrecognized peer gateway.) if I change the Vendor setting in the vpnc config file.

Any ideas?

]]> Beta on Lion, Cisco unavailable on 32bit http://www.chungwasoft.com/support/community/discussion/133/beta-on-lion-cisco-unavailable-on-32bit Mon, 26 Mar 2012 17:56:15 -0400 hugedilmna 133@/support/community/discussions Hello,

I'm using Lion and trying the beta. I'm booted up in 32bit mode but getting the following message:

Cisco API Unavailable

You have the CiscoVPN software installed on your computer, but it is unavailable in 64 bit mode. If you still want to use CiscoVPN connections, you can either use Shimo's alternative backends or reboot your computer in 32 bit mode.

Shimo 2 DOES work with Cisco without issue.

I confirmed I'm booted in 32bit mode using uname.

root:xnu-1699.24.23~1/RELEASE_I386 i386

Am I missing something?

]]>