Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NAT not working

0 views
Skip to first unread message

bill.b...@revest.com

unread,
Nov 4, 2003, 4:23:31 PM11/4/03
to
What would be the possible reasons that a recent entry in a NAT table
would work/take affect? I'm stumped.

This is on a 3.5 BM server using static and dynamic. The ISP has given us
63 possible addresses, thus far we have 8 configured. Those all work fine.
I have used the ADD SECONDARY IPADDRESS and have confirmed it is there
through DISPLAY. I have addded the appropriate internal and external
addresses in the table and have reinitialized. From the server with the
NIC that is being translated, I can ping BM, I can ping externally. (Of
course, the server has a couple of NICs). From BM, I can ping the server
in question's NIC and the external address assigned to it.

However, I cannot ping from the outside world to the externall address
assigned. It's like the translation isn't happening. Can anyone offer
suggestions?

Also, unloaded filters when pinging so that the pings go through. Other
external addresses ping fine.

Lance Reynolds

unread,
Nov 4, 2003, 7:35:12 PM11/4/03
to
What version of Netware and service pack? What version of TCP/IP? I'd
try upgrading to the latest code for starters.


--
Lance Reynolds, CNE

Sylvain

unread,
Dec 16, 2003, 2:49:24 PM12/16/03
to
I was just about to post about this exact problem that we have here.

Except it's a BM3.6sp2 on Netware 6sp3.

Secondary IP added and NATted /public/private. Filters up and down (for
port access) .. don't matter!

Ping from external source.. not working.


>>> <bill.b...@revest.com> 11/04/2003 4:23:31 PM >>>

Craig Johnson

unread,
Dec 17, 2003, 12:13:01 PM12/17/03
to
In article <nNUpb.3906$5N5....@prv-forum2.provo.novell.com>, wrote:
> However, I cannot ping from the outside world to the externall address
> assigned. It's like the translation isn't happening. Can anyone offer
> suggestions?
>
Two things to look at:

1. If the translation is working, the ICMP packets could be getting to
the internal hosts, but if those hosts do not have a proper default
route, they will never send a reply, or they will send it to the wrong
place.
2. If translation is not actually working, you may have a problem in
tcpip.cfg. See tip #48 at the URL below.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

0 new messages