Citrix Client Access Through ISA 2004 via Cisco VPN

We have a user who needs to access Citrix at a remote site.  The IT team at the remote site installed the Citrix software, a VoIP Softphone and a Cisco vpn client.

At our local site we have a PIX501 sitting in front of ISA2004 (inside SBS2003) so all our outbound traffic goes through ISA then the PIX.  I created an ISA allow rule (name : Cisco Outbound) for Cisco vpn protocols and now the user can make the vpn tunnel.  He can now connect to their VoIP PBX and make/receive calls via the softphone, so from this i believe the ISA 'Cisco Outbound' rule is working just fine as traffic is moving fine.

Now when the user tries to connect to Citrix (this is configured to look for the remote site internal ip), open opening Word 2007 he receives an error :

'Cannot connect to the Citrix Presentation Server'

I created a rule (Citrix Outbound) to allow internal>External access to the ICA protocol (TCP 1494 / UDP 1604). I can ping the two IP remote internal addresses set in the Citrix settings, however when i try to telnet to port 1494 i don't have a success.  I watch ISA monitoring and can see that 'Cisco Outbound' connects fine but then 'Citrix Outbound' rule 'initialise connection' shows for port 1494 to the remote internal ip address but after 10-20 seconds the connection is closed. There is currently no 'denied connection' or other error, just two lines one to initialise, one to close.

If we simply right click the ISA firewall client on the user laptop and click disable the firewall client, cisco vpn connects (activity shown in ISA monitor) and telnet works just fine (i see ICAICAICAICA in the window) but no activity to monitor in ISA relating to the telnet.

If we disconnect the user from our domain and he uses 'another' internet connection (that avoids our ISA server) then everything works as it should.

So process of elimination suggests ISA is causing problems here, what do i need to do to resolve ?

Couple of questions ..

1) Should i be seeing in ISA the traffic that should be 'inside' the Cisco vpn ? (ie the traffic to the remote internal server ip) ?

2) What else needs setting in ISA to allow ICA to fully communicate 'back home' ?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Get rid if the "Citrix Outbound Rule".  This traffic does not "use" the ISA.
The root of the problem,...You did not add the "Remote Internal IP Range" to the ISA's Internal Network Defintion.
ISA does not "route" this traffic,...the local "VPN Client" on the user's machine does,...ISA never "sees" the traffic inside the Tunnel, therefore the ISA can't possibly make decisions about the traffic.  By adding the remote internal ip range to the Internal Network keeps the Firewall Client running on the user's machine from "getting in the way".
So process of elimination suggests ISA is causing problems here, what do i need to do to resolve ?
ISA is not the problem,...the Client is the problem becuase it s sending the traffic to the ISA when it is not supposed to, is supposed to pass the inner-tunnel traffic into the local Cisco VPN Client which then in thrun "inserts" the traffic into the Tunnel.  The ISA is not supposed to be involved, does not know what to do the the "inner-tunnel traffic",..and it is not supposed to know, is never supposed to see it.  
So add the remote internal private ip range to the ISA's internal Network Defintion so that the Firewall Client on the user's machine will respond correctly by just simply "staying out of the way".

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bbgdistAuthor Commented:
So i guess i was barking up the wrong tree, or at least the one next to the solution!

i have added the additional ip range to the ISA internal network range and can now telnet to remote ip port 1494 successfully with the firewall client 'enabled, so all that remains is to test the citrix itself when the user returns to the office later today.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Forefront ISA Server

From novice to tech pro — start learning today.