Nieuws:

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

Auteur Topic: [OPGELOST] Krijg mijn server niet te zien  (gelezen 3557 keer)

Offline vis

  • Lid
  • Steunpunt: Nee
[OPGELOST] Krijg mijn server niet te zien
« Gepost op: 2009/04/17, 01:04:52 »
Beste allemaal,

Ik heb alle handleindingen gevolgd om een sambashare aan te maken. In mij smb.conf heb ik het volgende toegevoegd:

[Movies]
        comment = Movies
        writeable = yes
        valid users =
        invalid users =
        public = yes
        path = /home/vis/downloads/complete/Movies

Als ik met mijn mediaplayer (freecom mg-35) in het netwerk ga zoeken, dan ziet hij mijn server niet. Ook onder windows XP, kan ik de server (map movies) niet terugvinden. Moet ik nog ergens mijn server openstellen? Poorten?

Vis.
« Laatst bewerkt op: 2009/04/17, 16:43:31 door vis »

Online Johan van Dijk

  • Administrator
    • johanvandijk
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #1 Gepost op: 2009/04/17, 01:43:19 »
        valid users =
Geef daar eens de gebruikersnamen/groep op van de accounts die toegang mogen hebben?

Daarna wel even de server opnieuw starten.
sudo /etc/init.d/samba restart

Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #2 Gepost op: 2009/04/17, 01:52:11 »
Onder windows kan ik nu mijn samba server zien. Alleen nog niet mijn map Movies:

[Movies]
        comment = Movies
        writeable = yes
        valid users = guest
        invalid users =
        public = yes
        path = /home/vis/downloads/complete/Movies

Ik heb een user guest aangemaakt in mijn smbpasswd.

Online Johan van Dijk

  • Administrator
    • johanvandijk
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #3 Gepost op: 2009/04/17, 01:55:33 »
Dat is wel verwarrend, want een aparte user die je guest noemt is niet hetzelfde als de speciale guest user.
Maar dat kan ik helemaal mis hebben....

Waarom noem je die gebruiker niet gewoon vis? Of movies? Of een andere willekeurige naam die je makkelijk kan onthouden.
Daarna maak je die nieuwe sambagebruiker aan op de server:
sudo smbpasswd -a gebruikersnaam

Hierna weer de samba server restarten.

Vervolgens configureer je die gebruiker ook in je mediaspeler en evt. Windows.

Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #4 Gepost op: 2009/04/17, 02:10:43 »
De rede waarom ik een guest user heb aangemaakt, komt omdat ik het ook aan de praat wil hebebn met mijn freecom 35. Als ik daar op de wiki kijk, staat er dat ik het volgende moet doen:

Linux

This is how you can get MG-35 to work with a Linux SMB share, preserving the opportunity to have security = user. The example is for one share holding your private files (requiring username and password) and another public share granting all users read and write access.

 

You will also need to create a samba user called “guest” (command: smbpasswd -a username). Use any password if your not allowed to create a new user with an empty password and reset the password to null (command: smbpasswd -n username):

 

File: /etc/samba/smb.conf
[global]
workgroup = YOUR_WORKGROUP_NAME
netbios name = YOUR_SERVER_NAME
passdb backend = tdbsam
security = user
encrypt passwords = true
guest account = guest
null passwords = yes
socket options = TCP_NODELAY
[Private]
comment = Private files on server
path = /path/to/privte/files
read only = no
valid users = your_user_account
[Public]
comment = Public files on server
path = /path/to/public/files
invalid users = root
guest ok = yes
public = yes
writeable = yes

Online Johan van Dijk

  • Administrator
    • johanvandijk
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #5 Gepost op: 2009/04/17, 02:18:39 »
Volgens mij mis je in je startpost dan nog deze regel:
guest ok = yes

Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #6 Gepost op: 2009/04/17, 02:28:15 »
Ook na het toevoegen wil het niet lukken. Hier dan mijn hele smb.conf:

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

# server string is the equivalent of the NT Description field
   server string = %h server

# 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

# If we receive WINS server info from DHCP, override the options above.
   include = /etc/samba/dhcp.conf

# 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
   null passwords = yes
   guest account = guest


# 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

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

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

[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.
# The following parameter makes 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

[Movies]
   comment = Movies
   writeable = yes
   valid users = guest
   invalid users = root
   guest ok = yes
   public = yes
   path = /home/vis/downloads/complete/Movies

Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #7 Gepost op: 2009/04/17, 02:35:33 »
Misschien ligt het aan de logheid van windows, maar nu werkt het onder windows wel. Helaas vind mijn freecom mg-35 nog steeds mijn server niet.

Bedankt iig alavst voor alle hulp tot nu toe.

Online Johan van Dijk

  • Administrator
    • johanvandijk
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #8 Gepost op: 2009/04/17, 02:38:40 »
Even verder puzzelen dus...
Mooi dat het al gedeeltelijk werkt :)

Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #9 Gepost op: 2009/04/17, 13:10:08 »
Heb toch 2 uurtjes lopen spelen, maar ik krijg het op mijn mediaplayer niet voor elkaar. Onder windows kan ik dus wel mijn samba share benaderen en ziet dus ook mijn server. Op mijn mediaplayer ziet hij niet eens mijn server. Hopelijk kent iemand dit probleem, want ik kom er echt niet uit.

Vis

Offline elgl

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #10 Gepost op: 2009/04/17, 13:33:05 »
voeg bij de share eens toe,

browsable = yes


Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #11 Gepost op: 2009/04/17, 13:39:51 »
Heb dit erbij gezet, daarna samba geherstart maar helaas nog niks. Bedankt iig voor het meedenken.

Vis

Offline elgl

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #12 Gepost op: 2009/04/17, 13:52:30 »
en als je de config versimpelt naar,

[Movies]
   comment = Movies
   path = /home/vis/downloads/complete/Movies
   writeable = yes
   browsable = yes
   guest ok = yes

vindt ie m dan nog niet?

Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #13 Gepost op: 2009/04/17, 13:57:32 »
Helaas.... snap er echt niks meer van.

Offline elgl

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #14 Gepost op: 2009/04/17, 13:58:35 »
hmm... heeft die media player ook mogelijkheden om bv te pingen? dan kan je controleren of hij iig netwerk verbinding heeft, een geldig ip krijgt etc.

Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #15 Gepost op: 2009/04/17, 14:00:22 »
Hij kan hem wel pingen:

server:/# ping 192.168.1.133
PING 192.168.1.133 (192.168.1.133) 56(84) bytes of data.
64 bytes from 192.168.1.133: icmp_seq=1 ttl=255 time=3.72 ms
64 bytes from 192.168.1.133: icmp_seq=2 ttl=255 time=0.376 ms
64 bytes from 192.168.1.133: icmp_seq=3 ttl=255 time=0.327 ms

Offline elgl

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #16 Gepost op: 2009/04/17, 14:13:25 »
Ik zag wel op de site van freecom dat er firmware updates zijn, wellicht dat dat het oplost...

http://www.freecom.nl/firmware.asp?form1=true&form2=true&serie=12500&Manufactures=12500

edit: vindt hij de computer uberhaubt niet of krijg je een foutmelding bij het benaderen van de gedeelde map?

edit2:
kan je in windows wel via my network places/mijn netwerk locaties gewoon naar de server bladeren, zonder het ip of de naam rechtstreeks in te typen? zo nee, dan is dit het probleem en dan moet ervoor gezorgd worden dat dit wel kan.
« Laatst bewerkt op: 2009/04/17, 14:27:15 door elgl »

Offline vis

  • Lid
  • Steunpunt: Nee
Re: Krijg mijn server niet te zien
« Reactie #17 Gepost op: 2009/04/17, 15:27:47 »
Ik was even offline om mijn mediaplayer te backuppen. Nu hij gebackuped is, heb ik de alles geformateerd en de nieuwste firmware nogmaals geinstalleerd en nu werkt alles perfect.
Ik blijf het een beetje vreemd vinden aangezien ik dezelfde firmware als had. Misschien is er de vorige keer iets niet goed gegaan met de firmware upgrade?

In ieder geval hartelijk bedankt voor alle moeite en tips.

Vis.