SAMBA Problem

[qwartz]

So gleich noch ein Thread ...
Habe nach dem yum update Probleme mit samba

beim aufruf von service smb start >
SMB-Dienste starten: /etc/init.d/functions: line 83: 19978 Abgebrochen $nice $*
[FEHLGESCHLAGEN]


ind der smbd.log anschliessend folgender eintrag ...

[2006/01/05 18:37:17, 0] smbd/server.c:main(798)
smbd version 3.0.14a-2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2006/01/05 18:37:17, 0] passdb/secrets.c:secrets_init(64)
Failed to open /etc/samba/secrets.tdb
[2006/01/05 18:37:17, 0] passdb/secrets.c:secrets_init(64)
Failed to open /etc/samba/secrets.tdb
[2006/01/05 18:37:17, 0] passdb/secrets.c:secrets_init(64)
Failed to open /etc/samba/secrets.tdb
[2006/01/05 18:37:17, 0] passdb/machine_sid.c:pdb_generate_sam_sid(176)
pdb_generate_sam_sid: Failed to store generated machine SID.
[2006/01/05 18:37:17, 0] lib/util.c:smb_panic2(1517)
PANIC: Could not generate a machine SID

[2006/01/05 18:37:17, 0] lib/util.c:smb_panic2(1525)
BACKTRACE: 7 stack frames:
#0 smbd(smb_panic2+0x8a) [0xd0607c]
#1 smbd(smb_panic+0x19) [0xd062c2]
#2 smbd(get_global_sam_sid+0x2bc) [0xcbe84c]
#3 smbd(init_guest_info+0x65) [0xd4c6be]
#4 smbd(main+0x2a7) [0xd87fb3]
#5 /lib/libc.so.6(__libc_start_main+0xdf) [0x2f0d5f]
#6 smbd [0xb864f1]
hab das Paket schon deinstalliert und neu draufgespielt ... aber der Fehler blieb mir erhalten :mad:

Dank & Gruss

[qwartz]

Tja nachdem ich einfach mal die secrets.tb umbenannt habe und den Dienst gestartet habe het sambi sich ne neue secrets.tb erstellt und der dienst lies sich 1 a starten .. :eek: :D

[qwartz]

Na toll ... :(
nun hab ich ein neues Problem:

Ich kann mich nicht von meinem Windoof rechner aus an Samba anmelden...
Folgendes hab ich gemacht nachdem es nicht mehr ging :

Ich habe die passwd und user datei aus /etc/samba/ gelöscht ...

die user neu angelegt und im terminal passwd vergeben ...

nun kann ich mich aber immer noch nicht anmelden ?
Ich hab ja den verdacht dass es an irgendeinem passwort verschlüsselungs dingbums liegt ?

Kann mir da evtl einer nen Tip geben ?

[urias]

kannst Du bitte mal deine smb.conf posten?

[qwartz]

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = schlachter

# server string is the equivalent of the NT Description field
server string = dellwin

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
hosts allow = 192.168.1. 192.168.0. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
; printing = cups

# This option tells cups that the data has already been rasterized
cups options = raw

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# all log information in one file
# log file = /var/log/samba/log.smbd

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Security mode. Most people will want user level security. See
# security_level.txt for details.
; security = user
# Use password server option only with security = server
; password server = <NT-Server-Name>

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
; encrypt passwords = yes
; smb passwd file = /etc/samba/smbpasswd

# The following are needed to allow password changing from Windows to
# update the Linux system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*

# Unix users can map to different SMB User names
; username map = /etc/samba/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /etc/samba/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
interfaces = 192.168.0.10/24 192.168.1.10/24

# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no

# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no

#============================ Share Definitions ==============================
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
winbind use default domain = no
username map = /etc/samba/smbusers
; security = user
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
; security = user
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
[homes]
comment = Home Directories
browseable = no
writeable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /home/netlogon
; guest ok = yes
; writable = no
; share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /home/profiles
; browseable = no
; guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writeable = no
printable = yes

# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; read only = yes
; write list = @staff

# 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 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
; writable = 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

[tree]
comment = Baum auf FEDORA
valid users = qwartz
path = /
printable = no
; writeable = no // das ; verwirrt mich ein wenig ?
browseable = no

[HTTPD]
path = /var/www
valid users = qwartz, root
writeable = yes
printable = no
create mask = 0777
browseable = yes

[DATEN]
path = /var/smb
valid users = qwartz, root
writeable = yes
printable = no
create mask = 0777
browseable = yes

[amule]
path = /var/amule
writeable = yes
browseable = yes
valid users = qwartz, root
create mask = 0777


Hab immernoch keine Lösung gefunden :mad: wäre also für jede hilfe dankbar

[qwartz]

Also soweit ich das nun nachvollziehen kann könnte es am lokkit liegen...
Ich weis nicht warum aber wenn ich den Rechner neu starte heist mein eth0 plötzlich "dev14859" daraus ergibt sich folgende Frage...
Wie und wo kann ich das ändern dass dieses Device eth0 heist ?
In dem tollen Grafischen Tool hab ich das schon ... nja bestimmt 50 mal gemacht ...
Nach der Neuinstallation hies das Device auch eth0 nach dem ersten Reboot dann .. "dev14859" und eth0 wurde als konfiguriert aber nicht aktiv angezeigt ..

Da lokkit nur anbietet eth0 und eth1 als sichere geräte zuzulassen und kein "dev14859" wird es deswegen nicht gehen per samba zu verbinden ..? oder ?

mfg

[urias]

; security = user
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
; security = user
; encrypt passwords = yes
; guest ok = no
; guest account = nobody

versuch doch mal den Gastzugriff zu aktivieren?
Bzw. die Verschlüsselung an, daran lag es bei mir einmal, als ich mich nach einen update nicht mehr anmelden konnte...

hast Du mal versucht eth0 einfach dann von hand zu aktivieren?
Wie sieht es dann aus?



Ich kann mich nicht von meinem Windoof rechner aus an Samba anmelden...
Folgendes hab ich gemacht nachdem es nicht mehr ging :

Zugriff von anderen Rechner != (ungleich) localhost geht aber, oder?

PS: ähm lokkit???

[qwartz]

Ja also der Zugriff über smb per localhost geht auch nicht :(

lokkit ist das RH Firewall konfigurations /tool /hilfe ...

[Newbie2001]

blöde frage: du hast die benutzer schon auch über smbpasswd -a zu deinem neuen passwd-file hinzugefügt und über smbpasswd -e aktiviert oder ?
Das war deinen bisherigen Ausführungen nämlich nicht zu entnehmen. Du sprichst nur davon, dass du die Benutzer neu angelegt hast (ich nehme an die unix-nutzer) und über passwd (also auch auf os-ebene) die pwds vergeben hast nicht jedoch für samba.

[qwartz]

auszug aus smbpasswd

qwartz:500:77F6F9B08F05C276AAD3B435B51404EE:63BFDA 63304FD49393D575DF4C131A3F:[U ]:LCT-43BD6C2E:
root:0:1D7915C5AB2346E7AAD3B435B51404EE:6E0738B914 214F91399BAEF44068C152:[U ]:LCT-43BD6586:

smbuser

qwartz = qwartz
root = root

sollte passen denke ich ...?

[urias]

Ja also der Zugriff über smb per localhost geht auch nicht :(

lokkit ist das RH Firewall konfigurations /tool /hilfe ...

was genau gibt er denn aus, wenn Du einen Zugriff über localhost versucht?

Was sagt "smbclient -L localhost" ?

Was sagt "iptables --list" ?

[qwartz]

[root@dellwin ~]# smbclient -L localhost
Password:
session setup failed: NT_STATUS_LOGON_FAILURE

[qwartz]

LOLOOOOOL

das kanns ja nicht sein ..... die Freigabe auf ein Verzeichniss in var .... ist nicht möglich ?

Andere Verzeichnisse kann ich mittlerweile darauf zugreifen ... ich hab n Verzeichniss /mnt/share erstellt und freigegeben ... und da kann ich normal mit user und pwd drauf zugreifen .....

BAAAAHHH !

Hat einer nen plan was da los ist ? immerhin liegt das standart web / in var ... :(

[BedriddenTech]

Stimmen vielleicht die Unix-Dateirechte schlichtweg nicht? Von denen ist Samba schließlich nicht unabhängig...

[qwartz]

Hmm du meinst chmod ... und sein kind ?

ich hab schon auf /var/www/ chmod 777 -R gemacht ... hats auch nicht gebracht :(

Am filesystem kanns ja nicht liegen oder ? ext3 ?

[urias]

Am filesystem kanns ja nicht liegen oder ? ext3 ?
wüßte nicht warum dem so sein sollte...dennoch:
hab gerade was unter /var bei gentoo erfolgreich freigegeben, ist bei mir auch ext3...



Hat einer nen plan was da los ist ? immerhin liegt das standart web / in var ...

naja, dann ändere es doch;)

[qwartz]

Lalala ... Ich fange an meinen Umstig von RH auf Fedora zu bereuen :rolleyes:

Komischerweise hab ich im Büro auch FC aber Core 1 und hier hab ich Core 4 ....

nja nochmal zum thema ...

ich hab nu folgende Freigaben


[SHARE]
path = /mnt/Data
comment = Daten auf Server
valid users = qwartz
writeable = yes
printable = no
browseable = yes
; create mask = 0777

[HTTP]
path = /var/www
comment = Webserver
valid users = qwartz
writeable = yes
printable = no
browseable = yes
; create mask = 0777

[TREE]
comment = Baum auf Fedora
valid users = qwartz
path = /
writeable = yes
printable = no
browseable = yes
[SHARE2]
path = /mnt/share
comment = Daten2 auf Server
valid users = qwartz
writeable = yes
printable = no
browseable = yes
; create mask = 0777


lustigerweise kann ich auf [TREE] also / root verzeichniss zugreifen ...
aber /var/www oder /mnt/share geht nicht ... da bekomm ich den Fehler gemeldet "kann nicht zugegriffen werden der Netzwerkname wurde nicht gefunden. Die selbe / ähnliche meldung krieg ich auch wenn ich versuche von localhost (also Linux auf Linux) zuzugreifen :mad:

bevor die Frage kommt :p Ja die Verzeichnisse gibt es und ja ich habe bereits chmod 777 -R auf die verzeichnisse gelegt :p

Ich check das einfach nimme :confused: :confused: :(