Trying to make JIRA accessable from the public Internet

I am trying to get our JIRA server to b e accessible from the public internet.  I have done the following:
1.       The jira server is on a hyper-v vm.  It has a network connection to the internal network.  Its host server has LAN connections to the internal network and the DMZ.
2.      I can access the jira webpage in the internal network
3.      I have registered a DNS A record with the name nsca-jira.nsca-lift.org
4.      I created a and OUTSIDE incoming rule on my Cisco 5505 ASA allowing HTTP traffic from the IP registered with the DNS record.
5.      I created a DMZ incoming rule allowing HTTP traffic from the Host server DMZ LAN connection to the Jira Server IP.
6.      Jira uses Tomcat instead of IIS, we have pointed Tomcat to the internal IP of the Jira server.
I can’t reach the server from the public internet I am not sure what I need to do next or if what I have done is correct.  This is the first time I have tried to connect a server to the public internet.  Any help would be appreciated.
nsca_mitchAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Hypercat (Deb)Commented:
You've allowed the incoming traffic, but you have to bind that external IP address to the internal IP address being used by the JIRA server so that the router knows what internal server should be receiving that traffic.  I don't know how specifically to do this on a Cisco ASA, but here's a web post that might help you out:

http://ciscoconfigs.net/index.php?option=com_content&task=view&id=19&Itemid=26
0
Paul_McClureCommented:
Have you created a NAT rule for the server?

eg if your WAN address is 1.1.1.1

static (Inside,Outside) tcp 1.1.1.1 https JIRA-SERVER https netmask 255.255.255.255
0

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
nsca_mitchAuthor Commented:
After creating a NAT rule in the ASA it works
0
nsca_mitchAuthor Commented:
it worked
0
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
Networking

From novice to tech pro — start learning today.