|
GreenNight posted:Cisco is phasing out the IPSEC client. Their solution is the AnyConnect client which is SSL only. They now require you to purchase SSL cals for their PIX to use VPN, where as before IPSEC was "free".
|
#
¿
Oct 2, 2009 09:24
|
|
|
|
| # ¿ Apr 26, 2024 13:48 |
|
|
incoherent posted:You MIGHT get away with XP mode or continuing to use 32bit win7 which is fine for 90% of most end user business applications. Well we are trying to get rid of our old PIX for a couple of other reasons too. Not having to use that silly client anymore would be an additional motivation  Anyways, are there already experiences with using 64bit Windows7 in a corporate environment? I'm pretty free in my decisions, so I'm wondering if I should play it safe with future installations (using 32bit) or take the leap.
|
|
#
¿
Oct 3, 2009 10:34
|
|
|
incoherent posted:You MIGHT get away with XP mode or continuing to use 32bit win7 which is fine for 90% of most end user business applications. Conclusion: I ended up using Win7-32bit and vpnclient-win-msi-5.0.03.0560-k9.exe. In case somebody is having the same problem as I had: Problem: Cisco Client will connect to the VPN, but everything behind it will be unreachable. Reason: Cisco VPN Client is unable to add the correct route. Solution: Start cmd.exe with Admin rights:
|
|
#
¿
Oct 5, 2009 15:26
|
|
|
Xenomorph posted:Vista's UAC and account auto-elevation fixed all the crap that earlier versions of Windows suffered from in regards to account access. I'm dealing right now with a problem where I need to start a process with elevated rights from within powershell. Any ideas how to do this in a non-retarded way?
|
|
#
¿
Oct 8, 2009 07:00
|
|