Improve company productivity with a Business Account.Sign Up

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

Web access crawling on non-default port, something lost in translation?

Group,
Wanted to ask you a question, we have a apache server that is a dev box we are using right now. We already had a webserver on another IP (.3) running on port 80. This is correctly mapped and everything is working great. The Apache server we are running (.6) we changed to port 81 and internally everything works great. I added this to our ACL and our static mappings, however access from the outside CRAWLS, on Firefox you can see on the bottom "connecting to 192.168.0.6" and it seems as if it is having a very hard time loading images. What do you guys think?

Update, something interesting, keeping in mind I am outside the firewall so I have to type www.domain.com:81 which is in the 24.73.166.x block. If I click on a link I am getting a "connection timed out" error saying the server at 192.168.0.6 is taking to long to respond, shouldn't this be my outside IP address, do I have a mapping backwards?
0
blakmoon91
Asked:
blakmoon91
  • 3
  • 2
1 Solution
 
prueconsultingCommented:
Post your static statements and acls which are applicable.

Also did you do a clear xlate following updating the rules and the statics

0
 
blakmoon91Author Commented:
No, I didn't clear the xlate, I will have to remember that. I will post the ACL's and Static when I get back tonight
Thanks for the response.
0
 
Keith AlabasterEnterprise ArchitectCommented:
Assuming it is a pix, should look like this for the second server

static (inside,outside) tcp interface 81 192.168.0.6 81 netmask 255.255.255.255 0 0
access-list outside_access_in permit tcp any interface outside eq 81
access-group in interface outside
0
Increase Security & Decrease Risk with NSPM Tools

Analyst firm, Enterprise Management Associates (EMA) reveals significant benefits to enterprises when using Network Security Policy Management (NSPM) solutions, while organizations without, experienced issues including non standard security policies and failed cloud migrations

 
blakmoon91Author Commented:
Here are the statements as I have it in my Pix 6.3(5)

access-list outside_access_in permit tcp any host 24.73.166.50 eq 81

and

static (inside,outside) tcp 24.73.166.50 81 192.168.0.6 81 netmask 255.255.255.255 0 0

I just re-applied the group and cleared the xlate, I will let you know if it made a difference tomorrow.
0
 
prueconsultingCommented:
That should work just fine for you.. clearing the xlate is an important step to making it function proprely
0
 
blakmoon91Author Commented:
Group,
Thanks for all the response, I was able to work out the issue, however it was actually un-related to the Pix. I do however agree that anytime you apple or re-apply a access-group you need to be sure to clear the xlate, a step that I had forgotten. I do appreciate your time!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

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