Nieuws:

Welkom, Gast. Alsjeblieft inloggen of registreren.
Heb je de activerings-mail niet ontvangen?

Auteur Topic: [opgelost] Wat zie ik over het hoofd?  (gelezen 1060 keer)

Offline grafcom

  • Lid
  • Steunpunt: Nee
[opgelost] Wat zie ik over het hoofd?
« Gepost op: 2009/08/12, 15:02:18 »
Hallo,

ik probeer mijn Ubuntu 9.04 in een windows netwerk aan de praat te krijgen.

Vanuit windows kan ik wel naar Ubuntu maar omgekeerd niet.

Hier staan vele posts over maar ik kom er niet uit.

Wat heb ik tot nu toe gedaan:


Citaat
Open this file for editing with the following command:

Code:
gksudo gedit /etc/samba/smb.conf

Scroll down to the section that looks like this:

Code:
 #======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUPChange “WORKGROUP” in “workgroup = WORKGROUP” to match your Windows workgroup.

It may also help to add netbios name = computer-name just below "workgroup = WORKGROUP".

Your "computer-name" can be anything, but common convention is to use the name you gave it when you installed Ubuntu (everything after the "@" symbol on the CLI prompt).

For example, here's my CLI prompt:

Code:
dmizer@shinkansen:~$And here's my smb.conf file:

Code:
#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP
   netbios name = shinkansenNow,

save the file by clicking on "File" > "save", close gedit, and restart samba with the following command:

Code:
sudo /etc/init.d/samba restart

Daarna:

Citaat
Open /etc/nsswitch.conf for editing with the following command:

Code:
gksudo gedit /etc/nsswitch.confFind the line that looks something like:

Code:
hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4For this line, order IS important. You’ll need to add the “wins” option before dns, so the line reads like this:

Code:
 hosts:          files mdns4_minimal [NOTFOUND=return] wins dns mdns4Now, save the file by clicking on "File" > "save" and close gedit.

You'll also have to install the winbind daemon in order to resolve hostnames. This is easily done with the following command:

Code:
sudo apt-get install winbind

Then, either restart networking or reboot.

Dit alles had alleen als resultaat dat ik onder Locaties - Netwerk nu ook de gedeelde mappen van de Ubuntu computer zag naast het icoontje Windows Netwerk maar wanneer ik daarop druk krijg is de melding "Kon lijst van gedeelde mappen niet van server opvragen"

Ik heb ook volgende nog geprobeerd in de smb.conf file:

Citaat
Next scroll down a few lines until you find the line name resolver order = lmhosts hosts wins bcast and delete the semicolon at the beginning of the line.

Geen resultaat. Volgende regels kon ik niet vinden in de smb.conf file dus kon ik die ook niet proberen.

Citaat
hosts allow = 127. 192.168.1.
interfaces = 127.0.0.1/8 192.168.1.0/24[/font]
bind interfaces only = yes
remote announce = 192.168.1.255
remote browse sync = 192.168.1.255

Ik gebruik geen Firewall op Ubuntu en onder Windows heb ik dit alles ook geprobeerd met de Firewall uit.

Heeft er iemand nog een suggestie naar aanleiding van deze poging?

Bij voorbaat dank
« Laatst bewerkt op: 2009/08/13, 14:13:46 door grafcom »

Offline grafcom

  • Lid
  • Steunpunt: Nee
Re: Wat zie ik over het hoofd?
« Reactie #1 Gepost op: 2009/08/12, 19:49:14 »
Nog ter aanvulling, zo zie mijn smb.conf er nu uit:

#
# 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 ###

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

# 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 = true

# 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 <<kahan@informatik.tu-muenchen.de> 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 = auto

# 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

#======================= 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
   read only = yes
   guest ok = no
# 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

Offline Gandyman

  • Lid
  • Steunpunt: Nee
Re: Wat zie ik over het hoofd?
« Reactie #2 Gepost op: 2009/08/13, 00:02:00 »
Hieronder een werkende cfg van Samba.
Deze moet jij ietsje aanpassen natuurlijk voor jouw situatie, kwa namen, WERKGROEP en mappen.

[global]
   workgroup = DOMA
   netbios name = MOSCOW
   server string = %h server
   obey pam restrictions = Yes
   passdb backend = tdbsam
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
   syslog = 0
   log file = /var/log/samba/log.%m
   max log size = 1000
   load printers = No
   dns proxy = No
   wins support = yes
   panic action = /usr/share/samba/panic-action %d
   invalid users = root

   

[Werkmap-Jana]
   path = /data-doma/werkmap-jana
   valid users = server, jana
   admin list = server
   write list = server, jana
   read only = Yes
   guest ok = Yes
   hosts allow = 192.168.1.0/255.255.255.0
   create mask = 0777
   directory mask = 0777

[Werkmap-Pivni]
   path = /data-doma/werkmap-pivni
   valid users = server, jana
   admin list = server
   write list = server
   read only = Yes
   guest ok = Yes
   hosts allow = 192.168.1.0/255.255.255.0
   create mask = 0777
   directory mask = 0777

[MP3]
   path = /data-doma/mp3
   valid users = server, jana, michal
   admin list = server
   write list = server
   read only = Yes
   guest ok = Yes
   hosts allow = 192.168.1.0/255.255.255.0
   create mask = 0777
   directory mask = 0777

[Root-server]
   path = /
   valid users = server
   admin users = server
   read only = No

Wat uitleg

[global]

- workgroup = DOMA
DOMA is de naam van mijn network, maak hier van wat jij wil.
Vergeet dit dan niet bij de werkstations ook te doen.
WinXP home is standaard “MSHOME”
WINXP Pro is standaard “WERKGROEP” (Engelse versie = WORKGROUP)

- netbios name = MOSCOW
Mijn server heet Moscow en met de “netbios name” via http://moscow op mijn netwerk benaderen.
Dus als ik webmin wil opstarten, dan type ik https://moscow:10000
Dat is veel makkelijker te onthouden dan een IP adres.
Let op! Dit werkt alleen maar via je eigen netwerk.


[Werkmap-Jana]

-path = /data-doma/werkmap-jana
Dit is de werkmap van Jana, in deze map heeft zij lees- en schrijfrechten.
Server heeft hier alle rechten.

- valid users = server, jana
- admin list = server
- write list = server, jana
Zo stel je dan de rechten af op de map “werkmap-jana”

- hosts allow =x.x.x.0/255.255.255.0
(Hier ben ik nog niet uit of dat dit wel nut heeft, dat moet ik nog testen)

Vul hier het IP adres in van je router, de laatste cijfer eindig vaak met een 1, maak hier 0 van.
255.255.255.0 is het subnetmask, vaak is dit hetzelfde wat ik hier heb, controleer dat even.


[Werkmap-Pivni]

-path = /data-doma/werkmap-pivni
Dit is de werkmap van Pivni, in deze map heeft hij lees- en schrijfrechten.
Server heeft hier alle rechten en Jana heeft alleen maar leesrecht.

- valid users = server, pivni, jana
- admin list = server
- write list = server, pivni
Zo stel je dan de rechten af op de map “werkmap-pivni”

- hosts allow =x.x.x.0/255.255.255.0
(Hier ben ik nog niet uit of dat dit wel nut heeft, dat moet ik nog testen)

Vul hier het IP adres in van je router, de laatste cijfer eindig vaak met een 1, maak hier 0 van.
255.255.255.0 is het subnetmask, vaak is dit hetzelfde wat ik hier heb, controleer dat even.


[MP3]

-path = /data-doma/mp3
Dit is een map waar alleen gebruiker “server” alle rechten heeft.
Server heeft hier alle rechten en Pivni, Jana en Michal hebben alleen maar leesrecht.

- valid users = server, pivni, jana, michal
- admin list = server
- write list = server
Zo stel je dan de rechten af op de map “werkmap-pivni”

- hosts allow =x.x.x.0/255.255.255.0
(Hier ben ik nog niet uit of dat dit wel nut heeft, dat moet ik nog testen)

Vul hier het IP adres in van je router, de laatste cijfer eindig vaak met een 1, maak hier 0 van.
255.255.255.0 is het subnetmask, vaak is dit hetzelfde wat ik hier heb, controleer dat even.


[Root-server]
- path = /
- valid users = server
- admin users = server

Zo als je al aan “path” kan zien is dit de root van mijn Linux server.
Hier heeft alleen Server rechten en voor de rest niet (ook geen leesrecht)

Kijk hier mee alsjeblieft uit, hier mee kan je mappen en bestanden van je Linux PC lezen, bewerken, maar ook verwijderen.
Hiermee kan je dus heel je server mee verpesten.
I don't suffer from insanity, I enjoy every minute of it.
Microsoft geeft je een raam, Linux geeft je een heel huis :D

Offline grafcom

  • Lid
  • Steunpunt: Nee
Re: Wat zie ik over het hoofd?
« Reactie #3 Gepost op: 2009/08/13, 12:45:51 »
Hallo Gandyman,

hartelijk dank voor je hulp.

Ik heb het nu zover dat ik vanuit Ubuntu ook de XP computers in het netwerk zie.

Echter kan ik maar op 1 PC binnenkomen. De andere geeft aan "Kon de locatie niet aankoppelen"

Moet ik hier nog iets in aanpassen? hosts allow = 192.168.1.0/255.255.255.0

Vanuit beide XP computers kan ik wel naar de map van Ubuntu.



Offline Gandyman

  • Lid
  • Steunpunt: Nee
Re: Wat zie ik over het hoofd?
« Reactie #4 Gepost op: 2009/08/13, 13:08:22 »
Dit stukje
hosts allow = 192.168.1.0/255.255.255.0
Is eerlijk gezegd een beetje tricky omdat het voor iedereen anders kan zijn.
Zie het dus als een vuistregel.
Het ip adres wat hier staat kan je het beste altijd aanhouden dat dit de Gateway is van je router.
Dit vind je als je in Ubuntu ïfconfig typt in terminal.

Het kan dus 192.168.1.0 zijn, of wat veel voorkomt 192.168.1.1  bijv.
In ieder geval niet een IP adres van een PC op je netwerk. !

De melding "Kon de locatie niet aankoppelen" kan komen omdat op de PC waar je op wilt komen de Firewall je tegenhoud,
Dus de firewall van die PC houd je tegen, loop dit ff na in die firewall.

Of de settings van de gedeelde map op die PC staan niet goed. ?

I don't suffer from insanity, I enjoy every minute of it.
Microsoft geeft je een raam, Linux geeft je een heel huis :D

Offline grafcom

  • Lid
  • Steunpunt: Nee
Re: Wat zie ik over het hoofd?
« Reactie #5 Gepost op: 2009/08/13, 13:19:09 »
Ja, de Firewall dus  =D

Ga nu uitzoeken hoe dit "toe te staan"

Nogmaals hartelijk dank!

Offline Gandyman

  • Lid
  • Steunpunt: Nee
Re: [opgelost] Wat zie ik over het hoofd?
« Reactie #6 Gepost op: 2009/08/13, 15:48:02 »
NP  ;)
I don't suffer from insanity, I enjoy every minute of it.
Microsoft geeft je een raam, Linux geeft je een heel huis :D