sat444
asked on
pix 501 ftp problem
Experts,
I just recently built a sever using Windows Server 2008 R2 and set up an FTP site using IIS 7.0.
The server currently lives behind a pix 501 firewall. From any machine behind the pix 501 I can ftp to the site and also connect via telnet ( telnet X.X.X.9 21) with no problems. When i try to do both these tests from outside the firewall it just kind of hangs and then stops trying.
I can remote desktop to the server without problems either.
I am a basic pix user but I would appreciate any advice as to why it might be failing.
Also, if you see any glaring problems in my config ( see below) I would appreciate you pointing them out as well.
Thanks
John
time(config)# show run
: Saved
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
hostname time
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 timewarner permit icmp any any
access-list timewarner permit tcp any host X.X.X.10 eq 3389
access-list timewarner permit tcp any host X.X.X.9 eq ftp
access-list timewarner permit tcp any host X.X.X.9 eq ftp-data
pager lines 24
logging on
logging timestamp
logging trap warnings
icmp deny any outside
mtu outside 1500
mtu inside 1500
ip address outside X.X.X.11 255.255.255.128
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
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.X.10 192.168.1.50 netmask 255.255.255.255 0 0
static (inside,outside) X.X.X.9 192.168.1.49 netmask 255.255.255.255 0 0
access-group timewarner in interface outside
route outside 0.0.0.0 0.0.0.0 X.X.X.1 1
timeout xlate 3:00: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 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 timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.30 inside
dhcpd dns 24.25.5.60 24.25.5.61
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:a2542b5249f e802323acc 89a19ddc28 2
: end
time(config)#
I just recently built a sever using Windows Server 2008 R2 and set up an FTP site using IIS 7.0.
The server currently lives behind a pix 501 firewall. From any machine behind the pix 501 I can ftp to the site and also connect via telnet ( telnet X.X.X.9 21) with no problems. When i try to do both these tests from outside the firewall it just kind of hangs and then stops trying.
I can remote desktop to the server without problems either.
I am a basic pix user but I would appreciate any advice as to why it might be failing.
Also, if you see any glaring problems in my config ( see below) I would appreciate you pointing them out as well.
Thanks
John
time(config)# show run
: Saved
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
hostname time
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 timewarner permit icmp any any
access-list timewarner permit tcp any host X.X.X.10 eq 3389
access-list timewarner permit tcp any host X.X.X.9 eq ftp
access-list timewarner permit tcp any host X.X.X.9 eq ftp-data
pager lines 24
logging on
logging timestamp
logging trap warnings
icmp deny any outside
mtu outside 1500
mtu inside 1500
ip address outside X.X.X.11 255.255.255.128
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
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.X.10 192.168.1.50 netmask 255.255.255.255 0 0
static (inside,outside) X.X.X.9 192.168.1.49 netmask 255.255.255.255 0 0
access-group timewarner in interface outside
route outside 0.0.0.0 0.0.0.0 X.X.X.1 1
timeout xlate 3:00: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 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 timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.30 inside
dhcpd dns 24.25.5.60 24.25.5.61
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:a2542b5249f
: end
time(config)#
ASKER
What you have stated is correct.
I can ONLY remote desktop to .10 and should be able to FTP to .9 but it does not allow me to.
When I try the following command ( telnet X.X.X.9 21) from a laptop inside the firewall it gives me:
220 Microsoft FTP Service
When i try the same command from outside the firewall it gives me a blinking cursor for several minutes and just times out.
I can ONLY remote desktop to .10 and should be able to FTP to .9 but it does not allow me to.
When I try the following command ( telnet X.X.X.9 21) from a laptop inside the firewall it gives me:
220 Microsoft FTP Service
When i try the same command from outside the firewall it gives me a blinking cursor for several minutes and just times out.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also, please verify the windows firewall is off for troubleshooting purposes.
ASKER
Windows Firewall is off on the server.
I used the tool ( checked all option) and got the following results:
X.X.X.10
is responding on port 3389 (ms-wbt-server).
( All other ports are not responding)
X.X.X.9
is responding on port 21 (ftp).
( All other ports are not responding)
John
I used the tool ( checked all option) and got the following results:
X.X.X.10
is responding on port 3389 (ms-wbt-server).
( All other ports are not responding)
X.X.X.9
is responding on port 21 (ftp).
( All other ports are not responding)
John
Since you are getting back a "responding on port 21", I don't believe the issue lies in your PIX.
Try this website:
https://www.wormly.com/test_ftp_server
Can it connect to your FTP server?
Try this website:
https://www.wormly.com/test_ftp_server
Can it connect to your FTP server?
ASKER
When I seen I was getting a response on port 21 I realized the firewall was doing it's job.
Just for the hell of it I rebooted the server and sure enough when it came back up I can now
telnet to the ip address via port 21 and can also get to it via my broswer and cmd prompt.
Thanks for your help.
John
Just for the hell of it I rebooted the server and sure enough when it came back up I can now
telnet to the ip address via port 21 and can also get to it via my broswer and cmd prompt.
Thanks for your help.
John
ASKER
The port scan tool helped me realize it was not my firewall and allowed me to focus on just the ftp server itself.
access-list timewarner permit icmp any any
access-list timewarner permit tcp any host X.X.X.10 eq 3389
access-list timewarner permit tcp any host X.X.X.9 eq ftp
access-list timewarner permit tcp any host X.X.X.9 eq ftp-data
According to this, you are only allowing RDP to host .10. You are allowing FTP to .9.
Did you say you are able to RDP to .9?? You shouldn't be able to.