Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm a newbie to Linux, but not to Unix/Solaris, so maybe I'm just confused about where
things go, but I've been struggling almost two weeks, and all I've done is make matters worse.
Here's what's going on:
I'm running RH9 (2.4.20-8), NIS on two servers: kidrock and kwame. kidrock is the primary, and kwame is the secondary. There has been a problem with adding new users where after adding them on kidrock, the maps don't get pushed out correctly to kwame and the other clients. (I inherited this system!)
After having my id added and it working for a while, with a little more work, I've managed to lock myself out of NIS completely.
On the primary (kidrock), I:
1) modified /etc/yp.conf to list itself as the server
ypserver kidrock
2) set securenets to allow access to local host and all ips on network (we're
behind a firewall)
3) made the map, which was pushed to the client
On the client, restarted ypbind (but I have to have ypserv running because other clients point to kwame, and it doesn't work without it on for some reason).
When I run yptest for my user id, all the test pass, and I'm in the list. After restarting ypbind on my local machine, when I try to ssh to any machine (which I was logged in to before I started messing with stuff), I get rejected because the system doesn't know who I am. In /var/log/messages file
I get this:
Dec 22 09:50:32 kwame ypserv[18896]: refused connect from 192.168.0.121:37579 to procedure ypproc_all
Dec 22 09:51:52 kwame ypserv[18896]: refused connect from 192.168.0.121:33074 to procedure ypproc_match
Dec 22 09:51:53 kwame ypserv[18896]: refused connect from 192.168.0.121:37581 to procedure ypproc_all
(121 is my local machine). All of the other users in the database can log in via NIS fine, but not my user id. Portmap is running correctly, hosts.allow allows all connection from the network. I'm pulling my hair out! (What little I have!) Does anyone have something I can look at? Also, will this allow me to add new users and push them out correctly?
Just to follow up for future people looking for this problem:
I was able to solve this problem (temporarily at least) by changing the ypserv.conf file.
The "security" entry field which was set to "port" by default, was changed to "none" to
always allow access regardless of which port number. This worked almost instantly.
Why did it ever work before and not now, I don't know. Since we're on a private side
of a firewall, I'm not as concerned about this security issue for now. I need to check
to see which port number is being used and see if I can set it to something less than
1024 so that this will work as it's supposed to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.