Hello,
I have a client PC running Win98 SE that is networked to a Sun Ultra 5 workstation running Solaris 2.5.1. When the client tries to mount exported file systems on the Sun, the operation fails returning error 67 -- ENOLINK link severed). I am able to telnet to and ping the Sun machine and the Sun can ping the client. I've also verified that nfsd and mountd are running on the Sun system and that the file system I'm trying to mount shows up in /etc/dfs/sharetab.
I've been through the process of getting NFS running before on an identical setup and was under the impression that getting NFS working on the server side was as simple as setting up the appropriate entries in /etc/dfs/dfstab:
share -F nfs /filesystem
and rebooting the machine (or restarting NFS). Is this true? I don't think this is a client side issue because the same PC with no changes is able to mount drives fine
on another Sun machine running the same OS. Anyone have any ideas?
Russ
bobbitts@hotmail.com
I have a client PC running Win98 SE that is networked to a Sun Ultra 5 workstation running Solaris 2.5.1. When the client tries to mount exported file systems on the Sun, the operation fails returning error 67 -- ENOLINK link severed). I am able to telnet to and ping the Sun machine and the Sun can ping the client. I've also verified that nfsd and mountd are running on the Sun system and that the file system I'm trying to mount shows up in /etc/dfs/sharetab.
I've been through the process of getting NFS running before on an identical setup and was under the impression that getting NFS working on the server side was as simple as setting up the appropriate entries in /etc/dfs/dfstab:
share -F nfs /filesystem
and rebooting the machine (or restarting NFS). Is this true? I don't think this is a client side issue because the same PC with no changes is able to mount drives fine
on another Sun machine running the same OS. Anyone have any ideas?
Russ
bobbitts@hotmail.com