-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of email
Sent: Saturday, May 05, 2001 3:33 PM
To: [EMAIL PROTECTED]
Subject: [expert] Samba Issues
Hi guys,
I've asked before, but didn't receive any replies. Since then I've run a
few more tests and refined a few things, so maybe this should be a little
more helpful to any of you who may want to try to help diagnose this
problem.
Basically, I have a machine running mdk8.0 which I want to use as my
fileserver/proxy/firewall/dhcp server/whatever. Right now, it's running
as a firewall and router to my cable modem, it runs a DHCP server to my
internal LAN, but the samba server seems to have some issues...
Here is a copy of my smb.conf file;
[global]
#general workgroup stuff
netbios name = Server
workgroup = DEVELOPMENT
browseable = yes
socket options = TCP_NODELAY
# browser election stuff
os level = 33
local master = yes
preferred master = yes
domain master = yes
# network config stuff
hosts allow = 192.168.0. localhost
interfaces = 192.168.0.1/255.255.255.0
bind interfaces only = yes
[storage]
path = /storage
browsable = yes
comment = storage drive
volume = storage
writeable = yes
guest ok = no
[homes]
comment = Home Directories
read only = No
browseable = No
When I do an smbclient -L Server as root, then enter my password, it shows
up as the master browser, and has /storage and /root shared, jsut as it is
supposed to. I get a different error, ERRinvnetname.
Now, when I try to browse my network from Windows 98, NT4, or 2000, it
says
"Development is not acessible.
The list of servers for this workgroup is not currently available."
---
You have specified DOMAIN logins.
Did you remember to set up your Windows machines to use DOMAIN logons and
told them to use "Server" as the controller?
I'll bet not.
---
I have also recived an error stating that the server is not set up to
share that information.
---
Yeap the Workstations have not logged in yet.
The username and password you enter into Windows at startup are passed to
SAMBA from Windows whenever it attempts to access the domain/workgroup.
In turn the same accounts MUST exist in Samba with a corresponding Linux
account for each user. Think of your Samba server as a completely different
machine which needs a different set of logins!
So you need to "smbadduser" and "smbpasswd" for each new Windows account
that will be accessing the domain.
---
at any time, I can type in \\Server\storage and I am presented with a
dialogue asking me for username and password, then the server grants me
access to the share andother shares on the server.
---
Yeap
---
The workgroups are correctly configured, this was working perfectly fine
when I had a Windows NT4 server system set up to perform all of these
tasks. I have simply removed it, and made some slight modification to the
smb.conf file I used. None of the modifications affected the workgroup
though.
---
Now you are talking about a Workgroup, yet you are using a domain
controller.
Which is it? It can't be both!
---
I've spent the past week, on and off, reading though Using Samba by
O'Reilly and Associates, and unfortunately, it hasn't been able to help me
fix this.
Any help would be greatly appreciated... any RTFMs would be greatly
annoying as that's all I have been doing for the past 2 or three weeks now
---
Well here's a RTFM... O'Reilly's is somewhat poor in helping you to
understand what is going on...
Try CoriolisOpen Press, Samba Black Book by Dominic Baines.
It's great because it covers both the Windows/NT/2K aspects and the Samba
side of things...
Also there is another called something like...
Samba: Integrating Linux and Windows/NT workstations, but I forgot the
author...
Both are excellent.
BTW: If you want to see the Winblows shares from Linux, you'll have to
enable File and Printer sharing for MS Networks and then set "LM Announce"
to "on".
But fix your Workgroup/domain problem first.
-JMS
