Samba troubles in Suse, "location no longer available"
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Samba troubles in Suse, "location no longer available"
Hello,
I am running Suse Linux 10.0 with no firewalls on and I am trying to set up my samba server.
But If i try to move a file over 300 or so megabytes, I get a "the specified path is no longer available" message. I can copy small files into the directory and I can play/use any files without any troubles, its just copying larger files on there where the trouble occurs. I have tried a lot of things, with nothing working. Any help would be appreciated. I just want it to work like it does in windows, flawlessly.
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2006/05/01 08:50:43
[global]
workgroup = MSHOME
netbios name = MBOXX
server string = mboxx
map to guest = Bad User
server signing = auto
printcap name = cups
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
logon path = \\%L\profiles\.msprofile
logon drive = P:
logon home = \\%L\%U\.9xprofile
preferred master = No
local master = No
domain master = No
wins support = Yes
ldap ssl = no
guest ok = Yes
cups options = raw
include = /etc/samba/dhcp.conf
[homes]
comment = Home Directories
valid users = %S
read only = No
inherit acls = Yes
browseable = No
[comedy]
path = /windows/D/Comedy/
read only = No
[concerts]
path = /windows/D/Concerts/
read only = No
[dothacker]
path = /windows/D/dotHACKER_/
read only = No
[jackass]
path = /windows/D/Jackass/
read only = No
[music videos]
path = /windows/D/Music Videos/
read only = No
[other]
path = /windows/D/other/
read only = No
[music]
path = /windows/E/music/
read only = No
[stuffo]
path = /windows/E/stuffo/
read only = No
[tv shows]
path = /windows/E/TV Shows/
read only = No
personally.. start over. Start clean with your samba. Set it up with yast and make sure you have room. Can you pull a big file? Is this a full suse install? All your network cables are good? Are you mapping this to your windows machine or just opening a folder?
Thanks for the reply... I have actually totally started over twice. I am not sure if it has to do with fat32 file systems or if samba on linux just isnt that polished. I tried what you suggested, moving files from the server and I moved two 700 meg files, and I got the same "no longer available" dialog... Any other ideas?
hmm. For my setup I had to map the drive because I am logging into my windows box with a different user/passwd than my suse box. In mapping it i was able to specify who I wanted ( and give myself appropriat rights ) to connect. Your smb.conf file looks pretty intense. Mine is as follows.
Quote:
[global]
encrypt passwords = yes
guest account = smbguest
netbios name = Storage
security = share
socket options = TCP_NODELAY IPTOS_LOWDELAY
wins support = no
workgroup = cluster
[public]
path = /mnt/pub
read only = no
guest ok = yes
guest only = yes
[data]
path = /mnt/raid1
read only = no
guest ok = no
users = root j guest
[media]
path = /mnt/raid2
read only = no
guest ok = no
users = mw jbob j root
Storage is the computer name. and I log into windows mostly with 'user' so i had to map the drive as root. I have some other accounts on there, but you should get the idea. I'll think on this a bit, but I hope that helps.
I have tried tonight going over simple with the global settings with no success still. All I want is an open smb server where no authentication is needed to add large files to my computer from a windows machine. I did not realize it would be such a hurdle.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.