Hi,
I have this problem: OpenSuse 10.3 can browse the Windows xp shared folders but Windows can’t do the opposite. :’(
From Windows is possible to see the folder but not the files.
I follow also the Suse official guide to configure samba, but althought everythings seems to be ok it’s impossibile to share linux files.
Does anybody have an idea to resolve it?
Thanks.
P.S. Suse and Windows have the same user and the same password.
I haven’t tried samba for quite a while, but have a look at the samba howtos. When I did use it, I found it easier to use swat (samba web interface/admin) to configure it.
Also, look at this thread:
Samba: accessing an openSUSE server from a windows client - openSUSE Forums
To configure Samba I’ve just just swat, it was explained in the official suse guide.
About the three possibile solution, two of those aren’t aaplicabile in my case (I haven’t installed zone alarm and I’ve only one computer running linux.
Concerning the wins, where I can check the setting “Use WINS for hostname resolution”?
Thought: For diagnostic purposes try turning of the firewall at Yast → Security and users → Firewall → Disable firewall auto start + stop firewall now. That’s just temporary until you fix the problem. Reboot first Suse then windows and see if windows can see Suse. You need to be patient 5-10 minutes.
Another thought: do you have a netbios name defined in [global] of smb.conf plus a direction to use broadcast name resolution. They’re these two
netbios name = blahblah
name resolve order = bcast host lmhosts wins
Another thought: is the workgroup in smb.conf the same as in windows
Please post here the contents of smb.conf (located at /etc/samba/smb.conf) so I can see if something is wrong other than the firewall.
At this stage it’s not a good idea to go turning on WINS which is almost never used in a SOHO workgroup (but then I don’t know what you’re using the LAN for).
Thought: For diagnostic purposes try turning of the firewall at Yast → Security and users → Firewall → Disable firewall auto start + stop firewall now. That’s just temporary until you fix the problem. Reboot first Suse then windows and see if windows can see Suse. You need to be patient 5-10 minutes.
I disable the firewall and something is changed: in konqueror now I can see the workgroup, but if I want to see the windows folder I have to write the numerical address as usually. Windows can’t still see suse.
Another thought: do you have a netbios name defined in [global] of smb.conf plus a direction to use broadcast name resolution
Quote:
netbios name = blahblah
name resolve order = bcast host lmhosts wins
netbios name = SUSE-SAMBA
I don’t have name resolve order
Another thought: is the workgroup in smb.conf the same as in windows
Yes. I don’t know if it’s important the upper or lower case.
Please post here the contents of smb.conf (located at /etc/samba/smb.conf) so I can see if something is wrong other than the firewall.
[global]
workgroup = CASA
netbios name = SUSE-SAMBA
server string = Suse-Samba
map to guest = Bad User
acl compatibility = winnt
server signing = auto
printcap name = cups
logon path = \%L\profiles.msprofile
logon drive = P:
logon home = \%L%U.9xprofile
os level = 2
preferred master = No
local master = No
domain master = No
ldap ssl = no
usershare allow guests = Yes
usershare max shares = 100
valid users = ema
admin users = root
hosts allow = 192.168.1.
printing = cups
cups options = raw
print command =
lpq command = %p
lprm command =
[homes]
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
create mask = 0600
directory mask = 0700
store dos attributes = Yes
[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
create mask = 0600
printable = Yes
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin, root
force group = ntadmin
create mask = 0664
directory mask = 0775
[home_ema]
path = /home/ema/
read only = No
guest ok = Yes
case sensitive = No
strict locking = No
msdfs proxy = no
On Fri January 2 2009 08:46 am, ciampucci wrote:
>
>> Thought: For diagnostic purposes try turning of the firewall at Yast →
>> Security and users → Firewall → Disable firewall auto start + stop
>> firewall now. That’s just temporary until you fix the problem. Reboot
>> first Suse then windows and see if windows can see Suse. You need to be
>> patient 5-10 minutes.
>
> I disable the firewall and something is changed: in konqueror now I can
> see the workgroup, but if I want to see the windows folder I have to
> write the numerical address as usually. Windows can’t still see suse.
>
>> Another thought: do you have a netbios name defined in [global] of
>> smb.conf plus a direction to use broadcast name resolution
>> Quote:
>> netbios name = blahblah
>> name resolve order = bcast host lmhosts wins
>
> netbios name = SUSE-SAMBA
>
> I don’t have -name resolve order-
>
>> Another thought: is the workgroup in smb.conf the same as in windows
>
> Yes. I don’t know if it’s important the upper or lower case.
>
>> Please post here the contents of smb.conf (located at
>> /etc/samba/smb.conf) so I can see if something is wrong other than the
>> firewall.
>
> # Samba config file created using SWAT
> # from 127.0.0.1 (127.0.0.1)
> # Date: 2009/01/02 01:12:15
>
> [global]
> workgroup = CASA
> netbios name = SUSE-SAMBA
> server string = Suse-Samba
> map to guest = Bad User
> acl compatibility = winnt
> server signing = auto
> printcap name = cups
> logon path = \%L\profiles.msprofile
> logon drive = P:
> logon home = \%L%U.9xprofile
> os level = 2
> preferred master = No
> local master = No
> domain master = No
> ldap ssl = no
> usershare allow guests = Yes
> usershare max shares = 100
> valid users = ema
> admin users = root
> hosts allow = 192.168.1.
> printing = cups
> cups options = raw
> print command =
> lpq command = %p
> lprm command =
>
> [homes]
> comment = Home Directories
> valid users = %S, %D%w%S
> read only = No
> inherit acls = Yes
>
> [profiles]
> comment = Network Profiles Service
> path = %H
> read only = No
> create mask = 0600
> directory mask = 0700
> store dos attributes = Yes
>
> [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
> create mask = 0600
> printable = Yes
> browseable = No
>
> [print$]
> comment = Printer Drivers
> path = /var/lib/samba/drivers
> write list = @ntadmin, root
> force group = ntadmin
> create mask = 0664
> directory mask = 0775
>
> [home_ema]
> path = /home/ema/
> read only = No
> guest ok = Yes
> case sensitive = No
> strict locking = No
> msdfs proxy = no
>
>
ciampucci;
Is nmb running? To check:
ps -A | grep nmb
nmb needs to be running for name resolution, so if not turn it on in YAST.
It would also be wise to make the following changes to
your /etc/samba/smb.conf global section.
Add:
name resolve order = bcast host lmhosts wins
Change:
local master = Yes
domain master = Yes
preferred master =Yes
os level = 35
The name resolve order is important, the 4 changes are less important, but
samba seems to work best when it is the master browser.
Be sure to add Samba users with:
smbpasswd -a <username>
swerdna has written a very good tutorial for OpenSuse here:
http://www.swerdna.net.au/linux.html
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Ok. I’m not at home. I’ll check as soon as arrive and I’ll post the results.
Also thanks for the swerdna’s site.
I have to guess at the purpose/environment of your LAN so I guess a workgroup of independent workstations (not with a Primary Domain Controller like in a business with 40 machines) is that right?
In addition to PV’s suggestions, these:
1: You are sharing ema’s /home directories twice. Once with the share [home-ema] and once with the share [homes]. Did you mean to do that?
2: This could mean a couple of things: “From Windows is possible to see the folder but not the files”. Does that mean that you can see folders but can’t drill down to them? I guess “yes”? If “yes” = true then the next comments follow:
3(a): In the share [home-ema] try removing this line: msdfs proxy = no, because it can cause to return the message “file or folder does not exist”.
3(b): Another thought re [home-ema]: you have guest access. So changes in /home/etc/… by guests will be attributed to a user called “nobody”. Better to have the structur below so all the changes be attributed to owner “ema”.
[home_ema]
path = /home/ema/
read only = No
guest ok = Yes
force user = ema
“Force user” will make all files and directories remain as owned by ema, regardless of guest changes, so a bunch of different owners will not be created for files there. And I wonder do you really want “guest ok = yes” together with “valid users = ema”, seems inconsistent to me. What do you mean to have in that regard, a limiting to ema with valid users, or open to the world with guests?
If you really want case sensitive and strict locking, leave them there, but maybe you don’t?
4: To penetrate the shares [homes], [profiles] ,[users] you need as PV suggested to put user/s into the samba user database, but since you’ve set “valid users = ema” it should only be ema in the database I suppose.
5: IIRC [groups] doesn’t exist until you create the directory groups, but you have already so many shares you might as well turn it off or delete it.
6: If this is a SOHO LAN, you might try this extension of PV’s suggestion for [global]:
[global]
workgroup = CASA
netbios name = SUSE-SAMBA
name resolve order = bcast host lmhosts wins
map to guest = Bad User
local master = yes
preferred master = yes
os level = 33
server string =""
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
use client driver = yes
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False
valid users = ema
hosts allow = 192.168.1.
If you really really mean it you could include also “admin users = root” (check it in smb.conf on this link)
Oh and a couple of afterthoughts:
Might like to read about openSUSE’s default shares
And this:
I disable the firewall and something is changed: in konqueror now I can see the workgroup, but if I want to see the windows folder I have to write the numerical address as usually. Windows can’t still see suse.
That might improve with netbios naming tweaked as above. Also, either leave firewall turned off (bad idea) or configure it for Samba, perhaps using this method: Configure SuSEfirewall2 for Samba.
Ok, now it’s working, I can see the files and write on it! rotfl!
Here the answer to the question/doubt of swerdna and PV
Is nmb running?
Change:
local master = Yes
domain master = Yes
preferred master =Yes
os level = 35
Add:
name resolve order = bcast host lmhosts wins
Be sure to add Samba users with:
Code:smbpasswd -a <username>
I have to guess at the purpose/environment of your LAN so I guess a workgroup of independent workstations (not with a Primary Domain Controller like in a business with 40 machines) is that right?
You are sharing ema’s /home directories twice. Once with the share [home-ema] and once with the share [homes]. Did you mean to do that?
3(a): In the share [home-ema] try removing this line: msdfs proxy = no, because it can cause to return the message “file or folder does not exist”.
3(b): Another thought re [home-ema]: you have guest access. So changes in /home/etc/… by guests will be attributed to a user called “nobody”. Better to have the structur below so all the changes be attributed to owner “ema”.
[home_ema]
path = /home/ema/
read only = No
guest ok = Yes
force user = ema
I removed the hare [home-ema] and I leaved only this one:
[homes]
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes
To penetrate the shares [homes], [profiles] ,[users] you need as PV suggested to put user/s into the samba user database, but since you’ve set “valid users = ema” it should only be ema in the database I suppose.
Also, either leave firewall turned off (bad idea) or configure it for Samba
I reactivated the firewall (it was configured for samba already) and it works.
Thank you very much (sorry for my poor English) and greetings to everybody for a new bright year.
Glad you’re happy! Can I have a link to the picture, I’m interested to really see it. Can’t see it in the 1.5"x1.25" (my screen) thumbnail.
Can I have a link to the picture, I’m interested to really see it. Can’t see it in the 1.5"x1.25" (my screen) thumbnail.
Here the link: netbios.jpg - DivShare
It’s traslate in Italian (my language), but you can understand we are in the control center.
Thankyou. I see it now. KDE control centre.
The name reslove order is the order of the methods the netbios naming daemon tries to find the list of netbios names -vs- IP addresses of the various workstations.
You had it set to try as follows: lmhosts wins host bcast
lmhosts: First it looks in the the file /etc/samba/lmhosts for the list – but the file is empty
wins: Second it looks for a wins server to ask the wins server for the list – but there isn’t a wins server
host: Third it looks in the file /etc/hosts for a list – nut it’s not in the hosts file
bcast: Fourth it broadcasts to the machine that has been elected as the Browse Master for the workgroup to ask for the list – and that’s the only way that will work, but since it was last in the methoods to try, it went to sleep from boredom first and failed.
That’s why it wasn’t working and why for a workgroup you normally put “bcast” first, before the useless options, so it can discover the list straight away.
Interesting stuff!