+ Reply to Thread
Results 1 to 9 of 9
  1. #1
    Member littlebird's Avatar
    Join Date
    Oct 2002
    Location
    Caribean Skies (P.R., D.R, etc.)
    Posts
    198

    Linux networking....

     
    Hello!
    I need help with linux.
    You see we have a Dell Linux Server with RH7.2 and we have 16 workstations using RH7.3 and 7.2. Every workstation has their own IP and is connecting to the server via NIS (ypbind) to mount the users home directories and all that stuff.
    The thing is that the first week of use everything was great. Everything was working and every user could log in!
    But now only 3 computers are working!!

    The thing is that the other 13 machines are not binding to the server! The stay at :

    Listening for NIS .................................................. ........... [FAILED]

    Now... why the heck is this happening?
    Nothing was changed in the computer config files. Everything is the same. And the weird thing is that the server is configured correctly too (nothing has changed) so if it is the server nothing would be working but 3 computers are completing successfully the ypbind!!!

    Can anyone help me.?
    Any info I'll provide..!

  2. #2
    Not Really a Member
    Join Date
    Oct 2001
    Posts
    27,879
    can you see any reason for it in /var/log/messages on either the server or the failing clients?
    Helicopters don't fly; they vibrate so much and make so much noise that the earth rejects them.

  3. #3
    Member littlebird's Avatar
    Join Date
    Oct 2002
    Location
    Caribean Skies (P.R., D.R, etc.)
    Posts
    198
    in /var/log/messages for the machine it says:

    Oct 29 17:09:47 m117-16 ypbind: ypbind startup succeeded
    Oct 29 17:10:08 m117-16 ypbind: ypbind shutdown succeeded
    Oct 29 17:10:08 m117-16 ypbind: attempting to contact yp server failed
    Oct 29 17:15:17 m117-16 ypbind: ypbind startup succeeded
    Oct 29 17:15:39 m117-16 ypbind: ypbind shutdown succeeded
    Oct 29 17:15:39 m117-16 ypbind: attempting to contact yp server failed
    Oct 29 17:22:37 m117-16 portmap: portmap shutdown succeeded
    Oct 29 17:22:37 m117-16 portmap: portmap startup succeeded
    Oct 29 17:22:37 m117-16 ypbind: ypbind startup succeeded
    Oct 29 17:22:59 m117-16 ypbind: ypbind shutdown succeeded
    Oct 29 17:22:59 m117-16 ypbind: attempting to contact yp server failed

    whenever you try to start the ypbind daemon.!

    Let me check the server.

  4. #4
    Member littlebird's Avatar
    Join Date
    Oct 2002
    Location
    Caribean Skies (P.R., D.R, etc.)
    Posts
    198
    Server side:

    Oct 29 16:47:25 pegasus ypserv[26569]: refused connect from 136.145.......:1234 to procedure ypproc_domain_nonack
    Oct 29 16:47:45 pegasus ypserv[26569]: refused connect from 136.145.......:1238 to procedure ypproc_domain_nonack
    Oct 29 16:48:05 pegasus ypserv[26569]: refused connect from 136.145........:1239 to procedure ypproc_domain_nonack
    Oct 29 16:48:45 pegasus last message repeated 2 times
    Oct 29 16:50:05 pegasus last message repeated 4 times
    Oct 29 16:51:06 pegasus last message repeated 3 times
    Oct 29 16:52:26 pegasus last message repeated 4 times
    Oct 29 16:53:46 pegasus last message repeated 4 times
    Oct 29 16:55:06 pegasus last message repeated 4 times
    Oct 29 16:56:26 pegasus last message repeated 4 times
    Oct 29 16:57:46 pegasus last message repeated 4 times
    Oct 29 16:59:06 pegasus last message repeated 4 times
    Oct 29 17:00:26 pegasus last message repeated 4 times
    Oct 29 17:01:46 pegasus last message repeated 4 times
    Oct 29 17:02:06 pegasus ypserv[26569]: refused connect from 136.145.......:1239 to procedure ypproc_domain_nonack
    Oct 29 17:02:26 pegasus ypserv[26569]: refused connect from 136.145........:1240 to procedure ypproc_domain_nonack
    Oct 29 17:02:46 pegasus ypserv[26569]: refused connect from 136.145.........:1244 to procedure ypproc_domain_nonack
    Oct 29 17:03:06 pegasus ypserv[26569]: refused connect from 136.145.........:1247 to procedure ypproc_domain_nonack
    Oct 29 17:03:46 pegasus last message repeated 2 times
    Oct 29 17:05:06 pegasus last message repeated 4 times
    Oct 29 17:05:26 pegasus ypserv[26569]: refused connect from 136.145..........:1248 to procedure ypproc_domain_nonack
    Oct 29 17:05:46 pegasus ypserv[26569]: refused connect from 136.145.........:1251 to procedure ypproc_domain_nonack
    Oct 29 17:06:26 pegasus last message repeated 2 times
    Oct 29 17:07:46 pegasus last message repeated 4 times
    Oct 29 17:09:06 pegasus last message repeated 4 times
    Oct 29 17:10:06 pegasus last message repeated 3 times
    Oct 29 17:10:26 pegasus ypserv[26569]: refused connect from 136.145.........:1252 to procedure ypproc_domain_nonack

  5. #5
    Ultimate Member pbharris's Avatar
    Join Date
    Oct 2001
    Location
    Chicago, IL
    Posts
    2,514
    hello,
    as embarrassed as i am to say this i have never run NIS... but i have been thinking this would be nice because we are an all linux home now


    the first thing i would see if ypbind is running properly on the server, i assume a restart of a client would not fix the issue...
    Odds are very good there are several spelling mistakes in this post.

  6. #6
    Space for Sale! :p eagle1's Avatar
    Join Date
    Oct 2001
    Location
    La Isla del Encanto
    Posts
    5,879
    Already tried a restart!
    Also checked if the config files (yp.conf in the clients) were correctly written and they are.!
    The last thing we did (yesterday) was to upgrade the ypbind server version (and clients) but ... that didn't do anything either.!!

    We don't want to start over from scratch as that would take a lot of work (backing the server, the users home directories, etc. etc.).
    That's a last resort. But we can't find anything!!!

    BTW, I'm littlebirds brother.
    boo!

  7. #7
    Ultimate Member dunbar's Avatar
    Join Date
    Feb 2001
    Posts
    3,606
    Blog Entries
    5
    Originally posted by littlebird
    in /var/log/messages for the machine it says:

    Oct 29 17:09:47 m117-16 ypbind: ypbind startup succeeded
    Oct 29 17:10:08 m117-16 ypbind: ypbind shutdown succeeded
    Oct 29 17:10:08 m117-16 ypbind: attempting to contact yp server failed
    Let me check the server.
    g-g-g-g-z-z-z-k!
    I'm totally non network oriented, but it looks like the client makes attempts to contact the server after the server is successfully shutdown.... as if something is out of step somewhere. Maybe this is the way things are supposed to work, maybe not?
    I now return you to your regularyly scheduled thread.... brrrrzzzzzzaappp!

  8. #8
    Space for Sale! :p eagle1's Avatar
    Join Date
    Oct 2001
    Location
    La Isla del Encanto
    Posts
    5,879
    The message you quoted is the ypbind script OF one of the CLIENTS and not the server!
    That happenned whenever I tried to bind the client to the server to start NIS.!
    boo!

  9. #9
    Junior Member
    Join Date
    Feb 2009
    Posts
    1
    Quote Originally Posted by littlebird View Post
    Hello!
    I need help with linux.
    You see we have a Dell Linux Server with RH7.2 and we have 16 workstations using RH7.3 and 7.2. Every workstation has their own IP and is connecting to the server via NIS (ypbind) to mount the users home directories and all that stuff.
    The thing is that the first week of use everything was great. Everything was working and every user could log in!
    But now only 3 computers are working!!

    The thing is that the other 13 machines are not binding to the server! The stay at :

    Listening for NIS .................................................. ........... [FAILED]

    Now... why the heck is this happening?
    Nothing was changed in the computer config files. Everything is the same. And the weird thing is that the server is configured correctly too (nothing has changed) so if it is the server nothing would be working but 3 computers are completing successfully the ypbind!!!

    Can anyone help me.?
    Any info I'll provide..!


    Hi

    Please check the /var/yp/securenets. It does happen when the machines are in the different domain and there is different entry in securenets file.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Recommended Sites: ResellerRatings Store Reviews