• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How does samba work w/windows machines...

P

Paulson

Elite Member
I for the life of me cannot get samba to work with my windows machines... I have the server running, I have it set on my workgroup and have set some other settings up for it but cannot get it to show up in network neighborhood... what can I do?

this is mandrake linux running samba...
 
I assume by "server" you mean both smbd and nmbd? Do the logs tell you anything interesting? You can boost the log level in smb.conf to get more detailed info. The nmbd logs should show something if you reboot the Windows machine and reopen Network Neighborhood.
 
well I dont' know what has to be set up really.. I'm kind of stupid when it comes to this stuff...

there's so many different options that...
 
Is it setup to require users to login with a l/p or is it open to everyone? If it's password-required, make sure the encrypt passwords option is ON. It took me two weeks to figure that out with my network.
 
damnit now I f'd up everything in my network and I can't see any computers via the work group... oddly enough if I search through the workgroup I can find simple ones, but not my server

ugh!
 
post your smb.conf

Do you have username authentication on the Windows computers? Did you run `smbpasswd` for each user that will be accessing shares?
 
Here's the config:

# Samba config file created using SWAT
# from localhost.localdomain (127.0.0.1)
# Date: 2003/01/04 00:08:09

# Global parameters
[global]
workgroup = SERVER
netbios name = SAMBA
server string = SAMBA
interfaces = eth0
security = DOMAIN
encrypt passwords = Yes
root directory = /home
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = lpstat
dns proxy = No
wins server = 192.168.1.20
username = Blake
guest account =
admin users = root
hosts allow = 192.168.1.20/255.255.255.0
case sensitive = Yes
dos filemode = Yes
dos filetimes = Yes
dos filetime resolution = Yes

[homes]
comment = Home Directories
path = /home
valid users = Blake
read list = Blake
write list = Blake
force user = Blake
read only = No

[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
guest ok = Yes
printable = Yes
print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.
browseable = No

[print$]
path = /var/lib/samba/printers
write list = @adm root

[pdf-generator]
comment = PDF Generator (only valid users)
path = /var/tmp
printable = Yes
print command = /usr/share/samba/scripts/print-pdf %s ~%u \\\\\\\\%L\\\\%u %m %I &
 
before I start digging deeper... shouldn't your

hosts allow = 192.168.1.20/255.255.255.0

like

hosts allow = 192.168.1.

and security = DOMAIN? Are you running a Primary Domain Controller on your network?

Here's my conf for reference

Sorry Paulson, but I have to go to bed... I'll check this thread in the morrow to see if you got it working.
 
smb.conf allow specification of networks either by dropping the octet or specifying the netmask, so that doesn't matter. But, like Mucman said, "security = domain" is only if you're running an NT domain. Also, are you sure you want the workgroup name to be "SERVER"?
 
Originally posted by: cleverhandle
smb.conf allow specification of networks either by dropping the octet or specifying the netmask, so that doesn't matter. But, like Mucman said, "security = domain" is only if you're running an NT domain. Also, are you sure you want the workgroup name to be "SERVER"?
Click to expand...

Yes, I know you can specify the netmask, so shouldn't it be 192.168.1.0/255.255.255.0 in Paulson's case?

I would start off with a small smb.conf like mine (try making a public viewable folder first) and work your way up from there.

 
It used to be paulsonator, until all the sudden none of the computers would show up under the workgroup anymore.. I think I'm going to switch it back...
 
The workgroup must be set to whatever workgroup you have chosen for your network. All of your Windows boxes should have the
same workgroup value. Also remove your WINS server setting... unless you are running a WINS server at IP 192.168.1.20.

Also add :

local master = yes
domain master = yes

Then your samba box will be the master browser and you shouldn't have any problems browsing the network in Windows.
 
Originally posted by: MucmanYes, I know you can specify the netmask, so shouldn't it be 192.168.1.0/255.255.255.0 in Paulson's case?
Click to expand...

192.168.1.0/255.255.255.0 = 192.168.1.20/255.255.255.0 = 192.168.1.255/255.255.255.0 = 192.168.1.

However you state it, you're matching on the first three octets - any host in the 192.168.1.x network can connect.

 
Are you trying to have the Samba server be a WINS server for the group? Then you should have a "wins support = yes" line. As Mucman said, the "wins server" directive is telling Samba to use another machine in the group as the WINS server, which doesn't seem like what you want.
 
Originally posted by: cleverhandle
Originally posted by: MucmanYes, I know you can specify the netmask, so shouldn't it be 192.168.1.0/255.255.255.0 in Paulson's case?
Click to expand...

192.168.1.0/255.255.255.0 = 192.168.1.20/255.255.255.0 = 192.168.1.255/255.255.255.0 = 192.168.1.

However you state it, you're matching on the first three octets - any host in the 192.168.1.x network can connect.
Click to expand...

Blah, thanks for knocking some common sense back into my mind 🙂

Duh, anything anded with 0 is 0 😛... simple logic sometimes can be so elusive...

 
Remove: root directory = /home

root directory (G)
The server will chroot() (i.e. Change its root directory) to this directory on startup.
This is not strictly necessary for secure operation.
Click to expand...

You're chrooting samba to /home, which is most likely breaking any other paths you have in your configuration.

Remove: wins server = 192.168.1.20

You either need 'wins server = some.other.ip' or 'wins support = yes', but they're mutually exclusive because you can't tell the box it's a wins client and server at the same time. It'll make browsing much more reliable if you setup the samba box as a WINS server though, just add it''s IP to the WINS server list on all the clients or update your DHCP server to hand out the right WINS server IP.

Remove: username = Blake

The username line is needed only when the PC is unable to supply its own username. This is
the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX
usernames. In both these cases you may also be better using the \\server\share%user syntax
instead.
Click to expand...

Unless you have a really old SMB client, that line won't help anything.

Remove: case sensitive = Yes

Windows isn't case sensitive, this will only confuse it.

in [Homes] Section Remove: path = /home

Homes is a magical share, that automatically points to whatever user's home directory that's logged in.

Please, read the help pages on SWAT's web page or the smb.conf man page. It describes everything in great detail.
 
Blah, good catch on the path definitions! I completely missed those.

Paulson, have a look at my [homes] definition. Pretty darn simple, but it works flawlessly for the 3 Windows clients I have on the network.
 
I always keep my samba config simple. If your just running it on your home network then there is no reason for most of that.
If that dosent work get WEBMIN its has a great GUI and a step by step Howto.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top