In article <yP84a.3976$Hm3.1616@prv-forum2.provo.novell.com>, wrote:> and now believe that
> we have succesfully bypassed the mail proxy for incomming mail.
To be sure, disable Mail Proxy.
> But i am not convinced about NAT working, if i issue the _dumpnattcp
> command at the console prompt i am given an empty file of 1kb.
I tried it once and couldn't get it working either. Don't worry about
it.
If you have private IP addresses, and do not go through the proxy, NAT
must
be working in order to get replies from the Internet. There are other
diagnostics to see if NAT is working anyway.
Stay with NAT 6.00e.
> We have bound a secondary ip address to the puplic card
> using the insert menu in inetcfg>bindings. i was unable to get the
stack
> working by placing "add secondary ipaddress XXX.XXX.XXX.XXX".
You can add another binding (completely different network) in INETCFG,
but
secondary addresses are, by definition, in the same subnet as an
existing
primary address. Sounds like you tried to add the wrong address.
>
> Things we have noted apart from no tables in the nattcp.cfg file we
also
> note that on reboot of server the default route always comes up
disabled
You might have a GATE=x.x.x.x entry in NETINFO.CFG that needs to
removed, so
that the GATEWAYS file will work.
> our
> mail gateway is now able to perform mx lookup requests and resolve
dns
> names but is it doing this through NAT?
If it works, does it matter? Unload PROXY.NLM - if things work then,
you
can be sure it is a routed solution, and not a proxied solution. I am
not
sure of the config, so I can't say if you are using a proxy for part
of that.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to
http://nscsysop.hypermart.net ***