UPDATE - More Info -- YP Headaches

[Rick Stevens]

Waldher, Travis R wrote:
>  
> 
> 
>>-----Original Message-----
>>From: Rick Stevens [mailto:rstevens at vitalstream.com] 
>>Sent: Friday, September 03, 2004 9:59 AM
>>To: Getting started with Red Hat Linux
>>Subject: Re: UPDATE - More Info -- YP Headaches
>>
>>Waldher, Travis R wrote:
>>
>>> > -----Original Message-----
>>>
>>>
>>>>From: Waldher, Travis R
>>>>Sent: Friday, September 03, 2004 9:00 AM
>>>>To: Getting started with Red Hat Linux
>>>>Subject: YP Headaches
>>>>Importance: High
>>>>
>>>>
>>>>When I try to change my NIS password:
>>>>
>>>>[trw3016 at rpdsppc3 trw3016]$ yppasswd -p
>>>>yppasswd: yppasswdd not running on NIS master host ("~hostname~").
>>>>
>>>>On the NIS Server there is this:
>>>>
>>>>  program vers proto   port
>>>>   100000    2   tcp    111  portmapper
>>>>   100000    2   udp    111  portmapper
>>>>   100024    1   udp  32768  status
>>>>   100024    1   tcp  32768  status
>>>>   100004    2   udp    797  ypserv
>>>>   100004    1   udp    797  ypserv
>>>>   100004    2   tcp    800  ypserv
>>>>   100004    1   tcp    800  ypserv
>>>>600100069    1   udp    806  fypxfrd
>>>>600100069    1   tcp    808  fypxfrd
>>>>   100021    1   udp  32795  nlockmgr
>>>>   100021    3   udp  32795  nlockmgr
>>>>   100021    4   udp  32795  nlockmgr
>>>>   100021    1   tcp  32903  nlockmgr
>>>>   100021    3   tcp  32903  nlockmgr
>>>>   100021    4   tcp  32903  nlockmgr
>>>>   100011    1   udp    951  rquotad
>>>>   100011    2   udp    951  rquotad
>>>>   100011    1   tcp    970  rquotad
>>>>   100011    2   tcp    970  rquotad
>>>>   100003    2   udp   2049  nfs
>>>>   100003    3   udp   2049  nfs
>>>>   100003    2   tcp   2049  nfs
>>>>   100003    3   tcp   2049  nfs
>>>>   100005    1   udp    973  mountd
>>>>   100005    1   tcp    989  mountd
>>>>   100005    2   udp    973  mountd
>>>>   100005    2   tcp    989  mountd
>>>>   100005    3   udp    973  mountd
>>>>   100005    3   tcp    989  mountd
>>>>   100007    2   udp    866  ypbind
>>>>   100007    1   udp    866  ypbind
>>>>   100007    2   tcp    869  ypbind
>>>>   100007    1   tcp    869  ypbind
>>>>   100009    1   udp    935  yppasswdd
>>>>   391002    2   tcp  32990  sgi_fam
>>>>
>>>>And:
>>>>
>>>>[root at rpdssvr yp]# ps -ef |grep yppass
>>>>root      3726     1  0 08:46 ?        00:00:00 rpc.yppasswdd
>>>>root      4506  3421  0 08:59 pts/1    00:00:00 grep yppass
>>>
>>>
>>>Ok let's add to the weirdness.  My NIS Master has two NIC's.
>>>
>>>eth0      Link encap:Ethernet  HWaddr 00:50:8B:8F:A9:30
>>>          inet addr:136.203.75.118  Bcast:136.203.75.255 
>>>Mask:255.255.255.0
>>>eth1      Link encap:Ethernet  HWaddr 00:04:76:F5:6C:FF
>>>          inet addr:192.168.0.200  Bcast:192.168.0.255 
>>>Mask:255.255.255.0
>>>
>>>On my 192 client (referencing subnet #) I get this error running
>>>yppasswd:
>>>
>>>[username at 192client username]$ yppasswd
>>>yppasswd: yppasswdd not running on NIS master host 
>>>("rpdssvr.ca.boeing.com").
>>>
>>>If I attempt to telnet to the port indicated in the earlier message:
>>>
>>>On my 136 client, yppasswd works.
>>>
>>>[username at 136client username]$ yppasswd Changing NIS account 
>>>information for trw3016 on rpdssvr.ca.boeing.com.
>>>Please enter old password:
>>>Sorry.
>>>
>>>Any ideas?  I'm REALLY confused now.
>>
>>Have you checked your firewall configuration on the master 
>>server?  It looks like you have some things blocked there.
> 
> 
> Just checked:
> 
> [root at rpdssvr etc]# service iptables status
> Firewall is stopped.

Hmmmm.  It sure looks like yppasswd on the server is only listening
to one interface...that's why I suspected the firewall.

Have you tried "rpcinfo -p name-of-yp-server" on clients on both
networks to see if something is odd with portmapper?
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-           "I understand Windows 2000 has a Y2K problem."           -
----------------------------------------------------------------------