I'm not sure if I entirely understand your setup or your question, but I'll assume your 5 servers all have one (private) IP-address on your inside network and these addresses are being translated to public IPs as they connect to anything on the outside network.
The servers can talk to eachother on their private addresses as they're on the same subnet (again, I assume). But, the public addresses only exist on the firewall and only if a private address comes in that matches your static translation.
So the server cannot refer to itself on its public address because it doesn't have a public address. And if it doesn't have a public address, other servers cannot connect to it either.
It could be possible however, depending on your ACLs, to connect to the public address from the outside.
If there's a static translation like:
static (inside,outside) p.p.p.p 10.1.1.1 (where p.p.p.p is your public address) then a packet coming in on the outside interface with p.p.p.p as destination, will be translated to destination 10.1.1.1.
Thank you for the response, I am going to try to clarify my setup.
All 5 servers have a static (inside,outside) translations for public to private.
I am not sure if you thought I had PAT running, and doing overload.
I am able to connect the public addresses from outside, because these are web servers.
It is looking like this feature is built in and maybe not able to be worked around, and if this is so, thats fine, but hopefully there is a way to refer to the servers by their public IP addresses when coming from another server on the same private subnet that also have a public static translation.
If you are running version 7, you can run hairpinning to accomplish what you want.
Are you referring to the public ip's by ip only or are you possibly also referring to them by name? There is something called dns doctoring which would allow you to alter the dns reply from an outside dns server. For example if yourdomain.com resolves publicly to 126.96.36.199 you could have the pix change this reply to the inside address, ex. 192.168.x.x.
If the servers were on different interfaces, dmz and inside, you could use destination nat or the alias command in pix 6. Hope that helps.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...