NIS binding probs w/Firewall and SELinux

[Scott Ehrlich]

Hi Matt et al:

The problem ended up being my forgetting about ypinit -m.   Once run, the 
server was very happy.

Thanks again to all!

Scott

On Fri, 7 Sep 2007, Matthew Gillen wrote:

> Matthew Gillen wrote:
>> Scott Ehrlich wrote:
>>>> The 'rpcinfo' command is your friend:
>>>> /usr/sbin/rpcinfo -p serverhostname
>>>>
>>>> from both the server and clients will tell you what's currently
>>>> registered
>>>> with the portmapper.
>>> The other big question would be what default ports nis uses.  I know I
>>> have nfs configured for firewall passthru, but not sure if NIS uses the
>>> same ports.
>>
>> Running that command against my nis server yields:
>> /usr/sbin/rpcinfo -p <server>
>>    program vers proto   port  service
>>     100000    4   tcp    111  portmapper
>>     100000    3   tcp    111  portmapper
>>     100000    2   tcp    111  portmapper
>>     100000    4   udp    111  portmapper
>>     100000    3   udp    111  portmapper
>>     100000    2   udp    111  portmapper
>>     100000    4     0    111  portmapper
>>     100000    3     0    111  portmapper
>>     100000    2     0    111  portmapper
>>     100024    1   udp  32770  status
>>     100024    1   tcp  53071  status
>>     100004    2   udp   1022  ypserv
>>     100004    1   udp   1022  ypserv
>>     100004    2   tcp    601  ypserv
>>     100004    1   tcp    601  ypserv
>> ... <nfs stuff follows>
>>
>> So it looks like at least 111/tcp+udp and 601/tcp+udp will need to be open.
>>  The "status" stuff is probably nfs-related.
>
> I meant 111/tcp+udp, 1022/udp, and 601/tcp.  But you get the idea.
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.