So, I’m attempting to set up a Samba server from a suse Install. I found How To Samba With Suse 10.3 And Windows XP and have been using it as a guide. i got it all the way to the end, with some modifications because i used the latest release of suse. The Computer shows up in the windows network panel, but when i connect i get an error message. Any help is great -Techman9
any hardware Q’s ask
You did not say what the error message was.
Give the following website a shot. It is written by one of the moderators here. I consider it to be the authoritative source for samba shares.
If you still have questions at that point, post them here and Swerdna or someone will do their best to help. He is in Australia and is on a different time zone than most of us, so give him a little time to get on and respond.
Error message was 0x80070035, network path not found. I’ve been trying and i got the Suse computer to view the windows shares, but i need to do it the other way around. Thank you for the web site about samba, but it only describes Suse to Windows. i need a guide on Windows to Suse. BTW, this is windows 7.
Is this wired or wireless? Let’s see some info on what you are using on each end. Is the user for the shares set on each end? Same password on each end? We just have to work through all of it one step at a time. 
Oh, yes. Did you set up the Samba Server in YaST?
yes. i used How To Samba With Suse 10.3 And Windows XP as a guide. BTW, my suse computer dosen’t see itself when i point konquerer to it using smb://ShuttleX, but it shows up in the workgroup. (ShuttleX is the hostname of the comp)
That has to do with the Browse Master. Without a WINs server, you are limited to netbui to set the master browser in a workgroup. Let me see what I can find. I know the info is here on this site. Give me a few minutes to locate it.
ok. thanks so much.
I am searching for Browsemaster and Browse Master. There is a lot of info here.
Take a look at this thread to start. Samba : setting up and tweaking - openSUSE Forums
Also this thread. Windows XP box does not see/access Linux shares - openSUSE Forums
You have to excuse me, but my knowledge on this is quite limited. At home, I had some troubles browsing my NAS from Linux and got that sorted out using Swerdna’s site, but I have not tried browsing Linux shares from Windows before. At work, I manage an all Windows network, so I am just sort of trying to point you in the right directions.
ok. i read through the whole post (i admit i didn’t understand much of it, i’m a total linux newbie), and it seems like mostly firewall issues. I disabled my Suse firewall because i didn’t want to deal with it. my windows to windows connection works fine so it’s not a windows firewall issue. I think i need to change some security settings, i just don’t know what. :shame:
Well, if it is not a firewall issue, which was going to be my next topic, then it has to be permissions, OR the samba server is not quite setup and is not really sharing.
Do a search on this site for posts by Swerdna and read those threads. He is much more experienced at this than I am and you should find the answer to your problems there. That’s how I get my issues sorted out.
On Mon December 14 2009 07:56 pm, techman9 wrote:
>
> ok. i read through the whole post (i admit i didn’t understand much of
> it, i’m a total linux newbie), and it seems like mostly firewall issues.
> I disabled my Suse firewall because i didn’t want to deal with it. my
> windows to windows connection works fine so it’s not a windows firewall
> issue. I think i need to change some security settings, i just don’t
> know what. :shame:
>
>
techman9;
Please post the contents of /etc/samba/smb.conf. You can use substitute
values for any sensitive information such as public domain names and IPs.
This will be of great help in diagnosing your problem.
I would suggest you read these two HowTos by swerdna. They have been well
tested with recent versions of OpenSuSE.
http://opensuse.swerdna.org/suselanprimer.html
and
http://opensuse.swerdna.org/susesambaserver.html
- Be sure you have added Samba users with:
su
smbpasswd -a <username>
must be the name of a valid linux user but you can use a different
password for Samba than the log on password.
- Make sure that both nmbd and smbd are running. To check enter:
ps -A |grep [s,n]mb
There should be at least one of each.
-
While your testing drop the OpenSuSE Firewall. Once Samba is working you
can work on setting up the Firewall. There is no reason bumping your head
against the wall with two problems. -
Keep in mind that Samba must obey Linux permissions. See the second HowTo
above for some examples of shares.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
# Samba config file created using SWAT
# from UNKNOWN (�,7.0.,qܿ)
# Date: 2009/12/13 18:51:35
[global]
netbios name = SHUTTLEX
map to guest = Bad User
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
os level = 2
local master = No
domain master = No
usershare allow guests = Yes
hosts allow = 192.168.0.0/255.255.255.0
cups options = raw
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes
browseable = Yes
usershare max shares = 100
wins support = No
passdb backend = smbpasswd
workgroup = WORKGROUP
ldap suffix =
[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
guest ok = 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
[files]
comment = Files
path = /home/Admin/Shared/
read only = No
inherit acls = Yes
guest ok = Yes
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes
browseable = No
I now cannot connect to my workgroup at all from the SUSE machine, but it still shows up in My Network Places on windows.
as for that tutorial, i didn’t understand much of it, and didn’t know what to change so it wasn’t much help.
Hope you can help
Techman9
On Tue December 15 2009 07:26 pm, techman9 wrote:
>
> Code:
> --------------------
> # Samba config file created using SWAT
> # from UNKNOWN (�,7.0.,qܿ)
> # Date: 2009/12/13 18:51:35
>
> [global]
> netbios name = SHUTTLEX
> map to guest = Bad User
> 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
The above 4 parameters are only needed if you are setting up a PDC. I would
leave them out.
> os level = 2
> local master = No
> domain master = No
> usershare allow guests = Yes
> hosts allow = 192.168.0.0/255.255.255.0
> cups options = raw
>
> comment = Home Directories
> valid users = %S, %D%w%S
> read only = No
> inherit acls = Yes
> browseable = Yes
> usershare max shares = 100
> wins support = No
> passdb backend = smbpasswd
> workgroup = WORKGROUP
> ldap suffix =
>
> [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
> guest ok = 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
>
> [files]
> comment = Files
> path = /home/Admin/Shared/
> read only = No
> inherit acls = Yes
> guest ok = Yes
>
> comment = Home Directories
> valid users = %S, %D%w%S
> read only = No
> inherit acls = Yes
> browseable = No
>
> --------------------
>
>
>
> I now cannot connect to my workgroup at all from the SUSE machine, but
> it still shows up in My Network Places on windows.
>
> as for that tutorial, i didn’t understand much of it, and didn’t know
> what to change so it wasn’t much help.
>
> Hope you can help
>
> Techman9
>
>
Techman9;
You have mixed up share definitions with the global definitions. Lets see if
we can get this straighten out. I have also added some comments to your
smb.conf. I suspect the main reason you cannot connect to your work group is
the lack of the “name resolve parameter”, but just adding that will
definitely muck up the proper functioning of Samba.
First make a backup copy of your current /etc/samba/smb.conf. Disable
firewalls on both Windows and SuSe while you test. Once Samba works they can
be restarted. But you may need to do some configuration
Replace your existing /etc/samba/smb.conf with:
[global]
netbios name = SHUTTLEX
workgroup = WORKGROUP
# Use "WORKGROUP" for the name of your workgroup only if that is the
# same as what is used in Windows, otherwise use the same workgroup name as
# that used by windows
passdb backend = smbpasswd
map to guest = Bad User
name resolve order = bcast host lmhosts
os level = 35
preferred master = yes
domain master = yes
printcap name = cups
cups options = raw
usershare allow guests = Yes
usershare max shares = 100
[homes]
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes
browseable = No
# [users]
# comment = All users
# path = /home
# read only = no
# inherit acls = yes
# guest ok = 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
guest ok = yes
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin, root
force group = ntadmin
create mask = 0664
directory mask = 0775
You now need to restart smbd. At this point I think the easiest way will be
to just reboot the SuSE machine. This should also make sure your network
reconfigures. It may also helps to reboot the Windows machine. Wait a bit
for the network to settle down.
If things are still awry, make sure both smbd and nmbd are running, the
firewall is down and you’ve created samba users as in my previous post.
With any luck, you should be able to share. If you really need to limit the
interface you can just add that parameter. Never add more than one parameter
at a time. If something breaks you’ll know what did it. If you think you
need to, there should be no harm in uncommenting the shares [users] and
[groups].
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
On Tue December 15 2009 09:26 pm, PV wrote:
> On Tue December 15 2009 07:26 pm, techman9 wrote:
>
>>
<snip>
>
> Replace your existing /etc/samba/smb.conf with:
>
> [global]
> netbios name = SHUTTLEX
> workgroup = WORKGROUP
> # Use "WORKGROUP" for the name of your workgroup only if that is the
> # same as what is used in Windows, otherwise use the same workgroup name as
> # that used by windows
> passdb backend = smbpasswd
> map to guest = Bad User
> name resolve order = bcast host lmhosts
> os level = 35
> preferred master = yes
> domain master = yes
> printcap name = cups
> cups options = raw
> usershare allow guests = Yes
> usershare max shares = 100
>
> [homes]
> comment = Home Directories
> valid users = %S, %D%w%S
> read only = No
> inherit acls = Yes
> browseable = No
>
> # [users]
> # comment = All users
> # path = /home
> # read only = no
> # inherit acls = yes
> # guest ok = 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
> guest ok = yes
>
> [print$]
> comment = Printer Drivers
> path = /var/lib/samba/drivers
> write list = @ntadmin, root
> force group = ntadmin
> create mask = 0664
> directory mask = 0775
>
>
> You now need to restart smbd. At this point I think the easiest way will be
> to just reboot the SuSE machine. This should also make sure your network
> reconfigures. It may also helps to reboot the Windows machine. Wait a bit
> for the network to settle down.
>
> If things are still awry, make sure both smbd and nmbd are running, the
> firewall is down and you’ve created samba users as in my previous post.
>
> With any luck, you should be able to share. If you really need to limit the
> interface you can just add that parameter. Never add more than one
parameter
> at a time. If something breaks you’ll know what did it. If you think you
> need to, there should be no harm in uncommenting the shares [users] and
> [groups].
>
>
Techman9;
I just viewed my post on the web site, there seems to be some spurious
characters preceding certain parameters. The # is a comment leave those in,
or delete all that that follows the #. The *s (or whatever it is) are
spurious.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
I replaced the SAMBA.conf file with the one you gave me. It showed up in “My network places” and even allowed me to connect. However, i had no user then. I added a user to the SUSE machine and now it’s giving the same error as earlier. I may have accidentaly touched something when i was looking throught the SMBPASSWORDS.conf and SMBUSERS.conf because i didn’t know how to add the user. I am so close!!! Thanks so much.
On Wed December 16 2009 12:46 am, techman9 wrote:
>
> I replaced the SAMBA.conf file with the one you gave me. It showed up in
> “My network places” and even allowed me to connect. However, i had no
> user then. I added a user to the SUSE machine and now it’s giving the
> same error as earlier. I may have accidentaly touched something when i
> was looking throught the SMBPASSWORDS.conf and SMBUSERS.conf because i
> didn’t know how to add the user. I am so close!!! Thanks so much.
>
Techman9;
I’m not quite sure what you mean by:
However, i had no user then.
I assume you want to access your OpenSuSE’s user’s home directory? Is that
correct?
Can you elaborate on what exactly you did here:
I added a user to the SUSE machine
Can you post the results of:
su
pdbedit -L
For the names it displays you can substitute a value.
It will be a while before I can reply again, it’s late here.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green