rmilner@zia.aoc.nrao.edu (Ruth Milner) (04/26/91)
We will be rearranging our network in a month or two, and I have a couple of questions about PC-NFS routing support: 1. Does PC-NFS understand subnetting properly? 2. How can I make them talk to systems off our local network? Despite telling PC-NFS to use YP, I have also put entries in the hosts table for the BIND/YP server and the default router (a cisco which is our Internet connection), and some of the remote systems, explicitly. Every other system on the net, except *all* of the PC's (set up by 3 different people over a period of time), can talk to systems at our other sites, all connected to Internet. The PC's just sit there. They don't say "host unknown", they don't say "network unreachable", they just sit there. I know the YP information (or perhaps from named, it really doesn't matter which in this case) is getting to them because they can reach all of the systems on our local Ethernet even when they aren't in the PCs' hosts table. But they can't talk to anything else. Do I have to do anything peculiar to make them understand the routing? Most of them are running PC-NFS 3.0.1. The pcnfsd server is a Solbourne (read Sun 4) running the equivalent of SunOS 4.0.3. It is the master YP(NIS) server and runs BIND. As an aside, even if we make one of our Convexes the server, it doesn't make any difference. Will upgrading the PC-NFS software to 3.5 help? -- Ruth Milner Systems Manager NRAO/VLA Socorro NM Computing Division Head rmilner@zia.aoc.nrao.edu