Re: NFS connection dropped

> It gets very tricky very quickly. You can look up the allocated port numbers 
> on the machine that is running Guarddog, but that doesn't really work when 
> you want to connect (as a client) to a remote NFS share. (= need the port 
> numbers for the remote machine). And it doesn't work when Guarddog is on a 
> gateway machine and NFS is just passing through Guarddog. In that case you 
> need to know the port numbers for the NFS servers on either side of the 
> gateway. very ugly. NFS was put together before firewalls were a concern, 
> which is why it sucks so much. The only remotely practical solution is to pin 
> down the ports numbers on all of your NFS machines.

Simon,

Thanks for the explanation. It is a messy situation!

Perhaps the "protocol help" text could be updated for NIS and NFS to 
mention that additional ports need to be pinned and manually defined and 
opened before NIS and NFS will actually work with GD. That will save 
some grief for users in the future! It takes a lot of debugging to 
figure this out on your own :-(


- Mike


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf