Re: Sharing with workgroup

Robert wrote: 

The below smb.conf should work for you. Do that and,
# cd /etc/samba
# testparm (no error!)
# service smb restart

Firewall, open ports;
137:UDP
138:UDP
139:TCP
445:TCP

Your clients should be able to get to [tmp]. If not, get this working first.

useradd user/password and smbpasswd the same as the client and they can get to [home]
I do some special stuff for [data] that allows everyone to share easily. When you get the basic stuff working, let me know about sharing data as I did.

You can set security = share, public = yes, for anyone to get in.

Once you've done it, you can setup samba and cups shared printing in 5-min from the command line and it works everytime. Really, it's very simple. Windows NT, XP, and all Linux works fine.

I fiddled much with nmblookup, so I don't use it. Samba just works when testparm is ok.

I will say that if you use *NEW* stuff with kde-redhat, it "may" break thing like doing smb from konqueror. I pulled down kde 3.5 for a test box and the konqueror smb:// is not working. I've seen this before where *all* is not in sync. So... I keep my production stuff box stock standard, with only updates.


[global]
workgroup = workgroup
server string = Samba Server
#server string = %h ; this will show your computer's name, and what I usually do.
hosts allow = 192.168.1. 192.168.2. 127.
printcap name = /etc/printcap
load printers = yes
printing = cups
cups options = raw
log file = /var/log/samba/%m.log
max log size = 50
security = user
;security = share ; for no user/passwords
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
local master = yes
os level = 33
preferred master = yes
wins support = yes
dns proxy = no
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
winbind use default domain = no
[homes]
comment = Home Directories
browseable = no
writable = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
[data]
comment = data space
path = /data
read only = no
force group = data
;create mode = 0775
create mask = 0660
directory mask = 0775
;user access w/o password
public = yes
[tmp]
comment = Temporary file space
path = /tmp
read only = no
public = yes




I have replaced my smb.conf with the above, replacing the workgroup name with mine here. I also created a directory with the name 'data'.

The Linux machine now sees the data and tmp directories instead of those that were showing with my smb.conf file. There is a slight change in the way the Windows machines fail to connect..... on two machines I get a login box which does not accept the username and null password. Two other Windows machines just give a 'Not available' message. Either way, the Windows clients can't access the tmp directory.

Looking at the dialogue in Ethereal, I see that the Linux machine is responding with Login Failure.

Setting the listed ports in the firewall or having the firewall disabled (as it was before) seem to make no difference. Setting the Windows firewall off makes no difference.

testparm reports no error, and I've restarted smb regularly. Setting Security = share also makes no difference.

I notice in the above script local master is set to yes, where I had set it to no because I don't want the Linux box to take over the Windows system, just join in! That was another thing that wasn't working correctly before if the log messages were to be believed.

I'm still sure there is something really simple and basic that I haven't grasped.

Back to more reading.  Many thanks for the help.
.

Relevant Pages

  • Re: "Do not have access to logon to this session"
    ... different machines and ended up with the same results. ... EventLog on these clients? ... Windows XP, Windows 2000, and Windows NT ... home to Remote Desktop on their Windows XP Pro SP2 machines here ...
    (microsoft.public.windows.terminal_services)
  • RE: Windows XP Fax Printing
    ... I understand that three of five Windows XP clients cannot send fax through ... Make sure the Fax service is started in your Windows XP computer. ... Microsoft CSS Online Newsgroup Support ... On 1 of the machines, I uninstalled and re-installed the Fax Services ...
    (microsoft.public.windows.server.sbs)
  • Re: "Do not have access to logon to this session"
    ... EventLog on these clients? ... Windows XP, Windows 2000, and Windows NT ... something over 100 client machines as members. ... home to Remote Desktop on their Windows XP Pro SP2 machines here ...
    (microsoft.public.windows.terminal_services)
  • Re: Microfocus COBOL 3.2.43 (16bit)
    ... Given that they probably have Windows PCs everywhere they need them, ... sufficient new central machines with VMs may be just additional cost. ... I used Mac's back then for clients in the publishing industry who ... as the speed of the connection and utilization and b) is not ...
    (comp.lang.cobol)
  • Re: apache and websh
    ... I was finally able to run the Websh test suite on Server 2003 and I got ... tmp = Tcl_NewStringObj; ... My application runs fine on Windows 2000, ... set error "Error processing main startup script \"[file nativename ...
    (comp.lang.tcl)