Walter thanks for your help on this one i've made the following
changes
access-list out-acl permit tcp host a.a.a.a any eq 25
no sysopt connection permit-pptp
access-list acl100 permit gre any any
When telnetting i'm telnetting to the outside IP a.a.a.a as i am
trying to configure an exchange server with an SMTP feed behind the
PIX, on the IP seperate IP, if i am wasting my time and you think it
would be easier to just use port 25 off the NAT'd IP or even off the
PIX firewall IP then let me know
Thanks again for your help - really appreciated
(Walter Roberson) wrote in message news:<bogn79$11k$>...
> In article < >,
> paul tomlinson <> wrote:
> : I am trying to
> :configure the PIX to send any smtp and pptp traffic destined to
> :a.a.a.a to the local smtp server 172.17.135.100,
>
> :Two problems, neither the port 25 mapping or the VPN connection seem
> :to work, when i try to telnet the ports just closes straight away -
>
> :i am running IOS 6.3(1)
>
> :access-list out-acl permit icmp any any echo-reply
> :access-list out-acl permit icmp any any unreachable
> :access-list out-acl permit icmp any any time-exceeded
> :access-list out-acl permit icmp any any source-quench
> :access-list out-acl permit icmp any any parameter-problem
> :access-list out-acl permit tcp any any eq ssh
> :access-list out-acl permit tcp any any eq pop3
> :access-list out-acl permit gre host a.a.a.a any
> :access-list out-acl permit tcp host a.a.a.a any eq pptp
>
> Your out-acl, which you apply against the outside interface,
> isn't permitting smtp in to a.a.a.a.
>
> :sysopt connection permit-pptp
>
> That applies only to pptp traffic that terminates at the PIX.
>
> :access-list acl100 permit tcp 172.17.135.0 255.255.255.0 any eq www
> :access-list acl100 permit tcp 172.17.135.0 255.255.255.0 any eq https
> :access-list acl100 permit tcp 172.17.135.0 255.255.255.0 any eq smtp
> :access-list acl100 permit icmp 172.17.135.0 255.255.255.0 any
> :access-list acl100 permit tcp 172.17.135.0 255.255.255.0 any eq domain
> :access-list acl100 permit udp 172.17.135.0 255.255.255.0 any eq domain
> :access-list acl100 permit udp 172.17.135.0 255.255.255.0 any eq ntp
> :access-list acl100 permit tcp 172.17.135.0 255.255.255.0 any eq ssh
> :access-list acl100 permit tcp 172.17.135.0 255.255.255.0 any eq telnet
> :access-list acl100 permit tcp 172.17.135.0 255.255.255.0 any eq pop3
> :access-list acl100 permit tcp any any eq ssh
> :access-list acl100 permit tcp 172.17.135.0 255.255.255.0 192.168.1.0
> :255.255.255.0
> :access-list acl100 permit udp 172.17.135.0 255.255.255.0 192.168.1.0
> :255.255.255.0
> :access-list acl100 permit icmp 172.17.135.0 255.255.255.0 192.168.1.0
> :255.255.255.0
> :access-list acl100 permit tcp any any eq smtp
>
> You have acl100 applied against the inside interface. You do not,
> though, permit out gre traffic. I am not sure whether that is
> important: I don't know whether adaptive security would automatically
> permit the return traffic or not.
>
> :access-list 101 permit ip 172.17.135.0 255.255.255.0 172.17.150.0 255.255.255.0
> :ip address inside 172.17.135.230 255.255.255.0
> :ip local pool pptp-pool 172.17.150.230-172.17.150.240
> :nat (inside) 0 access-list 101
> :static (inside,outside) a.a.a.a 172.17.135.100 netmask 255.255.255.255 0 0
>
> If you are telneting to a.a.a.a then you are doing so outside
> of the pptp tunnel and you have to permit the smtp inward as previously
> noted.
>
> To telnet to the smtp port inside of the pptp tunnel that you
> are passing through the PIX, you would have to telnet to the
> inside address, 172.17.135.100, because you've exempted that
> connection from translation by using the nat 0 access-list .