• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

pix 501 config, all outbound ok except the server we have published behind firewall

Hi

I have pasted my pix config below, we basically have published out internal server 192.168.2.1 using static IP x.x.161.181

Pix internal IP 192.168.1.253
External IP x.x.161.180


All internal clients can get outbound access except the server i have published, i have know it is somthing to do with the Intenal IP address, as on my laptop i use any other internal address and i can get out, if i unplug the server and give my laptop the 192.168.2.1 address i cant.

Can anyone tell me what i need to add to my config to allow the servers internal ip acess outbound.

Thanks



interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password DQV8Tvl2R67oouiO encrypted
passwd jqdejBcg8QL9AUjH encrypted
hostname pixfirewall
domain-name ciscopix.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list ACL_OUT permit tcp any host X.X.161.181 eq 3389
access-list ACL_OUT permit tcp any host X.X.161.181 eq smtp
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside X.X.161.180 255.255.255.248
ip address inside 192.168.1.253 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 0.0.0.0 255.255.255.255 inside
pdm location 192.168.1.87 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) X.X.161.181 192.168.1.2 netmask 255.255.255.255 0 0
access-group ACL_OUT in interface outside
route outside 0.0.0.0 0.0.0.0 X.X.161.177 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 192.168.1.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
Cryptochecksum:822471119b9ad453778220a9a3f90e03
: end
pixfirewall#
0
higgsy
Asked:
higgsy
2 Solutions
 
nodiscoCommented:
<<we basically have published out internal server 192.168.2.1 using static IP x.x.161.181
<< if i unplug the server and give my laptop the 192.168.2.1 address i cant

Are these typos?  Your static is to 192.168.1.2 - not 192.168.2.1 - and the inside range is 192.168.1.0/24
As you can imagine - 2.1 is not going to work at all - unless it is on a different network inside the PIX and you need a route statment to the pix from the router and the router to the pix.

PLS advise

Have you typed clear xlate since you added the static:  You may just need to wipe the translation table for it to take effect :
On the pix :

clear xlate

hth

0
 
higgsyAuthor Commented:
sorry thats a typo, just to confirm

The Internal of the pix is 192.168.1.253
External of pix is x.x.161.180

Internal IP of server is 192.168.1.2
static mapping x.x.161.181

i will try the xlate command

Thanks

0
 
zyclonixCommented:
Make sure return traffic is being directed to your PIX by the adjacent router by adding a route. Also, make sure that the arp entry on the router for the 161.181 IP has the same mac address as 161.180
0
 
lrmooreCommented:
zyclonix has a good point about arp entries.
I looked for this in your PIX and didn't see it
  sysopt noproxyarp outside  <== this would give the symptoms you describe

You may want to reboot the router if you have one, or even the PIX. Some versions of PIX OS are buggy in that once you create a static you must reboot for it to really take effect.


0
 
zyclonixCommented:
Use the "show arp" command on the pix to see your arp table. I don't know what it would be on your router, it depends on the type.

You may need to debug to find out the answer to this one. First choose a website that resolves to only one IP address. Then plug it into the deug command as such:

debug packet dst <ip address>
debug packet src <ip address>

Then browse to the site and see what output you get.

If you only see packets going out with nothing coming in, then you either have an ARP issue or a routing issue.

If you are seeing bi-directional packets pay special attention to the NATing. It's possible you are NATing to the 161.180 in the outbound direction and the 161.181 in the inbound.

Don't forget to turn debugging off when you're done.
0

Featured Post

Rewarding opportunities for women in IT

Across the nation, technology jobs are vacant because there aren’t enough qualified professionals to fill them. With a degree from WGU, you can get the credentials it takes to become an in-demand IT professional. Plus, WGU’s IT programs include industry certifications.

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