Off the top off my head and frm cellpphone - check foor any secuurity style acls like selinux/auditd on that machine - yuu may have to explicitly allow file and/or net socket ooperations. I had a similar problem once with a net service and that was the issuue -----Original Message----- From: Richard Nairn <Richard@xxxxxxxxxxxxxxxxxx> Sent: Friday, August 08, 2008 4:38 PM To: linux-admin@xxxxxxxxxxxxxxx <linux-admin@xxxxxxxxxxxxxxx> Subject: RPC problems Hi, After upgrading to Fedora 8, RPC no longer seems to be working. I can't get ypserv, ypbind, NFS to work anymore. rpcbind seems to start happily, and rpcinfo will list it as working: program version netid address service owner 100000 4 tcp 0.0.0.0.13.93 portmapper superuser 100000 3 tcp 0.0.0.0.13.93 portmapper superuser 100000 2 tcp 0.0.0.0.13.93 portmapper superuser 100000 4 udp 0.0.0.0.13.93 portmapper superuser 100000 3 udp 0.0.0.0.13.93 portmapper superuser 100000 2 udp 0.0.0.0.13.93 portmapper superuser 100000 4 local /var/r portmapper superuser 100000 3 local /var/r portmapper superuser 100000 2 local /var/r portmapper superuser However, once I try and start ypbind, or ypserv I get a Unable to register (YPBINDPROG, YPBINDVERS,udp) in my log file, and a similary thing for ypserv. I have tried to reinstall the rpms for rpcbind, ypserv,ypbind but it still fails. Any suggestions? -- To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html