Our internet connection to our LAN is T1 and our public IP address to Border
Manager provided by our Internet provider.
I have 6 servers with NAT entry in Border Manager 3.6 and they can access
internet no problem.
I wanted to add another server with NAT, the moment I add NAT, the server
that I am trying to put NAT for can not access the internet.
If I remove the NAT, that server starts accessing the internet. I don't
understand why.
(Note: we don't use default filters, we blocked most of the ports except
default HTTP, TCP and SMTP ports)
1) Do I need my internet provider to put a pointer (Public name) record for
this server in order to let this server access internet
(I think, this may be the reason why because public IP we assign to this
server at BM, is not defined by our internet provider)
2) If # 1 is false, does filters have anything to do with? (Remind you, any
workstation in my LAN can access internet)
MC
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***
"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.0000336...@ix.netcom.com...
"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.0000337...@ix.netcom.com...
> Static NAT requires you to map a public IP address to a private IP
> address. The public IP address must be a secondary IP address. If you
> simply type a public IP address in the static NAT setup without
> actually adding to the public interface, you will have the exact
> symptoms you describe. You need to add the public IP address to be
> used with the ADD SECONDARY IPADDRESS x.x.x.x command (also in
> autoexec.ncf). DISPLAY SECONDARY IPADDRESS will show the addresses in
> use. (NW 6.5 can also add secondaries in INETCFG).
>
> Have a look at the URL below. You might be interested in my book on
> configuring BMgr filter exceptions, which covers static and dynamic
> NAT, and how filtering works with them.
If both are done, you may have a filtering issue. (You could try a
quick test with UNLOAD IPFLT to disable filtering).
Filter exceptions for static NAT need to call out the internal IP
address of the NAT host, not a public IP address. (Or IP address=Any).
Where else (which menu or config file) do you add Secondary IP address for
the new static NAT pair? and what would this secondary address do?
(When you say secondary IP, in my mind, I should have a second IP address
for this server?)
Regards, and thanks
"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.0000338...@ix.netcom.com...
I see a lot of similar problem of others in regards to this, but
"MC" <ozop...@hotmail.com> wrote in message
news:l%Qub.5226$I04....@prv-forum2.provo.novell.com...
You only need secondaries for static NAT, in the configuration we are
discussing. But NAT is only being used when bypassing the proxies. If those
internal hosts are doing proxy-based access, they will not be using NAT, and
not notice missing IP addresses.
Also, if the proxy is configured with those extra public IP addresses (as
'public'), they will be automatically loaded when proxy loads, and then static
NAT will be able to use them.
"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.0000339...@ix.netcom.com...
Do you see secondary IP addresses? Is the one for the new static NAT
not there? If so, add it.
Put that in autoexec.ncf.
(You really might benefit from one or both of the books mentioned in
the URL below...<g> All of this stuff is covered.)
In regards to purchasing your book, unfortunatley our company will phase out
Novell platform to move more user friendly (if not as powerfull as Novell)
firewall. It would be great for me to have as a reference untill though.
I will see I could my boss to approve.
Regards,
MC
"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.000033c...@ix.netcom.com...
"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.000033c...@ix.netcom.com...
If you want the addressed to load, put them in autoexec.ncf and be done
with it!
I think you would find BMgr to be a lot more user friendly than you
think, if you just understand a bit more about how it works and where
you need to go to configure this or that.
"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.000033c...@ix.netcom.com...
I generally launch an NCF file from autoexec.ncf to load up the secondary IP
addresses. I suspect either proxy is loading and putting in the addresses,
or you have another NCF file being called that is adding them.
Thank you very much.
MC
"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.000033e...@ix.netcom.com...
I have SECONDIP.NCF in the AUTOEXEC.NCF file that refers to all secondary
ips.
>>> Craig Johnson<cra...@ix.netcom.com> 11/25/2003 7:37:56 PM >>>