Greetings Nate, On 04-05-03, nate transmitted the following; % C-Cose Masters said: % % > Is there any way that either portsentry or ipchains is interfering with % > communication? % % yes this is very likely % Although likely, flushing my chains had no positive effect.
% > % > I've attempted to install with portsentry stopped, but haven't yet tried % > to alter my ~limited~ chains scripts. % > % > Also, while problem solving I've: % > % > 1 checked inetd.conf for RPC services and restarted it with them % > commented out. % > Result: no change % % nfs-related RPC stuff runs standalone (/etc/init.d/nfs-common) % % for now ipchains -F % done ... % and restart portmapper and nfs-common % % /etc/init.d/portmap restart % done .. with the following results: pmap_getmaps rpc problem: RPC: Unable to receive; errno = Broken pipe Stopping portmap daemon: portmap. Starting portmap daemon: portmap. % /etc/init.d/nfs-common restart % done ... % run rpcinfo -p % done ... again with negative results: rpcinfo: can't contact portmapper: rpcinfo: RPC: Unable to receive; errno = Connection reset by peer % should work now.. % should ... but hasn't % try starting the nfs server % % then run your ipchains scripts again, you'll probably have to tune them, % I recommend having most/all of your blocking rules tied to your external % interface to make it cleaner (use the option -i eth0 in the ipchains % command if eth0 is your external interface) % I currently have all prohibitive scripts locked on to only my ppp0 (external) interface. All local traffic (LAN and lo) is fully allowed. % nate Any other help to offer Nate? This is really beginning to irk me, as everything worked just jim-dandy with the potato nfs-server pkg. Silly me didn't need it at the time so Purge it went. C-Cose -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
