[NTLUG:Discuss] SAMBA Problem (I Think)

Bryan J. Smith b.j.smith at ieee.org
Thu Dec 23 22:56:41 CST 2004


Is the SMB share native NT or a Samba server?
If the former, I recommend you install Services for UNIX and share out via NFS.
If the later, then share it out via native NFS.

Samba client is fair for basic operations only.
And that's largely only to Samba servers.
For native SMB servers, Microsoft licensed Integraph NFS (fka Sun PC-NFS) for a reason.
NFS is far more native to UNIX clients.

Also consider using the automounter and advanced NFS options
(such as "bg", "intr" for backgrounding and interruptable mounts).
SMB does not offer equivalent state operation.


-- 
Bryan J. Smith (currently mobile)
b.j.smith at ieee.org

-----Original Message-----
From:  Scott Hollomon 
Date:  04-12-23 19:47
To:  NTLUG Discussion List 
Subj:  [NTLUG:Discuss] SAMBA Problem (I Think)

On a linux server running CentOS 3.3 (essentially RHEL 3) and Samba 3.07131 I 
am sharing a directory /home/1data on my home network.  When I attempt to 
access this share from a Linux machine which mounts the share from fstab and 
browse share with Konqueror, Konqueror locks up whenever I browse more than 
two directories deep.  Not only does Konq lock up, but I can't access the 
share from a terminal.  I have tried to access the share with machines 
running SuSE 9.2 pro and MEPIS, both running KDE 3.3.1.  

I have never run across anything like this.  There are other shares on the 
server and none of them have this problem.  The SuSE machine is a laptop and 
I use it to connect to numerous SMB shares without any issues.

I ran across one set of posts on an SuSE mailing list from two years ago where 
someone had this type of problem, but no answers were given.

Is this a Samba problem, a KDE problem, a Kernel problem, what?  Where do I 
start to figure this out?


-- 
Scott Hollomon
Collin Street Bakery, Inc.
scott at collinstreet.com

_______________________________________________
https://ntlug.org/mailman/listinfo/discuss



More information about the Discuss mailing list