Gavin,

Thank you for taking the time to respond.  Some valuable insight!

I have restarted network services on all three boxes.  I wonder if I need to
bounce the two boxes the 979 can't communicate with?  I have considered that
as a last resort because this week is a bad time to bring the other boxes
down.  (For the record, they are a 939 and an 997.)

Bob

-----Original Message-----
From: Gavin Scott [mailto:[log in to unmask]]
Sent: Tuesday, October 23, 2001 5:46 PM
To: Sorenson, Bob; [log in to unmask]
Subject: RE: [HP3000-L] Will DSLINE Work With NAT?

Bob writes:
> We decided to use NAT translations for the 979 so users would
> not have to modify their Reflection configuration for the new IP.
>
> I have changed the IP in NMMGR for the 979 node on all three boxes
> to the new IP.

If you're talking about the Network Directory, keep in mind that once a name
translation is loaded from the directory, it will stay there until the
network (or the machine?) is restarted, so changes made to the NSDIR *after*
someone has tried to use the translation will have no effect.  So you might
have changed the addresses, but the changes won't take effect until at least
a complete network restart.  Perhaps there is some incantation in NETTOOL
that will flush the NSDIR name cache, but if so I don't know what it is.

Depending on how your NAT stuff is set up, you may not be able to use some
or all NS services between those systems.  The problem is that some of the
NS protocols may involve sending port numbers or IP addresses in data, which
generally only works via NAT if you have a NAT implementation which knows
these protocols and will dynamically *change* the data going back and forth
to reflect the translated addresses and port numbers as needed.

I recall having had at least one 3000 customer who found it impossible to
run NetBase through a NATted connection because the protocol used by the
NetIPC's Named Sockets API to implement the NS Socket Registry turned out to
be incompatible with NAT due to using in-band signaling of network addresses
and port numbers.  I don't know if this problem would affect basic NS
services such as simple VT.

G.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *