In article , Samir wrote: :I am sure its Pix 6.3(3)
But you are using 'conduit'. You wouldn't use 'conduit' on PIX 6 unless you were required to by matters outside your control (e.g., certification requirements for a NASA flight simulator.) As you appear to have the authority to reconfigure your PIX 520, we know that's not the situation at hand.
Cisco replaced the functionality of 'conduit' in PIX 5.0(1), and by 5.1(2) was already suggesting that it not be used. By 5.2(3) they declared it deprecated, and by 5.3(1) Cisco started marking conduit-replaced problems as "Won't Fix". Then in PIX 6.2(1), Cisco rewrote important portions of access controls, and anywhere that conduit functionality did not fit smoothly in, Cisco just left conduit broken. By the time of 6.3(1), Cisco had already said clearly that conduit will definitely not be supported in any form in the next major software release (and sure enough, now that PIX 7.0 is released for some models, there is no conduit remaining.)
Thus, by PIX 6.3(3), you are walking the twilight borders of conduit, where things are neither real nor unreal, and debugging nightmares are to be routinely expected.
:The reason I need to use the public IP is because the I am using :another Web hoster which runs the web page, and the download things are :on my server here, I think this might clear it up a little.
:So I need the Public Ip because that's what I use on the Web Hosting :site to tell where my downloads are.
You must have DNS for your public page. Add another hostname to that structure, such as download.son-of-dlx.com and use that on the public pages instead of a literal IP. Once you have the address in hostname format instead of IP format, then the PIX can handle the translation details for you, giving you the appropriate inside or outside address. [The exact configuration details depend upon where the DNS server is relative to the PIX inside.]