Of all the gin joints in all the towns in all the world, Dag-Erling Smorgrav had to walk into mine and say:
> I have a very simple NIS configuration at home: niobe is the server > and luna, my scratch box, is the client. Niobe runs 4.0-CURRENT, and > luna runs 3.0-RELEASE until 'make world' finishes on niobe so I can > make installworld over NFS. In addition to being the NIS and NFS > server, niobe is also its own NIS client, and I have no trouble at all > looking up NIS maps on niobe. > > Luna, however, seems absolutely allergic to NIS. Everything is > configured correctly as far as I can see [chop] Sure, that's what they all say. The N in NIS stands for Network. This means that you should be concentrating your diagnostic efforts on the network. Are you using an insane amount of IP aliases? Did you try to run tcpdump on the interface that connects the two machines together? >From both sides? Are your netmasks correct? Did you check to see if 'domainname' returns the correct information? > Running the server in debug mode shows absolutely no activity of any > kind from luna. There's nothing wrong with the network connection > (LPIP); I don't believe you. Like I said: run tcpdump on both sides. See if you actually have traffic pertaining to NIS travelling between the two machines. What the hell is LPIP anyway. > Any suggestions? Tcpdump, tcpdump and more tcpdump. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
