[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 394
  • Last Modified:

Issues Configuring ASA5505 with 8.3

All,

I have got an issue with a new Cisco ASA5505 that has come with version 8.3.

It is completely different and I am having issues with it.

Basically my issue at the moment is with NAT's and access to internal resources to translated addresses from External Sources.

Basically I have setup a Citrix Web Interface and I want to access this from remote sources (which I do with all my other sites with Cisco ASA but using 8.2),

So I have sort of worked out you put the translation on the object rather then creating a NAT rule, and I have confirmed this doing a www.whatismyip.com on the server in question.

I have the following bits of config which relate to this setup :

object network citrix
 host 192.168.108.14
object network citrix-ext
 host 18.141.70.14

object network citrix
 nat (any,any) static citrix-ext

access-list outside_access_in extended permit tcp any object citrix eq www

Which is what I normally do but it doesnt work, can anyone help?

Thanks

Paul
0
essexboy80
Asked:
essexboy80
  • 3
  • 3
1 Solution
 
JFrederick29Commented:
Your access-list should reference the external IP address:

access-list outside_access_in extended permit tcp any object citrix-ext eq www
0
 
essexboy80Author Commented:
Are you sure, doesnt make any difference, I know pre 8.3 it was external but i read something that said use the non-translated address in your access rules with 8.3 and above
0
 
JFrederick29Commented:
Ahh, yeah, I think I read that also.

Did you apply the access-list to the outside interface?

access-group outside_access_in in interface outside

Can you connect to 192.168.108.14 on port 80 from the inside network?
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
StrifeJesterCommented:
What other ACLs are running you may also have to allow the traffic outgoing from the internal interface.  I know the way I have my ASA setup I block everything except the NAT traffic so I have to create outgoing rules on my internal interface because the traffic is translated static instead of via the NAT rule.  Not sure if there is something like this they have changed in 8.3.  So you have to create the translation, allow incoming on the outside interface and also all outgoing on the inside interface.
0
 
essexboy80Author Commented:
AStill having issues
0
 
JFrederick29Commented:
You applied the access-list to the outside interface, right?

access-group outside_access_in in interface outside
0
 
essexboy80Author Commented:
all sorted thanks
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now