Topic: Linux client wont see e-smith Samba shares

[ewomack]

My Windows machines see the Samba shares (I-Bays) and read & write to them just fine.  My Linux machines can see the shares and browse them but cannot write to them.  The user accounts are identical for both systems, so password issues is not the problem.  They are both served DHCP by the e-smith box, so addressing is not an issue.  They are all on the same hub so I don't have a bridging issue.  I have gone so far as to do a command line Samba mount (mount -t smbfs ....) including a username, pasword and the Read/Write mount options but it fails to authenticate.  Any other ideas?

On a similar subject, something "broke" in the transistion from 3.1 to the 4 series that prevents me from installing NFS properly.  Can anyone tell me what was removed or changed so that I might put it back, or was this just a temporary issue in the 4.0beta series?  I would actually be more interested in this solution as it would allow me to have the Linux machines connect to the server in a more "native" language, and I could leave the Samba shares to Windows - which is, of course, native to them.

Thanks

[Hasan Muhammad]

I'm having similar problems  when trying to backup one e-smith server to another using samba shares mounted via /etc/fstab.

I'm getting these error messages:
  smb_proc_readdir_long: name=e-smithfilesusers   estuser*, entries=0, rcls=1, err=5
  smb_refill_dircache: readdir failed, result=-13

Funny thing, it worked fine yesterday.

[ewomack]

The 4.0 final has solved my Samba problems.  At this point I am not sure that I want to try messing with NFS just yet as the Samba is working so well.