Šta je novo?

Samba sludjivanje

  • Začetnik teme Deleted member 9456
  • Datum pokretanja
D

Deleted member 9456

Guest
Da li se Samba ikako moze doterati u normalu? Imam tri umrezene masine, XP, Ubuntu 10.04, Ubuntu 10.10. Setujem sve po PS jednom, 10.04 vidi samo sebe, druge dve masine vide jedna drugu i za njih kao da ne postoji 10.04. Posle nekog vremena naidje neki update pa sad 10.04 vidi sve i svi vide nju. 10.10 je najzvezija instalacija i dok je bio 10.04 na njoj nije bilo boga da vidi ostale u mrezu.
Ovo je totalno zaludjivanje sa Sambom, da li ta samba ikad moze normalno da radi ili malo malo neki update ko zna cega pokvari sve. Sve se odigrava po vec ustaljenoj shemi, jedno vreme sve radi, onda krece shema jedna samba ne vidi ostale u mrezi a i ostali nju, onda druga samba ne vidi ostale u mrezi a i oni nju. Iscitavao sam sve zivo, stavljao i swat, kad se sa njim setuje onda i ono sto je radilo ne radi. Apsurd je sto kad Ubuntu masine koje imaju dual boot prebacim u XP sve radi ko podmazano. Ne mogu da svatim da jednu najprostiju mrezu sa workgrupom i kombinacijom windows i Ubuntu ne mogu da imam i da radi kako treba. Da li neko uoste ima ideju zasto se to dogadja i kako to vec jednom doterati da radi kako treba, nisam jedini koji ima ove probleme, konsultovao sam jos neke ljude, slezu ramenima i kazu digli su ruke od toga. Ptam se kako to radi u nekoj vecoj mrezi, mozda ljudi ne rade update po sistemu ne pipaj dugmice dok radi. :crash:
 
Ako neces da se non stop zezas sa konfiguracionim
fajlovima jednostavno uradi Share iz nautilusa.
Radi provereno i ne prestaje da radi posle update-a.

Ako hoces da se igras sa sambom i naucis to jednom
za svagda onda lepo pregledaj ubuntu community samba
dokumentaciju kao i samba man i kreni polako.

Ja sam imao nesto nedavno dosta problema sa sambom
jer mi je trebao share sa odredjenim dozvolama za user-e
pa sam morao da sednem i naucim to kako treba.
 
Obavezno ugasiti firewall-ove na ubuntu masinama, proveriti da li ne radi netbios ili ne radi i smb protokol (na xp-u probati sa otvaranjem share-a preko \\ime i \\ipadresa u windows exploreru).

ps. da, sambu intenzivno koristim i to kao AD i obicne file servere na mnogo mesta, ne mogu da se setim da je update ikada raz*ebao konfiguraciju; config fajlovi sambe su unazad kompatibilni godinama, gotovo deceniju unazad.
 
Evo ga smb.conf, potpuno idetican u slovo sa onim na drugoj masini. Mogu ja da pristupam ako kucam smb://IP_masine/dir ali je problem da utrefim dir koji je share isto tako mogu i iz XP slicnom sintaksom da pristupim. Problem je sto samba preko nautilusa ne vidi share masinu. Isto tako masine koje se vide izmedju sebe XP <> drugi Ubuntu ne vide tu masinu. Isto tako na Ubuntu masini koja trenutno zeza podignem VMware i virtuelni XP, stavio sam da radi u bridge modu, taj XP npr. kroz total commander normalno vidi racunare u mrezi ali svog domacina ne vidi. Kao sto sam vec napisao ako pokusam kroz SWAT da napravim novi smb.conf posle restarta smbd service i nmbd service (sad su service nisu daemon) onda tek taj Ubuntu ne vidi ni sebe (pricekam malo da bi proces objave ja sam share proradio) To je problem koji me izludjuje, mozda to nije ni do sambe nego do Nautilisa, pcmanfm i svih ostalih slicnih programa koji sluze da vide mrezu, racunare u mrezi i sta je u ponudi za share. Firewall je iskljucen (stavljaju UFW a i dok je bio ukljucen; jako davno; data mu je bila dozvola za sambu), to sam prvo probao, na XP nije ali je definisano pravilo i to radii sa njim nemam problema a pogotovo ako su sve masine podignute u XP. Stalno imam dilemu da li ;ispred komade disebluje tu komadu ili ne.

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###
; netbios name = unknown0

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = mshome

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# 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

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
; encrypt passwords = yes

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
; passdb backend = tdbsam

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# 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 = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
domain master = No
; local master = yes
preferred master = Yes
os level = 35

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
username map = /etc/samba/smbusers
security = user
; guest ok = no
; guest account = nobody

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
; guest ok = no
; read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
; browseable = yes
writeable = yes
valid users = dragica, lega, nobody, tijana
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom

[Downloads]
path = /home/lega/Downloads
; writeable = no
; browseable = yes
valid users = xxxx, lega99, xxxxx
 
Poslednja izmena od urednika:
Sambu mozes konfigurisati na vise nacina. Npr. za pristup nekom shareu mozes podesiti da mora da se unese username/password kombinacija a mozes da podesis i da je free za sve. Ako je kucna mreza i ne zelis da maltretiras ukucane sa siframa onda stavi ovo:

(potrazi u smb.conf gde se nalazi ovaj red)
security = share


i kada sharujes neki folder onda uradi ovako:
[MojShare]
path = /path/do/linux/foldera
available = yes
browsable = yes
public = yes
writable = yes
guest ok = yes
read only = no
create mask = 0777
directory mask = 0777
force user = nobody
force group = nogroup
 
Poslednja izmena od urednika:
Sambu mozes konfigurisati na vise nacina. Npr. za pristup nekom shareu mozes podesiti da mora da se unese username/password kombinacija a mozes da podesis i da je free za sve. Ako je kucna mreza i ne zelis da maltretiras ukucane sa siframa onda stavi ovo:

i kada sharujes neki folder onda uradi ovako:
[MojShare]
path = /path/do/linux/foldera
avaible - yes
browsable = yes
public = yes
writable = yes
guest ok = yes
read only = no
create mask = 0777
directory mask = 0777
force user = nobody
force group = nogroup

Na ovu sintaksu testparm javlja gresku, nesto mu se ne dopada.
Nasao sam jos njih koji imaju isti problem ali niko nije resio, ili je do nautilusa (ok ako gledas kod sebe), ali sta je problem kad jednu Ububtu masinu vidis iz XP a drugu ne a smb.conf isti, ili jedna Ubuntu vidi XP a ne vidi drugu Ubunt i to kad vidi vidi kroz sve zive programe te namene. :)
 
Citam, citam i sve se vise ukopavam... Pokusam po nekim preporucenim savetima koje nadjem, kao uspelo je tako i dobije nista... Sizifov posao, nadjem savet, kao garant radi, promenim u smb.conf, restart servisa, restart masine, ne pomeze. Najvise me iritira to sto radim sa 10.04 LTS verzijom i sto je to radilo i onda update ovaj onaj i odjednom kad zatreba ne radi. :wall::crash:
 
@mad_max0204,

I meni je najlakse da kliknem na file i kazem share, problem je sto ipak mora da se edituje smb.conf i stavi NetBios name racunara i workgrupa. Znaci sa takav minumalnim setovanjem uvek je lutrija da li ce ostali racunari videti to u mrezi. U Xp ne koristim simple file share, ne dajem dozvole za pisanje po share folderima, ako to dozvolim to je izuzetak i to samo na kratko.

@Salac,

Sta koristite koji program da bi videli sve racunare koji su umrezeni i njihove share foldere, mislim na mesovite velike mreze. Kolko vidim Samba je 3.4.7~dfsg-1ubuntu3.2. Isto tako u 10.10 je 3.5.x~dfsg ovo mi ne lici bas na oznake redovnih fajlova. 10.10 je instaliran pre par dana.
 
Poslednja izmena od urednika:
# lenny (stable) (net): a LanManager-like file and printer server for Unix
2:3.2.5-4lenny13 [security]: i386
Cinimi se po ovom podatku da se Canonical- Ubuntu igra sa nama, Debian koristi gore navedenu verziju, Ubuntu 10.04 LTS koristi 3.4.x verziju, Ubuntu 10.10 koristi 3.5.x verziju. Tracim vreme i zivce na nedovoljno testirane verzije.
 
@Salac,

Sta koristite koji program da bi videli sve racunare koji su umrezeni i njihove share foldere, mislim na mesovite velike mreze. Kolko vidim Samba je 3.4.7~dfsg-1ubuntu3.2. Isto tako u 10.10 je 3.5.x~dfsg ovo mi ne lici bas na oznake redovnih fajlova. 10.10 je instaliran pre par dana.

Sa jednog od servera - verzija sambe 3.4.8, do duse setovana da radi kao domen kontroler, a evo setovanja za public share:

[public]
comment = Public folder
writeable = yes
create mode = 777
public = yes
write list = @users
path = /home/samba/public
directory mode = 777

Inace, za file sharing izmedju *nix masina ne koristim sambu vec nfs server (moguce je setovanje samba+nfs na istom serveru i 'deljenje' foldera).
 
Poslednja izmena:
Hvala, to nije ono stoje mene zanimalo, GUI altka to sam pitao. Pitao sam za program slican Nautilisu, Total commanderu, da vidim clanove workgrupe, izberem racunar, izaberem folder, copy/paste sa misem itd... Sad radim screenshot-ove ekrana pa cu to negde okaciti i pokazati kako to radi-neradi u kucnim mrezama satavljenim od win i ubuntu masina.:Crash:
 
GUI "altka" za Linux sličan TC je Krusader.
Inače mislim da ćeš lakše rešiti problem "čistom" instalacijom Ubuntu-a 10.10. Previše ljudi se žali zbog problema prilikom abdejta. Ja lično ne koristim Ubuntu, koristim Suse, tako da mi nemojte zameriti na mišljenju.
 
GUI "altka" za Linux sličan TC je Krusader.
Inače mislim da ćeš lakše rešiti problem "čistom" instalacijom Ubuntu-a 10.10. Previše ljudi se žali zbog problema prilikom abdejta. Ja lično ne koristim Ubuntu, koristim Suse, tako da mi nemojte zameriti na mišljenju.
Koristim Krusader ali to nije isto kao TC (slican jeste) ili Nautilus.
Nemam problem sa 10.10 nego sa 10.04 LTS.
Ne pratkijujem "ciste instalacije" cak ni u Windowsu, za ovih 10 godina XP sam tri puta instalisao od pocetka.
.
 
Hvala, to nije ono stoje mene zanimalo, GUI altka to sam pitao. Pitao sam za program slican Nautilisu, Total commanderu, da vidim clanove workgrupe, izberem racunar, izaberem folder, copy/paste sa misem itd... Sad radim screenshot-ove ekrana pa cu to negde okaciti i pokazati kako to radi-neradi u kucnim mrezama satavljenim od win i ubuntu masina.:Crash:

Nekada davno postojali su linneigborhood, komba i gomila slicnih programa ali sam ubedjen da su ovi projekti odavno mrtvi.
 
Nekada davno postojali su linneigborhood, komba i gomila slicnih programa ali sam ubedjen da su ovi projekti odavno mrtvi.

Da ti projekti su mrtvi, bas am citao za linneigborhood. Nautilus to radi ali sad u 10.04 iz nekog razloga ne radi. Konqueror je to isto radio, smb4k itd. Mene izludjje to sto ne mogu da nadjem razlog zasto ne radi, da li je problem u sambi ili file browserima koji kiksaju. Nekad je bilo da Nautilus kiksira ali Konqueror nikada, uvek je nepogresivo radio browse mreze, prikazao workgrupu, clanove workgrupe i mogao si da otvoris svaki share folder. Sada imam situaciju jedna Ubuntu masina vidi sve osim druge Ubuntu masine, postavke identicne, druga Ubuntu masina vidi samo sebe. Gledam nautilus, ako sve radi imas ikone share masina i ikonu da imas mrezu. Kad kliknes na ikonu mreze otvori i prikaze workgrupu, klik na ikonu workgrupe daje ikone svih masina koje nesto sheruju. To sto prikaze je isto kao i prvi ekran Nautilusa ali nekad i nije. Sad mene zanima ko uopste sta azurira, prikacio sam jednu masnu u mrezu, u pocetnom ekranu Nautilusa nema te masina, pod workgrupom je ima, znam da je potrebno neko vreme ali je ocito da te dve stavri se ne azuriraju na isti nacin. Postoji file na cache diru browse.dat u njemu je workgrupa i share masine, ko njega azurira jer je ocito da jedna grana Nautilusa cita taj file, isto tako kod podizanja sistema file se azurira.
 
Kod:
sudo iptables -L

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
Iptables na obe masine potpuno isto.
Kada na Ubuntu masini koja izludjuje dignem kraoz VMware XP bridge mod, share folder od te virtuelme masine vidi se u mrezi, ne vidi ga samo taj Ubuntu. Dok je radilo kako treba Ubuntu i virtuelna masina mogli su da razmenjuju fajlove i videli su se u mrezi kao Ubuntu masina i kao druga XP masina.
 
Bio sam naleteo na program kojim se setuje share na Ubuntu, program setuje share folder, dozvole ali i setuje po NetBios imenu sve masine koje mogu da pristupe. Kad se kroz taj program odradi setovanje onda sve radi. Sad sam prevrnuo ceo synaptic i ne mogu da nadjem koji je to program, mozda je neki nezavisan ili neki KDE, ne mogu da se setim kako se zvao. Mislim da nije bilo u opisu SMB/CIF nego SMB i nesto drugo.
Mislim da je inneigborhood sad prekrsten u pyneigborhood...
 
Taj deo posla obavlja ti nmbd daemon (deo sambe), ja bih na tvom mestu najpre proverio logove da vidim da li nmbd uopste radi i da li se nalazi u odgovarajucim runlevelima. Isto tako proveri da ti nije slucajno port 137 fajervolovan.

The nmbd server daemon understands and replies to NetBIOS name service requests such as those produced by SMB/CIFS in Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, and LanManager clients. It also participates in the browsing protocols that make up the Windows Network Neighborhood view. The default port that the server listens to for NMB traffic is UDP port 137.
 
Poslednja izmena:
lega99@Unknown0:~$ ps awux | grep nmbd
root 3024 0.0 0.0 8764 1620 ? Ss 14:07 0:00 nmbd -D
lega99 3295 0.0 0.0 3320 792 pts/0 S+ 14:27 0:00 grep --color=auto nmbd
lega99@Unknown0:~$ ps awux | grep smbd
root 3011 0.0 0.1 15280 3904 ? Ss 14:07 0:00 smbd -F
root 3014 0.0 0.0 15280 1176 ? S 14:07 0:00 smbd -F
root 3039 0.0 0.1 15352 3004 ? S 14:08 0:00 smbd -F
root 3048 0.0 0.1 15352 3008 ? S 14:08 0:00 smbd -F
root 3059 0.0 0.1 15352 3156 ? S 14:09 0:00 smbd -F
lega99 3298 0.0 0.0 3320 796 pts/0 S+ 14:28 0:00 grep --color=auto smbd
Ovo ja ne znam da rastumacim -D je demon proces a trebalo bi da je service tako su prekrstili i startuje se i stopira kao service, to isto vazi i za smbd, -F je pozadinski proces. Sta je ovo 0.0 i 0.1 na onoj drugoj koja radi te vrednosti su 0.0 i 0.2 ili 0.3.
 
Nmbd je podignut, jesi li cekirao firewall i u log za nmbd(sambu) ?
 
log.nmbd
Kod:
  Samba name server UNKNOWN0 is now a local master browser for workgroup MSHOME on subnet 172.16.181.1
  
  *****
[2010/11/02 19:33:14,  0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
  *****
  
  Samba name server UNKNOWN0 is now a local master browser for workgroup MSHOME on subnet 192.168.96.1
  
  *****
[2010/11/02 19:33:14,  0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
  *****
  
  Samba name server UNKNOWN0 is now a local master browser for workgroup MSHOME on subnet 10.0.0.4
  
  *****
[2010/11/02 19:33:14,  0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
  *****
  
  Samba name server UNKNOWN0 is now a local master browser for workgroup MSHOME on subnet 10.0.0.6
  
  *****

Sta ce ova adresa 172.16.181.1 i ova 192.168.96.1 kad sam ja setovao vmware u bridge mod i kad podignem virtuelni XP i pogledam sa ipconfig /all IP je u delu adresa koje su kod mene 10.0.0.x
 
log.smbd tu su cudne poruke jer su kod mene sve fiksne IP u lokalnoj mrezi i to sa 10.0.0.0.x
[2010/11/02 19:32:48, 0] smbd/server.c:1069(main)
smbd version 3.4.7 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2010/11/02 19:32:48, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/11/02 19:32:48, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused
[2010/11/02 19:32:48, 0] smbd/server.c:1115(main)
standard input is not a socket, assuming -D option
[2010/11/02 19:32:48, 0] lib/util_sock.c:902(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2010/11/02 19:32:48, 0] smbd/server.c:457(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address family not supported by protocol
[2010/11/02 19:32:48, 0] lib/util_sock.c:902(open_socket_in)
open_socket_in(): socket() call failed: Address family not supported by protocol
[2010/11/02 19:32:48, 0] smbd/server.c:457(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address family not supported by protocol
 
log.winbindd-idmap i ovde su cudne stvari
[2010/11/02 19:33:12, 1] winbindd/idmap.c:438(idmap_init_passdb_domain)
Could not init passdb idmap domain
[2010/11/02 19:33:12, 1] winbindd/idmap_tdb.c:214(idmap_tdb_load_ranges)
idmap uid missing
[2010/11/02 19:33:12, 0] winbindd/idmap_tdb.c:287(idmap_tdb_open_db)
Upgrade of IDMAP_VERSION from -1 to 2 is not possible with incomplete configuration
[2010/11/02 19:33:12, 1] winbindd/idmap.c:321(idmap_init_domain)
idmap initialization returned NT_STATUS_UNSUCCESSFUL
[2010/11/02 19:33:12, 0] winbindd/idmap.c:201(smb_register_idmap_alloc)
idmap_alloc module tdb already registered!
[2010/11/02 19:33:12, 0] winbindd/idmap.c:149(smb_register_idmap)
Idmap module passdb already registered!
[2010/11/02 19:33:12, 0] winbindd/idmap.c:149(smb_register_idmap)
Idmap module nss already registered!
[2010/11/02 19:33:12, 1] winbindd/idmap_tdb.c:214(idmap_tdb_load_ranges)
idmap uid missing
[2010/11/02 19:33:12, 0] winbindd/idmap_tdb.c:287(idmap_tdb_open_db)
Upgrade of IDMAP_VERSION from -1 to 2 is not possible with incomplete configuration
 
Sta ce ova adresa 172.16.181.1 i ova 192.168.96.1 kad sam ja setovao vmware u bridge mod i kad podignem virtuelni XP i pogledam sa ipconfig /all IP je u delu adresa koje su kod mene 10.0.0.x

nbmd log je ok, a upravo zbog bridge moda samba je postala master browser u svim network segmentima koji su joj dostupni
 
log.smbd tu su cudne poruke jer su kod mene sve fiksne IP u lokalnoj mrezi i to sa 10.0.0.0.x

Hm.....da nemas mozda ukljucen SELinux ili nesto slicno? Ovo sam vidjao na fedori gde je SELinux po defaultu ukljucen.

Da ne pisem i treci post ubacicu ovde i winbindd - on ti nije bitan dok sambu ne prikacis na windows AD.
 
Hm.....da nemas mozda ukljucen SELinux ili nesto slicno? Ovo sam vidjao na fedori gde je SELinux po defaultu ukljucen.

Da ne pisem i treci post ubacicu ovde i winbindd - on ti nije bitan dok sambu ne prikacis na windows AD.

Ne znam kako da pogledam a i sad je sve otislo u PM. Uradio sam upgrade na 10.10 da bi obe masine imale istu verziju sambe, upgrade odradi ali ode sve u PM.
 
Hm.....da nemas mozda ukljucen SELinux ili nesto slicno? Ovo sam vidjao na fedori gde je SELinux po defaultu ukljucen.

Da ne pisem i treci post ubacicu ovde i winbindd - on ti nije bitan dok sambu ne prikacis na windows AD.

Postoje na obe Ubuntu masine dve rutine u synapticu koje su instalirane i u cijem imenu ima xxselinux i nista vise
 
Poslednja izmena od urednika:
Postoji jos jedna suluda cinjenica, lampice na switchu na portu gde je veznana network karica i preko koje ide samba non-stop treperi. Saobracaj na izlanom portu switcha prewa ruteru ne postoji a ni ruter ne registruje bilo kakav izlazni saobracaj prema WAN mrezi. Ne registruje se po lampicma na switchu ni bilo kakav saobracaj prema ostalim clanovima mreze. :Crash:
 
var/cache/samba/browse.dat se ne azurira, taj fajl citaju svi GUI programi koji vizuelno browsuju mrezu. Zasto se ne azurira a na drugoj masini se azurira to ne mogu da otkrijem. nmbd ili smbd ili nesto trece treba taj fajl konstatno da azurira.
 
Nazad
Vrh Dno