any free VPN Client Software (64 bit)?

[mountainman]

We use the Cisco stuff at work, but their client software doesn't work with 64 bit OS.

Anyone know of one I can use for free? I just have to connect once to get my OUtlook/Exchange "handshake" and then I don't need it anymore.

Thanks!

[mountainman]

BTW - Shrew Soft VPN Client on Win7 64-bit means BSOD.

You have to uninstall from the install folder since it doesn't appear in the program list.

[Mark]

http://sourceforge.net/search/?type_...&search=Search

maybe look here ?

[YeOldeStonecat]

Which Cisco appliance is used? The models that support SSL VPN work with 64 bit. Also the IT guy can fall back and setup a PPTP VPN for you.

There used to be a free version of Greenbow IPSec VPN client, dunno if it's still floating around out there.

If this is just for Outlook, they're not going chase down Outlook over http?

[mnosteele52]

Gbridge

[Shinobi]

Dont know how good this one is...

http://www.start64.com/index.php?opt...3207&Itemid=75

[YeOldeStonecat]

Gbridge

Doubt that would interface with an ASA though.

[mountainman]

I honestly don't know the different types/conenctions of a VPN. For some reason, you have to use the VPN software once when setting it up so it'll pull down the username/password and then finally connect. (Yes, even though it's done over HTTP.)

Again...this is the crappy setup at the office that has no "real" IT guy, so I really have no one to ask/complain to. I just need to make it work.

I have the following to make the connection (from the Cisco software):

IP address
Group Auth (not certificate): name / password
User (once connected): name / password

I'll try the posted stuff. Thanks!

[mountainman]

Greenbow

http://www.thegreenbow.com/vpn_down.html

Win7 64 bit > right click and compatibility mode

Trying it now...

[YeOldeStonecat]

I honestly don't know the different types/conenctions of a VPN. For some reason, you have to use the VPN software once when setting it up so it'll pull down the username/password and then finally connect. (Yes, even though it's done over HTTP.)

Oh..you're still doing in Outlook over HTTP? That's a common mis-understanding, that you have to be connected to the LAN with the Exchange Server the first time you set it up.



From a remote computer that has never joined the domain, say some Windows XP Home computer at someones home...you can still setup Outlook over HTTP.

Must import certificate first, via browser. And then steps pretty much like in the link below.

If the IT guys setup Exchange so that OWA is working, then they have port 443 open/forwarded..and that's the only firewall rules on the host end they need to do for Outlook over HTTP. Nothing further except going through a few steps to configure Exchange to allow Outlook over HTTP to connect. Since they've done that already....

http://www.petri.co.il/configure_out..._over_http.htm

"RPC over HTTP/S is a cool method for connecting your Outlook 2003 client to the corporate Exchange Server 2003 from the Internet or WAN, without the need to establish a VPN session to the corporate LAN and/or needing to open many ports on your corporate firewall. The only ports you'll need to open on your firewall are TCP 80 and, if using SSL, TCP 443."

I never do port 80, only 443. Port 80 gets gang raped on a daily basis, security hole.

[mountainman]

Hmmm... well, a guy I work with sent me a config file to load into the VPN software that got me connected and all was well.

Well, until after I was done and shut down the VPN software and it gave me yet another BSOD. Good grief.

Cat - If they ever talk about doing some external IT, you'll get the call.