Advertisement

12.25.2007 at 06:58AM PST, ID: 23042315
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.8

Restricting user access to LAN Hosts - Pix VPN Client through IAS Radius

Asked by theoaks in Virtual Private Networking (VPN), IPSec Security Protocol, Cisco PIX Firewall

Tags: , , , ,

I have currently a pix 506e 6.3 with an internal radius/ias doing the user authentication for Cisco VPN clients. The pix is setup so that there are two VPN groups each with a different ip pool, and my acl's allow the different pools to have different access to the internal network:

POOL1 (10.10.10.0/24) can access all internal hosts using
"access-list 101 permit ip 192.168.1.0 255.255.255.0 10.10.10.0 255.255.255.0"
POOL2 (10.1.1.0/24) can access only 192.168.1.20 using
"access-list 101 permit ip 192.168.1.20 255.255.255.255 10.1.1.0 255.255.255.0"

This all works fine but.... is it possible to make the access policy to work based on the AD account rather than which vpngroup the user is accessing? I dont know if what ive done above is the proper way to do it, i just sort of through it all together based on what little knowledge i have - and it does work, but i would prefer to have one ip pool and all users using the one pool but access granted based on their account, not their ip range they get from the pool.

If not, thats fine but any other ideas are welcome.

ThanksStart Free Trial
 
Loading Advertisement...
 
[+][-]12.25.2007 at 08:33AM PST, ID: 20527420

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 14-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]12.25.2007 at 02:27PM PST, ID: 20527890

View this solution now by starting your 14-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Virtual Private Networking (VPN), IPSec Security Protocol, Cisco PIX Firewall
Tags: vpn, access, client, ias, lan
Sign Up Now!
Solution Provided By: lrmoore
Participating Experts: 2
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-43 / EE_QW_2_20070628