Cisco 501 - redirection problem

Hi!

I have made a port redirection on my PIX 501, but it only works when the connections comes from the outside. When I tries to ping etc. the server ip (192.168.1.40) from the LAN it doesn't work. Then sometimes I and can ping and use the server normaly on the LAN but after 5min it's down again. In the down periods it still works from the outside.

Can anyone help me??

The config is:

Building configuration... : Saved : PIX Version 6.3(5) interface ethernet0 auto interface ethernet1 100full nameif ethernet0 outside security0 nameif ethernet1 inside security100 hostname Frost domain-name ciscopix.com clock timezone CEST 1 clock summer-time CEDT recurring last Sun Mar 2:00 last Sun Oct 3:00 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 name 192.168.2.0 VPN access-list inside_cryptomap_dyn_20 permit ip any interface inside access-list outside_access_in permit tcp any host 172.21.3.66 eq ftp access-list inbound permit udp any host 192.168.1.40 eq 21 access-list inbound permit tcp any host 192.168.1.40 eq ftp access-list 101 permit tcp any host 172.18.124.99 eq ftp pager lines 24 mtu outside 1500 mtu inside 1500 ip address outside 172.21.3.66 255.255.255.0 ip address inside 192.168.1.1 255.255.255.0 ip audit info action alarm ip audit attack action alarm ip local pool VPN-pool 192.168.1.200-192.168.1.210 pdm location VPN 255.255.255.192 outside pdm location 192.168.2.192 255.255.255.224 outside pdm location 192.168.2.96 255.255.255.240 outside pdm location VPN 255.255.255.0 outside pdm location 192.168.1.40 255.255.255.255 inside pdm logging informational 100 pdm history enable arp timeout 14400 global (outside) 1 interface global (inside) 22 192.168.1.40 nat (inside) 1 0.0.0.0 0.0.0.0 0 0 static (inside,outside) tcp interface ftp 192.168.1.40 ftp netmask

255.255.255.255 0 0 access-group outside_access_in in interface outside route outside 0.0.0.0 0.0.0.0 172.21.3.1 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 TACACS+ (inside) host 192.168.1.1 1234 timeout 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 sysopt connection permit-ipsec crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac crypto dynamic-map inside_dyn_map 20 match address inside_cryptomap_dyn_20 crypto dynamic-map inside_dyn_map 20 set transform-set ESP-AES-256-MD5 crypto dynamic-map outside_dyn_map 20 set transform-set ESP-AES-256-MD5 crypto map inside_map 65535 ipsec-isakmp dynamic inside_dyn_map crypto map inside_map client authentication LOCAL crypto map inside_map interface inside crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map crypto map outside_map interface outside isakmp enable outside isakmp enable inside isakmp policy 20 authentication pre-share isakmp policy 20 encryption aes-256 isakmp policy 20 hash md5 isakmp policy 20 group 2 isakmp policy 20 lifetime 86400 isakmp policy 40 authentication pre-share isakmp policy 40 encryption aes-256 isakmp policy 40 hash md5 isakmp policy 40 group 5 isakmp policy 40 lifetime 86400 vpngroup VPN address-pool VPN-pool vpngroup VPN split-tunnel inside_cryptomap_dyn_20 vpngroup VPN idle-time 1800 vpngroup VPN password ******** telnet timeout 5 ssh timeout 5 management-access inside console timeout 0 dhcpd address 192.168.1.2-192.168.1.33 inside dhcpd dns 192.168.1.1 194.239.134.83 dhcpd lease 3600 dhcpd ping_timeout 750 dhcpd auto_config outside dhcpd enable inside terminal width 80 Cryptochecksum: : end [OK]
Reply to
frostware
Loading thread data ...

Hi,

The configuration is neat. Can you elaborate your problem.

The normal lan would be lan---------PIX--------internet. So, the ftp 1.40 server is in the lan and pc from the same lan will not go to the PIX to go to the ftp server. I hope you are not trying call the ftp server by the public ip address of the PIX. don't try that, it can not be done because ASA wont let you do it.

-Vikas

Reply to
sampark

hi,

i examined the configration. i saw some things.

-"global (inside) 22 192.168.1.40" :i think this statement is unnecessary. because you defined the inside for all ip.

-"static (inside,outside) tcp interface ftp 192.168.1.40 ftp netmask

255.255.255.255 0 0" in this statement, you type the interfaces ip address, as that "static (inside,outside) tcp xxx.xxx.xx.xx ftp 192......" and than test it.

and finally, you try the configration without access-lists. if work it, after insert the access-list to config.

formatting link
regards..

Reply to
-

You put the finger on it.

This line have no use , but it assign the IP 192.168.1.40 on the inside interface.

This meen you have two devices with the same IP on your network . It explains why it sometimes works and sometime don't. Your arp cache gets populated with the wrong MAC. When it doesn't work , do a arp -a on the client PC , and you will probably see the PIX inside MAC address associated with 192.168.1.40

Reply to
mcaissie

I'm not that good at Cisco, but what you say is:

1 - remove the line "global (inside) 22 192.168.1.40" (how do I do that?) 2 - replace the "static (inside,outside) tcp interface ftp 192.168.1.40 ftp netmask 255.255.255.255 0 0" with "static (inside,outside) tcp xxx.xxx.xx.xx ftp 192......" 3 - test it
Reply to
frostware

Just add "no" in front of the line in configuration mode

no global (inside) 22 192.168.1.40

From a PC on the inside open a prompt and flush the arp cache

arp -d *

then try to ping 192.168.1.40

IMHO you don't have to modify the second line

Reply to
mcaissie

After removing the line it seems to work but I will test some more...

In the meantime can you check the firewall setup in the config? Is it safe? Are there some bugs?

Reply to
frostware

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.