In article <fxZyi.5011$pG6.2335@prv-forum2.provo.novell.com>, Keith
wrote:
> If I am wanting to get to port 3306 from the outside, what could I be
> missing.
>
Let me see if I understand what you said so far:
1. No filtering up, so filters are not the issue.
2. Static NAT is enabled.
3. You can access the internal server from the outside, so that means
the secondary public address is there, static NAT is working, routing is
working, and the internal server has a correct default route.
My guess is that you are doing something with a web browser that
involves a redirect coming from the internal server. That redirect is
embedding the server's private IP address, and so when the external
client tries to get to the server, it doesn't know how to send the
packets to it. Not a port-related issue at all.
In these scenarios, you must configure the application to use a DNS name
instead of an IP address. The DNS name must be available on the public
and private sides. The public DNS must point to the public static NAT
address. The private DNS must point to the internal address (though you
can cheat here by putting the name and private address in the BMgr HOSTS
file if accessing via proxy).
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to
http://www.craigjconsulting.com ***