I have a problem of shares that "disappear" or are inaccessible.
This only happens with Win2k and only for some users. My Samba is version
2.2.2 running on Solaris 2.6. Here's the sequence:
1) The user logs into PC (not using PDC).
2) He connects to Samba server via "Run..." and typing \\spike.
3) The user is prompted for "connect as" and "password".
The correct ones
are used.
4) The server window opens and all the shares show, all the printers show, etc.
5) This particular user is in the group that has access to CustMgr-*. He
double clicks on any of these and receives an error:
The network name cannot be found.
6) The user double clicks on any of the other shares, it opens fine.
7) He then goes back and the three CustMgr-* shares have disaapeared.
I have attached the smb.conf, after expansion and removal of printer
definitions. The real smb.conf has entries like:
include = /etc/samba/primary-config/%U
which is what makes the group shares only show for those people that are
in the group. I would otherwise have way too may shares!
I have captured a level 10 log and grepping for CustMgr I see:
-------------------------------------------------------------------------
init_srv_share_info1: CustMgr-Grp 0 /u/custmgr/group -- Group Only
Share
init_srv_share_info1: CustMgr-Pub 0 /u/custmgr/public -- Publicly
Readable Share
init_srv_share_info1: CustMgr-Web 0 /u/custmgr/public_html --
Group's webspace
free_service: Freeing service CustMgr-Grp
free_service: Freeing service CustMgr-Pub
free_service: Freeing service CustMgr-Web
lp_servicenumber: couldn't find CustMgr-Web
checking for home directory CustMgr-Web gave (NULL)
find_service() failed to find service CustMgr-Web
lp_servicenumber: couldn't find CustMgr-Web
checking for home directory CustMgr-Web gave (NULL)
find_service() failed to find service CustMgr-Web
lp_servicenumber: couldn't find CustMgr-Web
checking for home directory CustMgr-Web gave (NULL)
find_service() failed to find service CustMgr-Web
-------------------------------------------------------------------------
The full log file is available upon request, but it is 1.5Mbytes. I have
the same from a WinME system.
Why does it see them, then they disappear? Why does the same user work
fine on WinME and WinNT?
This always happened when I had 2.0.* and tried to use Win2k. It went
away with 2.2.1 and now has come back with 2.2.2, but only for some
users/Win2k systems.
I really need to get this solved as we are upgrading all our customer support
people to Win2k (new application dependencies) and it isn't good to
have customer support crippled.
Help!
--
Gary Algier, WB2FWZ gaa@@ulticom.com +1 856 787 2758
Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054 Fax:+1 856 866 2033
A self-addressed envelope would be addressed "envelope."
-------------- next part --------------
[global]
workgroup = Ulticom
server string = Spike [the Rugrats dog]
# The printer definitions are done separately (see smb.conf.printers)
# so we can have complete control over them.
printcap name = /dev/null
# This next file is the printers definitions as extracted and modified
# from the Win9X msprint.inf file. See PRINTER_DRIVER.txt for more
# information.
printer driver file = /etc/samba/printers.def
# log file = /var/samba/log
log level = 0
local master = yes
# OS Level determines the precedence of this server in master browser
# elections. The default value (33) should be reasonable, but we want
# to be sure to one-up any NT host. Remember, however, that a PDC
# must be also the domain master. Therefore, do not try to put a
# PDC in the same workgroup.
# New info: one needs a value of 65 to make sure a Win2k system does
# not win!
# I have set this higher so it will always win over any Winbloze system.
os level = 99
domain master = yes
preferred master = yes
domain logons = no
update encrypted = yes
encrypt passwords = no
# we may be having problems with oplocks:
oplocks = no
level2 oplocks = no
[homes]
comment = My Home Directory
browseable = no
writable = yes
# make sure users don't make publicly writable files:
directory mask = 0755
create mask = 0755
# This needs external support to make sure the given directory is
# up to date with symlinks into /u
[users]
comment = Links to all the user's home directories
path = /etc/samba/users
# it is too easy for somebody to drag and drop the whole
# thing in the trash, so don't allow writes here
# they can always access their own directory via [homes]
browseable = yes
# Well, it happened. The Nimda Worm clobbered thousands of 777 files
# because of this being writable. Never, ever, make this a writable
# share!
# gaa, Thu Sep 20 20:36:04 EDT 2001
writable = no
# Here we manually create symbolic links to the other servers.
[hosts]
comment = Links to other file servers in the same NIS domain.
path = /etc/samba/hosts
browseable = yes
# Well, it happened. The Nimda Worm clobbered thousands of 777 files
# because of this being writable. Never, ever, make this a writable
# share!
# gaa, Thu Sep 20 20:36:04 EDT 2001
writable = no
# Here we manually create symbolic links to the publicly shared spaces.
# We do this to keep to a minimum the number of public shares
# everyone needs to see.
[public]
comment = Here are files for public consumption
path = /etc/samba/public
browseable = yes
writable = yes
[CustMgr-Grp]
comment = /u/custmgr/group -- Group Only Share
path = /u/custmgr/group
writable = yes
browsable = yes
; only members may write:
write list = @custmgr
; only members force groupness:
force group = +custmgr
; only members may connect:
valid users = +custmgr
; make everything group writable, DON'T let others see:
; (also set group-id bit)
force directory mode = 02770
force create mode = 0770
directory mask = 02770
create mask = 0770
[CustMgr-Pub]
comment = /u/custmgr/public -- Publicly Readable Share
path = /u/custmgr/public
writable = yes
browsable = yes
; only members may write:
write list = @custmgr
; only members force groupness:
force group = +custmgr
; only members may connect:
valid users = +custmgr
; make everything group writable, DO let others see:
; (also set group-id bit)
force directory mode = 02775
force create mode = 0775
directory mask = 02775
create mask = 0775
[CustMgr-Web]
comment = /u/custmgr/public_html -- Group's webspace
path = /u/custmgr/public_html
writable = yes
browsable = yes
; only members may write:
write list = @custmgr
; only members force groupness:
force group = +custmgr
; only members may connect:
valid users = +custmgr
; make all web pages, etc., belong to the special user:
force user = custmgr
; do not make group writable as the apache setuid exec mechinism considers
; this to be a security violation:
; (also set group-id bit)
force directory mode = 02755
force create mode = 0755
directory mask = 02755
create mask = 0755
[OracleImp]
comment = ES Group Oracle Implementation
path = /u/es/OracleImp
writable = yes
browsable = yes
; only group members may write:
write list = @esora
; only members force groupness:
force group = +esora
; anyone may connect
valid users ; make sure all directories are writable by group and readable by
others:
force directory mode = 0775
force create mode = 0775
; make sure all files and directories are not writable by others:
directory mask = 0775
create mask = 0775
