Re: Cisco VPN client and Outlook
- From: Colin <Colin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Nov 2006 05:42:01 -0800
Hi James,
The Cisco VPN Client can utilise DES, 3DES and AES 128/256 and can also use
DH1,2 and 5 and SHA to create a secure IPSec Tunnel. The built in MS client
is PPTP only (although you can create a L2TP tunnel if you know how to
configure it, however this is unsupported on SBS). The PPTP VPN is insecure
compared to an IPSec tunnel. This is probably why your client's client has
insisted on the change (I can only assume they are now using a Cisco VPN
Concentrator/Pix/ASA device to terminate their VPN's).
The only issue that I am aware of with the Cisco client is that by default
it enables it's own SPI Firewall which runs all the time unless you
specifically turn it off. I believe that this also conflicts with the Windows
Firewall. If it was me, I'd reinstall the Cisco client, disable the firewall
(launch the client, click 'Options' and then click 'Stateful Firewall (Always
On)'. This will remove the 'check' from this option and you may be able to
reconnect your initial VPN config. Hope this helps.
Regards Colin.
"Robert L [MVP - Networking]" wrote:
I have seen similar cases like this one. Cisco believe the Cisco VPN client is more secure and manageable..
1. Remove the Cisco VPN client manually by following this how to.
Cisco How to and issues How to uninstall Cisco VPN client · Cisco Router/Firewall Configuration Samples. Cisco Issues. Can ping from the router but not from inside computers ...
www.howtonetworking.com/Cisco/cisco.htm
2. Try a different Cisco VPN client version. Latest version doesn't mean good. It depends on you Windows OS.
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"James Newman" <jnewman33@xxxxxxxxx> wrote in message news:h0rkl2t5mrun6jlbtq6bkn6lkflb20nbpo@xxxxxxxxxx
Hey all,
I have a client with SBS 2003 SP1 with 2 Nics that has been working
flawlessly for several months.
One of the laptops is taken home each evening and the user connects
using the Connect To Small Business Server icon to establish VPN and
then uses Outlook 2003 for email chores.
Two days ago one of their clients upgraded hardware and told them that
installing the Cisco VPN Client was necessary to establish and VPN
connection with them. My client had previously been using the simple
MS client to connect with them.
After the Cisco client was installed my client took his laptop home
and used the Connect To Small Business Server icon to connect with
his server but Outlook cannot seem to connect with Exchange. It just
endlessly says trying to connect. The VPN still seems to authenticate
ok as there are no errors.
I have had them remove the Cisco client but they still cannot VPN to
their server and connect to Exchange as they did before.
My questions are:
What could the Cisco client have done that would affect the previously
working connection method they used before?
Could it have left behind something that is now preventing the
previously working connection method they used before from working?
Since VPN is not my strong suit, why is the Cisco VPN client required
in some cases when a MS connection can be configured and used?
Thanks for any information,
James
- References:
- Cisco VPN client and Outlook
- From: James Newman
- Cisco VPN client and Outlook
- Prev by Date: MS-DTC...Some vulnerability info required
- Next by Date: Re: Access Denied While Querying the IIS Server NameSpace
- Previous by thread: Cisco VPN client and Outlook
- Next by thread: Just how dumb is Windows 2003 Server for SmallBusiness Server 2003
- Index(es):
Relevant Pages
|
