Re: Samba won't dance (more info)




On Tue, 2008-04-15 at 11:09 -0400, Claude Jones wrote:
On Tue April 15 2008, Craig White wrote:
you don't actually expect people to parse that do you?


I stated why I did it. I'm glad to do it your way. Here's the current:

workgroup = MDKGROUP
server string = Samba Server %v
printcap name = cups
load printers = yes
printcap cache time = 60
printing = cups
log file = /var/log/samba/%m.log
max log size = 50
map to guest = bad user
security = user
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
[homes]
comment = Home Directories
browseable = no
writable = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
guest ok = yes
writable = no
printable = yes
create mode = 0700
use client driver = yes
[print$]
path = /var/lib/samba/printers
browseable = yes
write list = @adm root
guest ok = yes
inherit permissions = yes
[pdf-gen]
path = /var/tmp
guest ok = No
printable = Yes
comment = PDF Generator (only valid users)
printing = bsd
print command
= /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" &
lpq command = /bin/true

*******************************
and the original Fedora

grep -v '#' /etc/samba/smb.conf.original | grep -v ';'
[global]
log file = /var/log/samba/%m.log
ldap ssl = No
restrict anonymous = no
domain master = no
wins support = true
dns proxy = no
cups options = raw
max protocol = NT
default service = global
acl compatibility =
server signing = Auto
security = share
preferred master = no
max log size = 50
workgroup = workgroup
[homes]
comment = Home Directories
browseable = no
read only = no
[printers]
comment = All Printers
path = /usr/spool/samba
printable = yes
printer name = HPLaserJet
[cj]
path = /home/cj
guest ok = yes


testparm -s > /tmp/smb.conf.txt

and upload that

or..

grep -v '#' /etc/samba/smb.conf | grep -v ';' > /tmp/smb.conf.txt

But I'm telling you that if you can't reliably ping and nmblookup (which
is somewhat similar to a ping), you're wasting your time here.

It would not surprise me that the whole problem is something I've completely
missed. In my now currently, seemingly, working setup, I just discovered that
even though the smbk4 utility can identify all the machines, their ip
addresses, and their available shares (still un-mountable), on the lan, I
still can't ping one of those machines!
----
nothing monumental sticks out but I would probably drop the SO_RECV and
SO_SND socket options unless you have specific knowledge of them being
of a benefit...

http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/speed.html#id2687166

Craig

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



Relevant Pages

  • Re: Networking Problems - smb.conf suggestions
    ... > server string = Linux here! ... # Specify the workgroup and netbios name of the server ... # If you have any printers connected to your Linux box you ... # Browser master settings. ...
    (alt.os.linux.suse)
  • Re: Samba wont dance (more info)
    ... workgroup = MDKGROUP ... load printers = yes ... map to guest = bad user ... comment = Home Directories ...
    (Fedora)
  • Persistent Print Jobs
    ... print jobs are printed properly and then the status is ... The printers on the Domain ... the exact same way as on the old Workgroup "server". ... the Workgroup server have both been tried with no success. ...
    (microsoft.public.win2000.general)
  • Persistent Print Jobs
    ... print jobs are printed properly and then the status is ... The printers on the Domain ... the exact same way as on the old Workgroup "server". ... the Workgroup server have both been tried with no success. ...
    (microsoft.public.win2000.printing)
  • Persistent Print Jobs
    ... print jobs are printed properly and then the status is ... The printers on the Domain ... the exact same way as on the old Workgroup "server". ... the Workgroup server have both been tried with no success. ...
    (microsoft.public.windows.server.migration)