Help with (hopefully) simple configuration problem
Owen DeLong
owen at DeLong.SJ.CA.US
Tue Mar 9 05:19:05 GMT 1999
I have a (mostly) windows environment into which I am attempting
to integrate a SAMBA based printer server (Solaris 2.5.1 SPARC).
I'm running SAMBA 1.9.18p10. I need the print server to do
two things:
1. Perform as local network browser/WINS server
for the local subnet it is on (10.255.8.128/27)
2. Register itself and clients on it's subnet
with the browsers/WINS servers/whatever it
needs to to be browseable by the rest of the
clients. The primary WINS server is 10.255.1.10/24.
I've tried everything I can think of. My smb.conf file is as follows:
; Configuration file for smbd.
; ============================================================================
; For the format of this file and comprehensive descriptions of all the
; configuration option, please refer to the man page for smb.conf(5).
;
; The following configuration should suit most systems for basic usage and
; initial testing. It gives all clients access to their home directories and
; allows access to all printers specified in /etc/printcap.
;
; Things you need to check:
; --------------------------
;
; 1: Check the path to your printcap file. If you are using a system that does
; not use printcap (eg., Solaris), create a file containing lines of the
; form
;
; printername|printername|printername|
;
; where each "printername" is the name of a printer you want to provide
; access to. Then alter the "printcap =" entry to point to the new file.
;
; If using Solaris, the following command will generate a suitable printcap
; file:
;
; lpc status | grep ":" | sed s/:/\|/ > myprintcap
;
; 2: Make sure the "print command" entry is correct for your system. This
; command should submit a file (represented by %s) to a printer
; (represented by %p) for printing and should REMOVE the file after
; printing.
;
; One most systems the default will be OK, as long as you get "printing ="
; right.
;
; It is also a good idea to use an absolute path in the print command
; as there is no guarantee the search path will be set correctly.
;
; 3: Make sure the "printing =" option is set correctly for your system.
; Possible values are "sysv", "bsd" or "aix".
;
; 4: Make sure the "lpq command" entry is correct for your system. The default
; may not work for you.
;
; 5: Make sure that the user specified in "guest account" exists. Typically
; this will be a user that cannot log in and has minimal privileges.
; Often the "nobody" account doesn't work (very system dependant).
;
; 6: You should consider the "security =" option. See a full description
; in the main documentation and the smb.conf(5) manual page
;
; 7: Look at the "hosts allow" option, unless you want everyone on the internet
; to be able to access your files.
;
[global]
interfaces = 10.255.8.134/27
bind interfaces only = yes
printing = sysv
printcap name = /etc/printcap
load printers = yes
guest account = nobody
; This next option sets a separate log file for each client. Remove
; it if you want a combined log file.
log file = /opt/ATsamba/log.%m
; You will need a world readable lock directory and "share modes=yes"
; if you want to support the file sharing modes for multiple users
; of the same files
lock directory = /opt/ATsamba/var/locks
share modes = yes
username map = /opt/ATsamba/lib/usermap
auto services = homes printer tmp lawson1-2 dj1600cm srtg4000
workgroup = SOL
wins proxy = yes
dns proxy = yes
lm announce = true
local master = yes
name resolve order = lmhosts host wins bcast
netbios name = ASILOMAR
netbios aliases = ASILOMAR-IN asilomar asilomar-in Asilomar Asilomar-in
remote announce = 10.255.1.255/SOL 209.185.81.255/SOL 209.185.80.255/SOL
remote browse sync = 10.255.1.255 209.185.80.255 209.185.81.255
server string = Samba %v -- Better NetBios wihtout Microsoft
time server = True
[lawson1-2]
comment = Lawson 1-2 LJ5si
browseable = yes
printable = yes
public = yes
create mode = 0777
directory=/opt/ATsamba/var/print
[dj1600cm]
comment = Deskjet 1600 CM
browseable = yes
printable = yes
public = yes
create mode = 0777
directory=/opt/ATsamba/var/print
[srtg4000]
comment = HP LaserJet4000
browseable = yes
printable = yes
public = yes
create mode = 0777
directory=/opt/ATsamba/var/print
[homes]
comment = Home Directories
browseable = no
read only = no
create mode = 0750
; you might also want this one, notice that it is read only so as not to give
; people without an account write access.
;
; [tmp]
; comment = Temporary file space
; path = /tmp
; read only = yes
; public = yes
;
; Other examples.
;
; A private printer, usable only by fred. Spool data will be placed in fred's
; home directory. Note that fred must have write access to the spool directory,
; wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
;
; A private directory, usable only by fred. Note that fred requires write
; access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
;
; A publicly accessible directory, but read only, except for people in
; the staff group
;[public]
; comment = Public Stuff
; path = /usr/somewhere/public
; public = yes
; writable = no
; printable = no
; write list = @staff
;
; a service which has a different directory for each machine that connects
; this allows you to tailor configurations to incoming machines. You could
; also use the %u option to tailor it by user name.
; The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writeable = yes
;
;
; A publicly accessible directory, read/write to all users. Note that all files
; created in the directory by users will be owned by the default user, so
; any user with access can delete any other user's files. Obviously this
; directory must be writable by the default user. Another user could of course
; be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
;
;
; The following two entries demonstrate how to share a directory so that two
; users can place files there that will be owned by the specific users. In this
; setup, the directory should be writable by both users and should have the
; sticky bit set on it to prevent abuse. Obviously this could be extended to
; as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
When I run nmbd in -d 255 mode, I get a consistent stream of messages
as follows:
find_workgroup_on_subnet: workgroup search for SOL on subnet 10.255.8.134: found
find_workgroup_on_subnet: workgroup search for SOL on subnet 10.255.8.134: found
is_myname("ASILOMAR") returns 1
send_lm_host_announcement: type 49a23 for host ASILOMAR on subnet 10.255.8.134 for workgroup SOL, ttl: 60
send_mailslot: Sending to mailslot \MAILSLOT\LANMAN from ASILOMAR<00> IP 10.255.8.134 to SOL<00> IP 10.255.8.159
0 char ..#.....<.ASILOM hex 01 00 23 9a 04 00 04 02 3c 00 41 53 49 4c 4f 4d
10 char AR.Samba 1.9.18p hex 41 52 00 53 61 6d 62 61 20 31 2e 39 2e 31 38 70
20 char 10 -- Better Net hex 31 30 20 2d 2d 20 42 65 74 74 65 72 20 4e 65 74
30 char Bios wihtout Mic hex 42 69 6f 73 20 77 69 68 74 6f 75 74 20 4d 69 63
40 char rosoft. hex 72 6f 73 6f 66 74 00
1999/03/08 21:14:14 sending a packet of len 239 to (10.255.8.159) on port 138
is_myname("ASILOMAR-IN") returns 1
send_lm_host_announcement: type 9a23 for host ASILOMAR-IN on subnet 10.255.8.134 for workgroup SOL, ttl: 60
send_mailslot: Sending to mailslot \MAILSLOT\LANMAN from ASILOMAR-IN<00> IP 10.255.8.134 to SOL<00> IP 10.255.8.159
0 char ..#.....<.ASILOM hex 01 00 23 9a 00 00 04 02 3c 00 41 53 49 4c 4f 4d
10 char AR-IN.Samba 1.9. hex 41 52 2d 49 4e 00 53 61 6d 62 61 20 31 2e 39 2e
20 char 18p10 -- Better hex 31 38 70 31 30 20 2d 2d 20 42 65 74 74 65 72 20
30 char NetBios wihtout hex 4e 65 74 42 69 6f 73 20 77 69 68 74 6f 75 74 20
40 char Microsoft. hex 4d 69 63 72 6f 73 6f 66 74 00
1999/03/08 21:14:14 sending a packet of len 242 to (10.255.8.159) on port 138
announce_myself_to_domain_master_browser: no unicast subnet, ignoring.
dump_workgroups: dump workgroup on subnet 10.255.8.134: netmask=255.255.255.224:
SOL(1) current master browser = ASILOMAR
ASILOMAR 40049a23 (Samba 1.9.18p10 -- Better NetBios wihtout Microsoft)
ASILOMAR-IN 40009a23 (Samba 1.9.18p10 -- Better NetBios wihtout Microsoft)
Even the machine on the local subnet doesn't seem to find the samba server.
The samba server is named asilomar. It has two interfaces, 10.255.8.134
and 216.32.162.38. The SAMBA server should only work with/on the 10.255.8.134
interface.
Any help appreciated. I'm now up against a deadline and really starting to
tear my hair out over this.
Owen
More information about the samba
mailing list