NIS binding probs w/Firewall and SELinux
Matthew Gillen
me-5yx05kfkO/aqeI1yJSURBw at public.gmane.org
Fri Sep 7 01:39:08 EDT 2007
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.
HTH,
Matt
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the Discuss
mailing list