I have fixed the problems with all the error messages, The server was
using an ancient RTL8029, i replaced it with an e100, and the whole
network is now flying.
I still know why it is not using tcp, but this is not so important now.
Thank You
Ben.
On 31/10/05, Ben Sagal <[EMAIL PROTECTED]> wrot
I have tried to mount it with on tcp, the dhcp sends the following for rootpath:
"192.168.1.1:/srv/client,ro,tcp,hard,intr"
but the tcp part seams to be ignored by the client,
I have confirmed the server can handle tcp since i have been
successful in connecting using tcp from another (non-diskl
Ben Sagal ([EMAIL PROTECTED]) wrote:
>
> I have a few diskless clients setup, using a read-only nfs root, and
> with a tmpfs mounted for /var, /home and /tmp. The system regularly
> prints the following messages:
>nfs: server 192.168.1.1 not responding, still trying
>nfs: server 192.168.1.
I have a few diskless clients setup, using a read-only nfs root, and
with a tmpfs mounted for /var, /home and /tmp. The system regularly
prints the following messages:
nfs: server 192.168.1.1 not responding, still trying
nfs: server 192.168.1.1 OK
the output from mount on the client is:
/
4 matches
Mail list logo
