Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can not telnet to server in the DMZ

Status
Not open for further replies.

strayrog

MIS
Feb 2, 2005
54
US
I have a PIX 515e and just set up the DMZ for a mail server. When I attempt to telnet IP 25, there is no response. Not exactly sure what the problem is.

PIX Version 6.3(4)
interface ethernet0 100full
interface ethernet1 100full
interface ethernet2 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security50
enable password nxWpkg/YNVmBGGTq encrypted
passwd nxWpkg/YNVmBGGTq encrypted
hostname MApix
domain-name ciscopix.com
clock timezone EST -5
clock summer-time EDT recurring
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 pptp 1723
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 smtp 135
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
name 192.168.66.xx ex-mail
object-group service BCMudp udp
port-object range 51000 51200
port-object range 7000 7000
port-object range 28000 28511
object-group service ex-mail tcp
port-object eq www
port-object eq pop3
port-object eq https
port-object eq ftp
port-object eq imap4
port-object eq smtp
port-object eq telnet
port-object eq ssh
access-list dmz_access_in permit tcp 192.168.66.0 255.255.255.0 any
access-list outside_access_in permit tcp any host 12.170.xx.xx object-group ex-mail
pager lines 24
logging on
logging timestamp
logging buffered informational
logging trap warnings
logging history informational
logging host inside 192.168.64.xx
icmp permit any outside
icmp permit any inside
mtu outside 1500
mtu inside 1500
mtu dmz 1500
ip address outside 12.170.xx.xx 255.255.255.128
ip address inside 192.168.64.xx 255.255.255.0
ip address dmz 192.168.66.xx 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.64.xx 255.255.255.255 inside
pdm location 12.170.xx.xx 255.255.255.255 outside
pdm location 192.168.128.2 255.255.255.255 inside
pdm location 192.168.128.0 255.255.255.0 inside
pdm location 192.168.63.0 255.255.255.0 inside
pdm location 192.168.64.xx 255.255.255.255 dmz
pdm location ex-mail 255.255.255.255 dmz
pdm logging warnings 50
pdm history enable
arp timeout 14400
global (outside) 1 12.170.xx.xx
global (dmz) 200 ex-mail-192.168.66.xx
global (dmz) 10 12.170.54.xx
nat (inside) 1 192.168.63.0 255.255.255.0 0 0
nat (inside) 1 192.168.64.0 255.255.255.0 0 0
static (inside,outside) 12.170.xx.xx 192.168.128.2 netmask 255.255.255.255 0 0
static (dmz,outside) 12.170.xx.xx ex-mail netmask 255.255.255.255 0 0
access-group outside_access_in in interface outside
access-group dmz_access_in in interface dmz
route outside 0.0.0.0 0.0.0.0 12.170.54.1 1
route inside 192.168.63.0 255.255.255.0 192.168.64.1 1
route inside 192.168.128.0 255.255.255.0 192.168.64.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 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 0.0.0.0 0.0.0.0 inside
snmp-server host inside 192.168.64.xx
snmp-server host dmz 192.168.64.xx
snmp-server location
snmp-server contact
snmp-server community public
snmp-server enable traps
tftp-server inside
floodguard enable
telnet 192.168.64.0 255.255.255.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh 0.0.0.0 0.0.0.0 inside
ssh 0.0.0.0 0.0.0.0 dmz
ssh timeout 5
console timeout 0
 
do this:

static (inside,dmz) 192.168.64.0 192.168.64.0 netmask 255.255.255.0

access-list dmz_access_in permit icmp any any log
access-list dmz_access_in permit tcp 192.168.66.0 255.255.255.0 any log
access-group dmz_access_in in interface dmz

After that, you can telnet from inside to dmz
 
Wirelesspeap,

Thanks for the post. However I am still unable to telnet to port 25 from the outside address. I can ping the dmz address but not the outside address. I also can not open a web page from either the inside, dmz or the outside.

Any other ideas? Anyone?

Thanks
 
strayrog,
What exactly are you trying to do? Telnet from the outside to a server in the DMZ; telnet from the inside to a server in the DMZ; telnet to the PIX itself from outside or inside. I just need a clearer picture.




Brent
Systems Engineer / Consultant
CCNP
 
Supergrrover,

I am attempting to put a mail server in the dmz of y pix 515e. I can telnet to the internal IP (2 nics, 1 inside ip and 1 dmz ip) but not to the outside IP.
 
Are you trying to telnet the pubIP from your local lan? That wont work.

To only have access from your lan to your dmz you dont need any access-list dmz statement. You need your global/nat statements in order though. And dealing with exchange i would disable the fixup protocol ( no fixup protocol smtp 25 )

Check this guide from cisco. Its a simple configuration for what you want to accomplish

 
Sorry to be a pest, but I need a little more.

Where are you telnet-ing from (an external source, from the inside to the static DMZ address - as seen from the inside, from the inside to the static DMZ address - as seen from the outside.) What IP are you telnet-ing from and to.

I don't see an Static from the inside to the DMZ. If that is where you are coming from, then add this line

static (inside,dmz) inside IP address ex-mail netmask 255.255.255.255 0 0
You won't need an ACL becuase by default, everything is allowed from a higher security level to a lower one.

This line isn't attached to a NAT so I would delete it
global (dmz) 200 ex-mail-192.168.66.xx

Hope this helps

Brent
Systems Engineer / Consultant
CCNP, CCSP
 
Grovver, maybe i am wrong but do you really need a static statement if the mailserver dont need access to the lan!? I have to check my configs but i dont recall needing one.
 
Hey marty - that's two "r"s :)

He is trying to get to the DMZ from the INSIDE. You don't need an ACL for this but you do need some sort of translation to get across the pix security boundaries in either direction unless it is setup in transparent mode (which his is not.) It can be a static or a Global NAT pair. While it is possible to have it set up as a router instead, I don't see anything in his config regarding that and you will still need Global NAT pairs, just a Nat 0 instead.

There are bunch of Natting statements, but some of them aren't tied to anything

global (outside) 1 12.170.xx.xx
global (dmz) 200 ex-mail-192.168.66.xx - not attached
global (dmz) 10 12.170.54.xx - not attached
nat (inside) 1 192.168.63.0 255.255.255.0 0 0
nat (inside) 1 192.168.64.0 255.255.255.0 0 0
static (inside,outside) 12.170.xx.xx 192.168.128.2 netmask 255.255.255.255 0 0
static (dmz,outside) 12.170.xx.xx ex-mail netmask 255.255.255.255 0 0


Now if he just adds his static (inside,dmz) to this you are set. It is also possible to fix up the
global (dmz) 200 ex-mail-192.168.66.xx
statement.


Brent
Systems Engineer / Consultant
CCNP, CCSP
 
Sry didnt see the second r =)

Yes i noticed i didnt read his config very well, thought he had he´s globals/nats in order.

And you are right for this he would need the static statement =)
 
Supergrrover and boymarty24,

Thank you very much for your help. After I applied your suggestions, all is working well. Once again, thank you. Tek-tips never fails to help!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top