Allowing CISCO VPN Client Traffic in ISA Server

Featured Posts

Internet to fall short of IPv4 Addresses soon The word is out and it is official - Internet is going to fall short of IPv4 addresses in the next 500 days or odd. Computer experts and Industry leaders had expressed their warnings earlier but it seems...

Remote Infrastructure Management Services (RIMs) –... Remote Infrastructure Management (RIM) services will be the next growth engine for the offshore service industry as reported by leading consulting agencies and media. In fact, the global RIM industry has...

Xobni – Search and Relationship Toolbar for Outlook This is the best Outlook add-in so far from a company called Xobni located in San Francisco. “Xobni” is basically “Inbox” spelled backwards. The main idea behind the development of this plug-in...

Open Source versus Open Standards Everyone’s talking about open source and open standards now-a-days but hardly have I come across any who knows what exactly it contains and what the importance is. I’m putting this post in my blog...

Installing Exchange Server 2007 SP1 on Windows Server... In this article I've tried to explain how to install or upgrade an organization running on Exchange Server 2003 to Exchange Server 2007 SP1 on a Windows 2008 Server. In the next post I'll be talking about...

Posted on : 01-05-2009 | By : Vishal Vasu | In : ISA Server

Tags: CISCO VPN, ISA server

0

I thought that this might be easy since all that may be required would be allow the IPSec and IKE Client traffic through a rule in ISA. But no it did not work.

To allow a CISCO client via IPSec/UDP to connect through an ISA 2006 firewall, I had to create custom protocol as under:

Port Number: 500
Protocol Type: UDP
Direction: Send Receive

Port Number: 4500
Protocol Type: UDP
Direction: Send Receive

Port Number: 10000
Protocol Type: UDP
Direction: Send Recieve

I added all the ports in one custom protocol defination without Secondary Connections and then added an Access Rule to allow traffic from Internal to External for the above created custom protocol. Problem solved and the connections were now possible.

Share:

Featured Posts