Routing outside a new NIS+ domain
2007-12-25 10:14:00
below.) We were having problems routing to other machine outside the
domain.
I received a number of suggestions to the effect that it didn't sound
as though NIS+ was the problem.
These suggestions were in fact correct. Due to another problem we had
turned off IP forwarding on our intended gateways.
Thanks to:
Original description:
> Hello,
>
> I'm trying to set up a NIS+ domain on a an internal network.
>
> We have about 20 machines on this network and between them, we have
> about 130 different network interfaces with a very large number of
> subnets.
>
> We want to serve host names but not nfs mounts of user accounts from
> the NIS+ server.
>
> I set up the server and populated only the hosts tables. Then I set up
> the clients. I discovered that I also needed to populate the services
> tables in order to get telnet to work from the clients.
>
> Having done that, I set up a couple of other machines to be route replicas
> and then set up the clients.
>
> All was OK and internal connectivity looks to be in place and the local
> accounts on each machine are still in place.
>
> However, we have a connection to a company wide network to which the servers
> are connected.
>
> From a server machine (directly connected to this netwqork) I can reach other
> machines outside this network. From a client (inside the network) I cannot.
>
> If I log on to a client and try to ping an external machine I can see that
> the client gets the address of the external machine from a NIS+ server and
> then start trying to send packets to it on the interface to which the
> default gateway (one of the servers) is connected. However, there is no
> other activity and no response.
>
> I wondered if the problem was caused by lack of data in some of the other
> tables so I then also populated the rpc and protocols tables but to no avail.
>
> Any suggestions gratefully received.
>
> john o'connor
>
Comments
Got something to say?
You must be logged in to post a comment.
