In article <1130348406.139437.196400@g47g2000cwa.googlegroups .com>,
"Albert" <sfaerax@gmail.com> writes:
> Thank you for support,
>
> If i try your commands on NIS+Client in NET_B, they don't work:

They won't - you need to run them on the master, or at least on
something that's working as a client.

> I can run "niscat -o `domainname`" on NIS+Client on the same network
> of NIS+Master, and I see the the real IP address:
>
> ...
> Universal addresses (6)
> [1] - udp, inet, "REAL_IP_NIS+Master".0.111
> [2] - tcp, inet, "REAL_IP_NIS+Master".0.111
> [3] - -, inet, "REAL_IP_NIS+Master".0.111
> [4] - -, loopback, "Hostname_NIS+Master".rpc
> [5] - -, loopback, "Hostname_NIS+Master".rpc
> [6] - -, loopback, "Hostname_NIS+Master".rpc
> ....
>
> Is it possible to insert a row with also information of
> NATTED_IP_NIS+Master?

That was the general idea I was getting at. If you - on the master -
add the natted IP address of the master into the hosts table as another
IP address for the master, and then run

nisupdkeys -s -a -H hostname_of_master

then it should add the entries for the natted IP address, and then the
machines on the other side should be able to see them. You might have
to use nisprefadm to force the use of the correct address (depending on
which side the client is).

I've never tried doing this in the situation you describe - this is
normally used for multihomed hosts, and I've used it for that, but the
general principle doesn't seem too different.

--
-Peter Tribble
L.I.S., University of Hertfordshire - http://www.herts.ac.uk/
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/