Discussion
Nooo. Don't use the std OS client (it will require modification to the end system (firewall/concentrator) and you'll lose a lot of functionality. For example, the Cisco client supports NAT'd client addresses without breaking IPSEC.
As for the client, I may have a copy somewhere but AFAIK, Cisco insist that it is not distributed outside the organisation which signed an agreement with them (something to do with exporting the encryption technology used in the product).
As for the client, I may have a copy somewhere but AFAIK, Cisco insist that it is not distributed outside the organisation which signed an agreement with them (something to do with exporting the encryption technology used in the product).
Hmmm, have you considered this may not be a VPN related issue at all? Things to check are:
1) If you're authenticated and have a VPN session established (check for the padlock on the task bar), you should be allocated an IP address on the internal network. Can you confirm that?
2) Can you ping any other machines on the same subnet (such as a router or the concentrator itself?).
3) If you can ping a router on the same subnet, how about another device on another subnet
4) If you can do all 3 above it's likely to be a Windows name resolution issue (assuming you're using Windows of course!).
5) If it's not a Windows problem and you do 2 and most of 3 it'll either be routing or split tunnelling which is setup incorrectly!
Darren.
edited to add: some more information about your setup would be useful. i.e what device are you using to terminate the tunnel, what client OS are using, what is the VPN tunnel for etc etc.
>> Edited by _DJ_ on Sunday 14th March 14:17
>> Edited by _DJ_ on Sunday 14th March 14:18
1) If you're authenticated and have a VPN session established (check for the padlock on the task bar), you should be allocated an IP address on the internal network. Can you confirm that?
2) Can you ping any other machines on the same subnet (such as a router or the concentrator itself?).
3) If you can ping a router on the same subnet, how about another device on another subnet
4) If you can do all 3 above it's likely to be a Windows name resolution issue (assuming you're using Windows of course!).
5) If it's not a Windows problem and you do 2 and most of 3 it'll either be routing or split tunnelling which is setup incorrectly!
Darren.
edited to add: some more information about your setup would be useful. i.e what device are you using to terminate the tunnel, what client OS are using, what is the VPN tunnel for etc etc.
>> Edited by _DJ_ on Sunday 14th March 14:17
>> Edited by _DJ_ on Sunday 14th March 14:18
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff