There are actually dozens of files in the mounted directory. It mounts the same file system from the same server as the embedded systems, but it works fine on this machine. I think that's videolan client - not available on the embedded systems, and I don't see what it would tell me. What are the permissions on the exported share and on the mount point?
On the affected clients, I can use (edit, cat, execute) any file if I know the exact path. Being able to display files in a directory but not list them can occur when the directory does not have the "execute" permission set.
If you are using a firewall, you must explicitly allow traffic from your local subnet to access the server.
For users with only local NT user accounts, you must specify the user profile path name in each user account on each client.
If you have an NT domain set up with domain user accounts, you can specify the user profile path in the user's account on the domain controller.
The mount succeeds, and I can read and write files. After the update, the current version of nfs-kernel-server is 1:1.2.5-3ubuntu3.1. $ mount /dev/root on / type yaffs (rw) none on /dev type devfs (rw) proc on /proc type proc (rw) 192.168.1.10:/home on /mnt/copper type nfs (rw,v3,rsize=32768,wsize=32768,hard,udp,lock,addr=192.168.1.10) $ ls /mnt/copper $ echo "test" Normal clients means other relatively modern linux machines.
The example below is from a console session on one of the embedded clients (they all act the same way). I can create a file on it and read the file, but a directory listing shows nothing. I'm typing this on a client running xubuntu 12.10, for instance.
You can create user profiles on the client running Windows NT and store them on an NFS server.