amkbailey
asked on
Replacing PIX with Cisco ASA 5505 issues
We replaced an extremely old PIX with an ASA 5505. We duplicated the old config on the new ASA (when possible) but still having a couple issues. The biggest one is that the old PIX had a rule that assigned an additional wan ip address to the outside interface.
global (outside) 1 74.x.x.12
I don't think the ASA is using that line (if at all) the way the pix did because we are having issues with some outbound email bouncing back due to our SPF record. The SPF record is set to 74.x.x.12 but when I telnet into other mail servers, they are seeing me come from 74.x.x.10 which is the IP assigned to the outside interface 0/0 of the ASA.
Any ideas how to resolve this besides changing the SPF record?
global (outside) 1 74.x.x.12
I don't think the ASA is using that line (if at all) the way the pix did because we are having issues with some outbound email bouncing back due to our SPF record. The SPF record is set to 74.x.x.12 but when I telnet into other mail servers, they are seeing me come from 74.x.x.10 which is the IP assigned to the outside interface 0/0 of the ASA.
Any ideas how to resolve this besides changing the SPF record?
Need to create a static NAT rule for your email server and 74.x.x.12
ASKER
Here was the existing NAT rule.
access-list acl_inbound permit tcp any host 74.x.x.11 eq smtp
I added
access-list acl_inbound permit tcp any host 74.x.x.12 eq smtp
but when I telent into other mail servers, it is seeing my ip in the greeting as 74.x.x.10
access-list acl_inbound permit tcp any host 74.x.x.11 eq smtp
I added
access-list acl_inbound permit tcp any host 74.x.x.12 eq smtp
but when I telent into other mail servers, it is seeing my ip in the greeting as 74.x.x.10
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
8.2 (1)
nat (inside,outside) tcp 74.x.x.11 smtp 10.x.x.113 smtp netmask
nat (inside,outside) tcp 74.x.x.11 smtp 10.x.x.113 smtp netmask
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
sorry. it does. left that part off. I guess I need to post both config files to see the difference.
It should be a 1-1 static nat, or a policy nat and not just the smtp port static.
ASKER
We ended up just going to 1 static IP so we have it working ok now.