It’s not a firewall problem; disabling the firewall entirely doesn’t help. I have the workgroup set properly, and the location I want to share is enabled. But the entire computer won’t show up, even on my openSUSE machine’s Network section. I can access my Windows computers’ shares from it, but not the other way around. It was working, then I rebooted and I lost it.
On Sat December 19 2009 04:06 pm, MindWanderer wrote:
>
> It’s not a firewall problem; disabling the firewall entirely doesn’t
> help. I have the workgroup set properly, and the location I want to
> share is enabled. But the entire computer won’t show up, even on my
> openSUSE machine’s Network section. I can access my Windows computers’
> shares from it, but not the other way around. It was working, then I
> rebooted and I lost it.
>
>
MindWanderer;
Check if smbd and nmbd are both running. In a terminal window enter:
ps -A |grep [s,n]mb
There should be at least one instance of each smb and nmb.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
result:
1507 ? 00:00:00 nmbd
1509 ? 00:00:00 nmbd
1794 ? 00:00:00 smbd
Please post here the return in a console window to this command:
testparm -s
and look in the windows machine in control panel → system → machine name (or like that IIRC) and report here the name of the workgroup.
Result:
Load smb config files from /etc/samba/smb.conf
Processing section “[profiles]”
Processing section “[printers]”
Processing section “[print$]”
Processing section “[file-server]”
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
workgroup = TRINITY
netbios name = FAMILY-SERVER
map to guest = Bad User
passdb backend = smbpasswd
name resolve order = bcast host lmhosts wins
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
domain master = No
wins support = Yes
idmap uid = 10000-20000
idmap gid = 10000-20000
cups options = raw
[profiles]
comment = Network Profiles Service
path = %H
read only = No
create mask = 0600
directory mask = 0700
store dos attributes = Yes
[printers]
comment = All Printers
path = /var/tmp
create mask = 0600
printable = Yes
browseable = No
browsable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin, root
force group = ntadmin
create mask = 0664
directory mask = 0775
[file-server]
comment = Shared files
path = /windows/C
read only = No
inherit acls = Yes
And the Windows’ workgroup is TRINITY
On Sat December 19 2009 05:46 pm, MindWanderer wrote:
>
> Result:
>
> Load smb config files from /etc/samba/smb.conf
> Processing section “[profiles]”
> Processing section “[printers]”
> Processing section “[print$]”
> Processing section “[file-server]”
> Loaded services file OK.
> Server role: ROLE_STANDALONE
> [global]
> workgroup = TRINITY
> netbios name = FAMILY-SERVER
> map to guest = Bad User
> passdb backend = smbpasswd
> name resolve order = bcast host lmhosts wins
> 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 four parameters are only needed for a Domain Controller
> domain master = No
> wins support = Yes
> idmap uid = 10000-20000
> idmap gid = 10000-20000
> cups options = raw
>
> [profiles]
> comment = Network Profiles Service
> path = %H
> read only = No
> create mask = 0600
> directory mask = 0700
> store dos attributes = Yes
>
> [printers]
> comment = All Printers
> path = /var/tmp
> create mask = 0600
> printable = Yes
> browseable = No
> browsable = No
>
> [print$]
> comment = Printer Drivers
> path = /var/lib/samba/drivers
> write list = @ntadmin, root
> force group = ntadmin
> create mask = 0664
> directory mask = 0775
>
> [file-server]
> comment = Shared files
> path = /windows/C
> read only = No
> inherit acls = Yes
>
>
> And the Windows’ workgroup is TRINITY
>
MindWanderer;
You have configured Samba as a WINS server, which is ok, but:
- Have you set the Windows machines to use a wins server?
- Samba is set to check wins last, everything likely dies before it gets to
wins. Try
“name resolve order = wins bcast host lmhosts”
or maybe (a distant second option)
“name resolve order = bcast wins host lmhosts” - Are all your machines found in
“/var/lib/samba/wins.dat” ?
Generally Samba prefers to be the master browser, you might try adding these
to your /etc/samba/smb.conf.
domain master = yes
preferred master = yes
os level = 65
Also check that your Windows firewalls allow file sharing. While you are
debugging this, try shutting down the firewalls on both Windows and Samba.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
I would have blamed the “wins support” because it’s misaligned with name resolve order, removed wins, left the name resolve as is and set “preferred master” to match the name resolve order, thus no need to tweak the windows machines to look for a wins server, and set it as a workgroup for simplicity.
But – whatever works, works
So if the domain server approach become tricky, drop back to a simple windows SOHO setup.
@venzkep: Tried deleting the logon lines, changing the resolve order, and adding the lines you suggested. No luck. BTW, my wins.dat says:
VERSION 1 0
“TRINITY#1e” 1261516160 0.0.0.0 e4R
“MEDIA-SERVER#20” 1261377267 192.168.2.2 66R
“FAMILY-SERVER#03” 1261516160 192.168.2.2 66R
“FAMILY-SERVER#20” 1261516160 192.168.2.2 66R
“MEDIA-SERVER#00” 1261377267 192.168.2.2 66R
“FAMILY-SERVER#00” 1261516160 192.168.2.2 66R
“TRINITY#00” 1261516160 0.0.0.0 e4R
“MEDIA-SERVER#03” 1261377267 192.168.2.2 66R
None of which are my Windows computers. However, it’s worth noting again that if I go to Network->Trinity on the openSUSE machine, it only shows the Windows computers, and not itself.
@swerdna: I’ll try that, thanks.
On Sat December 19 2009 09:36 pm, swerdna wrote:
>
> I would have blamed the “wins support” because it’s misaligned with name
> resolve order, removed wins, left the name resolve as is and set
> “preferred master” to match the name resolve order, thus no need to
> tweak the windows machines to look for a wins server, and set it as a
> workgroup for simplicity.
>
> But – whatever works, works
>
> So if the domain server approach become tricky, drop back to a ‘simple
> windows SOHO setup’ (http://opensuse.swerdna.org/suselanprimer.html).
>
>
@swerdna
The OPs SMB.conf, is a workgroup, even with my suggestions. The “domain
master” parameter just makes Samba the master browser for the entire
workgroup (vs a local master browser for just a subnet). I agree, that
unless the OP has machines on different subnets, there is not much need for a
WINS server, and that a local master browser is all that’s needed. To create
a domain the key parameter is “domain logons”. For a simple Workgoup network
that does not span more than one subset, the domain master parameter should
either be yes or left at the default value (auto), it should be set to No
only on BDCs.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Poor choice of words on my part. Maybe I should have said like: too many lines there to sort it out easily, suggest take out wins and simplify [global] to like this:
workgroup = TRINITY
netbios name = FAMILY-SERVER
map to guest = Bad User
passdb backend = smbpasswd
name resolve order = bcast host lmhosts wins
printcap name = cups
local master = yes
preferred master = yes
os level = 65
The main advantage of this is that if it doesn’t work, the problem’s not in [global]
PS if /windows/C belongs to root:users as is often the case, you’d have trouble accessing it, but that’s another matter.
I’d recommend mounting the partition (if it’s NTFS and openSUSE 11.1 or 2) with this options string:
uid=billybob,gid=users,umask=0022
and making the share like this:
[file-server]
comment = Shared files
path = /windows/C
force user = billybob
guest ok = yes
read only = No
and if you wanted only authenticated users, take out “guest ok = yes” and add any number of users to smbpasswd, doesn’t have to be just billybob or even billybob.
But that’s not the current problem, just a passing thought.
@swerdna: Thanks, that bare-bones [global] did the trick. And your last post is info I wanted, as well.
Glad it’s cookin
Update: Everything is indeed cooking… but only manually. Everytime I make a connection (which is often; my router is sketchy), I have to do rcnmb restart and rcsmb restart.
Try this: goto Yast → system → system services (runlevels) and switch on /enable smb and nmb → OK etc