I am getting this bizarre error with SuSE 11.0. I have samba set up and configured properly (I think) via the tutorials. I can see network shares and drill into the folders, on my NAS for instance, as well as Windows computers, but I can’t browse any files, when I open a folder, I get an error dialog for each file “file does not exist”, and they are listed in red with an exclamation point. Does anybody have any idea what’s causing this?
On Sat November 1 2008 12:36 pm, guyonearth wrote:
>
> I am getting this bizarre error with SuSE 11.0. I have samba set up and
> configured properly (I think) via the tutorials. I can see network
> shares and drill into the folders, on my NAS for instance, as well as
> Windows computers, but I can’t browse any files, when I open a folder, I
> get an error dialog for each file “file does not exist”, and they are
> listed in red with an exclamation point. Does anybody have any idea
> what’s causing this?
>
>
guyonearth;
Are you getting these problems from the Windows machine? If so it may be a
permission problem on the files. Make sure they are at least readable by
others. Something like mode 664 or 666. If the problem is only on the SuSE
machine, it may be the GUI. What GUI are you using?
P. V.
Cogito cogito ergo cogito sum.
I am using KDE 3.5. The problem occurs when trying to access files on a NAS running naslite (linux-based). When I try to access Windows machines I get prompted for a username/password. (not sure what to enter, as the machines in question don’t have set passwords). The NAS works fine from all the other machines, I accessed it from WinXP, 2000, and MacOSX.
It’s definitely a SuSE problem, as I have just booted to Ubuntu on the same computer and network browsing is quick and seamless. I’ve been a SuSE fan for a long time, but they could take some lessons from how Ubuntu does it. Anyway, I also ran the sscw script to test the samba setup and everything checks out. I hope someone has a solution, because otherwise this is a deal-killer, I need to access network shares.
On Sat November 1 2008 03:26 pm, guyonearth wrote:
>
> It’s definitely a SuSE problem, as I have just booted to Ubuntu on the
> same computer and network browsing is quick and seamless. I’ve been a
> SuSE fan for a long time, but they could take some lessons from how
> Ubuntu does it. Anyway, I also ran the sscw script to test the samba
> setup and everything checks out. I hope someone has a solution, because
> otherwise this is a deal-killer, I need to access network shares.
>
>
guyonearth;
KDE3.5 should work well. I’m not familiar with the NAS, but here are some
ideas:
-
If you have not done so already add Samba Users on Suse; In a terminal su
to root and run:
smbpasswd -a <username>
Username must be a valid linux user name for your machine but the password
does not need to be the same as the login password.
Use this name and password on Windows, or try using “guest” with a blank
password. -
Check the samba log to see if it gives you some hint;
/var/log/samba/log.smbd
If nothing shows up here, then increase the log level. To do this, as root
edit /etc/samba/smb.conf by adding the parameter “log level = 3” to the
global section; then restart smbd (su to root enter “rcsmb restart”). Now
monitor the log file. Once you are done debugging be sure to remove the log
level parameter, to keep your logs to a manageable size. -
Finally, if all this fails, post the contents of /etc/samba/smb.conf.
–
P. V.
Cogito cogito ergo cogito sum.
I was unable to browse windows shares as well. Then I found out it was a firewall “feature”. Solution was to add samba browsing for my local network in Yast’s firewall settings.
So, in the Broadcast menu click “add”, select external zone and samba browsing and type in your network details. For me that is 192.168.1.0/24.
Hope, that helps…
The log says nothing except that the service started. I did add the samba user already, that was one of the first things I did.
Here is the contents of the samba.conf:
smb.conf is the main Samba configuration file. You find a full commented
version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
samba-doc package is installed.
Date: 2008-08-28
[global]
workgroup = earthcity
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
#logon path = \%L\profiles.msprofile
#logon home = \%L%U.9xprofile
#logon drive = P:
usershare allow guests = Yes
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = No
domain master = No
security = user
local master = yes
os level = 33
netbios name = ninthcomp
name resolve order = bcast host lmhosts wins
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = Yes
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775
Share disabled by YaST
[netlogon]
I’m not sure if I really got your point. I thought you wanted to access samba or Windows shares from your Suse11 desktop as you do with your windows and mac computers. If that’s the case you don’t need to care about smb.conf on your Suse computer. smb.conf is used by the samba server, not the samba client. Did you try the firewall thing from my previous post?
Finally, if my posts don’t make any sense then give me a bad reputation, because I really don’t know whether my suggestions help people, confuse them or are just stupid.
On Sat November 1 2008 08:16 pm, guyonearth wrote:
>
> The log says nothing except that the service started. I did add the
> samba user already, that was one of the first things I did.
> Here is the contents of the samba.conf:
>
<snip>
>
I see nothing in your smb.conf that would account for the behavior you
describe. I would like to try to sort out your problems with Windows first
and then concentrate on the NAS.
Did you try to authenticate on your Windows Machine(s) with username “guest”
and a blank password? “Guest” is a built in user in Windows and will be used
to authenticate a user without a Windows account.
Try looking at your Windows logs to see if we can see how authentication is
progressing there.
Control Panel–>Administrative Tools–>Event Viewer–>Security
You would expect to see 3 or more entries.
Have you upped the log level in Samba as I suggested?
It’s possible your NAS uses the older Lanman style of authentication, this was
disabled with Samba3.2.x. Add to your smb.conf the following two parameters:
Lanman auth = yes
Client Lanman auth =yes
These were the defaults in Samba3.0.X, which may explain why Ubuntu works.
You need to edit /etc/samba/smb.conf as root. The easy way in KDE3 is to
use “File Manager-Super User Mode”; navigate to your smb.conf; right click on
the file and choose “open with” then choose Kword or Kate (what ever editor
you like).
–
P. V.
Cogito cogito ergo cogito sum.
On Sat November 1 2008 09:56 pm, PV wrote:
> On Sat November 1 2008 08:16 pm, guyonearth wrote:
>
>>
>> The log says nothing except that the service started. I did add the
>> samba user already, that was one of the first things I did.
>> Here is the contents of the samba.conf:
>>
> <snip>
>>
> I see nothing in your smb.conf that would account for the behavior you
> describe. I would like to try to sort out your problems with Windows first
> and then concentrate on the NAS.
> Did you try to authenticate on your Windows Machine(s) with username “guest”
> and a blank password? “Guest” is a built in user in Windows and will be
> used to authenticate a user without a Windows account.
>
> Try looking at your Windows logs to see if we can see how authentication is
> progressing there.
> Control Panel–>Administrative Tools–>Event Viewer–>Security
> You would expect to see 3 or more entries.
>
> Have you upped the log level in Samba as I suggested?
>
> It’s possible your NAS uses the older Lanman style of authentication, this
> was
> disabled with Samba3.2.x. Add to your smb.conf the following two
> parameters:
>
> Lanman auth = yes
> Client Lanman auth =yes
>
> These were the defaults in Samba3.0.X, which may explain why Ubuntu works.
>
> You need to edit /etc/samba/smb.conf as root. The easy way in KDE3 is to
> use “File Manager-Super User Mode”; navigate to your smb.conf; right click
> on the file and choose “open with” then choose Kword or Kate (what ever
> editor you like).
>
Be sure you restart smb after you edit smb.conf. To do this open a terminal,
su to root, and enter “rcsmb restart”.
Just to rule out a firewall problem, try dropping the firewall while testing.
supertimorplusfort may have a point, but I think if you can get as far as
seeing the shares your firewall must be configured correctly. There is
always a chance that one of the ports you need is closed.
–
P. V.
Cogito cogito ergo cogito sum.
OK, I seem to have got this more or less solved. First, I tried smb4k, which worked once I modified mount.cifs permissions. Then I added my NAS to fstab, mounted cifs guest to a fully writeable directory. Either method seems to work well, it’s just not as seamless as I thought it would be. It apparently was not a Samba issue as such, but I wish the SuSE developers would put some effort into making network resources available without all this extra work. A person shouldn’t have to do any custom configuring to get the network to show up in the browser, that seems obvious to me, if you’re trying to have any kind of a user-friendly experience at all. Just my 2 cents.
nothing works…I can’t get samba to work either…
mkather wrote:
> Hi, I have exactly the same problem towards a SuSE 7.0 share. There is a
> new Samba version in SuSE 11, it’s just not fully tested,
> alpa-version at most. Forget about it and go back to SuSE 10.2
10.2 is discontinued, do not use.