nigel@cnw01.storesys.coles.oz.au (Nigel Harwood) (12/06/90)
I have a situation where some machines on our TCP/IP network are not listing all other machines when an rwho or ruptime is done. The majority of these machines are running Excelan TCP/IP on V.2 although one is running Win TCP/IP on V.3. All machines have complete /etc/hosts files. Machine A will list A, B, C, D Machine B will list B, C Machine D will list A, B, C, D Basically what I'm asking is, is there a gotcha in how rwho determines who to tell about itself or alternatively who to listen to. I thought rwho was pretty straight forward, am I wrong ? Could it have something to do with addressing schemes which changed here a little while back (I can't categorically blame that as I did not notice the behavior for a while). Also, all machines can rlogin etc to each other. Thoughts ? -- <<<<<<<<<<<<<<<<<<<<<<<<< Nigel Harwood >>>>>>>>>>>>>>>>>>>>>>>>>>> << Post: Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >> << Phone: +61 3 829 6090 E-mail: nigel@cnw01.storesys.coles.oz.au >> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
08071TCP@MSU.BITNET (Doug Nelson) (12/13/90)
>I have a situation where some machines on our TCP/IP network are not >listing all other machines when an rwho or ruptime is done. > >The majority of these machines are running Excelan TCP/IP on V.2 >although one is running Win TCP/IP on V.3. > >All machines have complete /etc/hosts files. > >Machine A will list A, B, C, D > >Machine B will list B, C > >Machine D will list A, B, C, D > >Basically what I'm asking is, is there a gotcha in how rwho >determines who to tell about itself or alternatively who >to listen to. > >I thought rwho was pretty straight forward, am I wrong ? > >Could it have something to do with addressing schemes which >changed here a little while back (I can't categorically >blame that as I did not notice the behavior for a while). > >Also, all machines can rlogin etc to each other. "rwho" relies on broadcasts from the other systems. Therefore, I'd guess that your systems don't all agree on what to use for the IP broadcast address. You should use either <network>.<subnet>.<all one's> or <all ones> (32 bits) for the broadcast address, but be consistent among all systems. If you aren't the network administrator, be sure to contact that person to get the proper address. If you have a large network, though, I would not recommend running "rwhod" at all. It's not much more than a waste of network bandwidth. That's one of the first things I make sure is removed from systems on our network. Doug Nelson Network Software Manager Michigan State University d .edu> d .edu>,