I'm dieing. No route to host on same DMZ

[joneschw1]

I have a mail server physically sitting in my dmz. Its IP is (make believe) 205.1.1.1 I have a port natted on that same DMZ for 205.1.1.2. This IP nats to a mail server 10.1.1.1 sitting on the inside. For some reason I cannot send mail from 205.1.1.1 to 205.1.1.2. When I try to telnet via port 25, it gives me a "no route to host" Do I have to add some sort of route on my PIX to allow this to happen? It should send traffic to it without a route since it is on the same subnet shouldn't it? Will this even work? I am struggling, and am not the best Cisco guy. Please help.

[mostiguy]

post the config - you might have it set up such that the outside world can connect to .1.1.2, but not the dmz

[scoclayton]

It's a translation issue. Since we need to take a look at your xlate's, can you send me a 'sh run' from your PIX (sclayton@cisco.com)? I would ask you to post the config normally but I think it might be easier to explain if you didn't have to "sanitize" the config by changing addresses before posting. If you are not comfortable with this, I completely understand but it will be difficult to explain unless I can see the actual config or a sanitized config that is 100% consistent in the changes made.

Scott

[jasobrown]

Is this what you have?

static (inside,dmz) 205.1.1.2 10.1.1.1 netmask 255.255.255.255

access-list dmz permit tcp host 205.1.1.1 host 205.1.1.2 eq 25

That should be all you need.

[joneschw1]

I have static (inside,dmz) 205.1.1.2 10.1.1.1 netmask 255.255.255.0

Should it be 255.255.255.255?

[scoclayton]

Yes, and this is indeed most likely the issue. Change this config statement and issue a 'cl xlate' and then re-try. Let us know.

Scott

[joneschw1]

Scott,

You were a big help. It is working. Thank you much.