FW Using Incorrect NAT Rule?

[Startrek4u]

Ok, so here is my configuration, off of our FW we have a number of subnets which are used for private connections to various partners of ours. They are numbered as follows: 192.168.201.X, 192.168.202.X, etc. For these connections I have NAT rules setup to do no translating of the internal address, so when traffic comes from 192.168.1.X (internal) it looks that way to the next hop as well. For one of these connections the final address is a 170.132.X.X address scheme, I have the routing set to send any traffic destined for this network to the next hop (192.168.201.2). However, the party looking at the device on the other end say they see our Public IP coming into their device. I'm confused as to why that is, the no-NAT rules for this are number 3 and 4 (ie no-NAT from 192.168.1.X to 192.168.201.X), the automatic NAT Rule for the public IP much lower in the list.

I don't suppose anyone has any suggestions or know what I can do to fix this?

Thanks

[bglass]

You say that the NAT rule is "no-NAT from 192.168.1.X to 192.168.201.X" but you mention that the final address as a 170.132.X.X network.

The NAT rule you mentioned above would not match a connection from 192.168.1.x going to 170.132.x.x and would therefore match your Automatic NAT rule hiding it behind the public IP.