Windows 7 - Zugriff auf Samba-Server

Dieses Thema im Forum "Samba" wurde erstellt von Knorpi, 24.02.2011.

  1. #1 Knorpi, 24.02.2011
    Zuletzt bearbeitet: 24.02.2011
    Knorpi

    Knorpi Grünschnabel

    Dabei seit:
    24.02.2011
    Beiträge:
    6
    Zustimmungen:
    0
    Hallo,

    der Zugriff auf meinen Samba-Server funktioniert einwandfrei von einem
    Client mit Windows XP, aber nicht von einem Client mit Windows 7.

    Samba-Server, Name: maximus, IP: 192.168.0.11
    Client, Name: wagner

    Zugriff von Windows XP:

    Man gibt im Explorer "\\Maximus" ein und meldet sich anschließend
    mit "wagner" an. Dies funktioniert.

    Zugriff von Windows 7 (auf denselben Server):

    Man gibt im Explorer "\\Maximus" ein. Die Passwortabfrage kommt, aber eine
    Anmeldung mit "wagner" schlägt fehl. Gibt man im Explorer
    aber "\\192.168.0.11" an, funktioniert die Anmeldung.

    Was kann man tun, damit es mit Namen genauso funktioniert, wie mit IP?

    Danke!
    Magnus




    Hier meine smb.conf:
    ----------
    [global]

    workgroup = Wagner
    security = user
    server string = Wombels Home
    wins support = yes
    browseable = yes

    [wagner]

    comment = Home of Magnus
    path = /mws/stg/pub/Home/wagner
    browsable = no
    writable = yes
    valid users = wagner

    ----------

    Hier die letzten Einträge in log.nmbd:

    [2011/02/20 07:53:50, 0] nmbd/nmbd.c:terminate(68)
    Got SIGTERM: going down...
    [2011/02/20 07:53:53, 0] nmbd/nmbd.c:main(849)
    nmbd version 3.2.5 started.
    Copyright Andrew Tridgell and the Samba Team 1992-2008
    [2011/02/20 07:53:53, 0] nmbd/asyncdns.c:start_async_dns(155)
    started asyncdns process 7950
    [2011/02/20 07:55:30, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage
    (395)
    *****

    Samba name server MAXIMUS is now a local master browser for workgroup
    WAGNER on subnet 192.168.0.11

    *****
    [2011/02/20 07:55:30, *0]
    nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(350)
    find_domain_master_name_query_fail:
    Unable to find the Domain Master Browser name WAGNER<1b> for the workgroup
    WAGNER.
    Unable to sync browse lists in this workgroup.
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. #2 Hobbystern, 24.02.2011
    Hobbystern

    Hobbystern Wahl-Debianer

    Dabei seit:
    02.02.2007
    Beiträge:
    186
    Zustimmungen:
    0
    Ort:
    westl. Ruhrgebiet
    Nabend!

    Schau mal ...

    Code:
    find_domain_master_name_query_fail:
    
    Schau doch ergänzend in die WIndows Ereignisanzeige, es sieht aber so aus als ob die Zusammenarbeit mit dem DNS nicht klappt (Samba 4 wird das in Kombi erhalten)
     
  4. #3 Remidemi, 24.02.2011
    Remidemi

    Remidemi Routinier

    Dabei seit:
    17.03.2008
    Beiträge:
    352
    Zustimmungen:
    0
    Ort:
    Südpfalz
    Bist du mit der Windows 7 Maschine in der gleichen Arbeitsgruppe/Domäne wie mit Windows XP?
     
  5. Knorpi

    Knorpi Grünschnabel

    Dabei seit:
    24.02.2011
    Beiträge:
    6
    Zustimmungen:
    0
    Hallo,

    ja, es ist die gleiche Arbeitsgruppe, d. h. ich habe sie im Windows-Client genauso genannt ("WAGNER").

    Wenn es ein DNS-Problem gäbe, käme ich doch gar nicht erst zum Server und dort käme es nicht zu dem Log-Eintrag, oder?

    Nur, warum verhält sich der Samba-Server unterschiedlich, je nach dem, ob ich über Name oder IP zugreife? #-)

    Grüße
    Magnus
     
  6. Knorpi

    Knorpi Grünschnabel

    Dabei seit:
    24.02.2011
    Beiträge:
    6
    Zustimmungen:
    0
    Hallo nochmal,

    hat jemand vielleicht einfach eine Konfiguration, die mit Windows 7 funktioniert? So umfangreich ist meine ja nicht und ich könnte es mit der ja einfach mal probieren...

    Magnus
     
  7. Lord_x

    Lord_x Guest

  8. Anzeige

    Vielleicht findest du HIER Antworten.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  9. Knorpi

    Knorpi Grünschnabel

    Dabei seit:
    24.02.2011
    Beiträge:
    6
    Zustimmungen:
    0
    Danke, aber muss man sich wirklich mit einer Lösung abfinden, bei der man beim Client Registry-Änderungen machen muss? :think:

    (Ich verwende ja auch keine Domäne...)

    Geht das nicht auch anders?

    Magnus
     
  10. daboss

    daboss Keine Macht für niemand!

    Dabei seit:
    05.01.2007
    Beiträge:
    1.294
    Zustimmungen:
    0
    Ort:
    sydney.australia.world
    Das läuft hier mit Vista- und Sevenclients einwandfrei. (Ohne das Registrygefrickel von oben, ;) welches dem Artikel nach ja auch nur Domains betrifft?)
    An sich ist die aber bis auf die zwei, drei Freigaben und afair der "name resolve order" ziemlicher (Ubuntu 10.04 Netbook) Standard...
    Code:
    #
    # 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 = WORKGROUP
    
    # 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
    
    # 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 = bcast lmhosts host wins
    
    #follow symlinks = yes
    #wide links = yes
    #unix extensions = no
    
    #### 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 = no
    
    # 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 = 0770
    
    # 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 = 0770
    
    # 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
    
    [Backup]
       comment = Backupverzeichnis
       browseable = no
       read only = no
       valid users = <myUserList>
       path = /mnt/disk1/Backup
    
    [Disk1]
       comment = Datenplatte1
       browseable = yes
       read only = no
       valid users = <myUserList>
       path = /mnt/disk1
    
    [Disk2]
       comment = Datenplatte2
       browseable = yes
       read only = no
       valid users = <myUserList>
       path = /mnt/disk2
    
    [Shared]
       comment = Gemeinsam
       browseable = yes
       read only = no
       valid users = <myUserList>
       path = /home/shared
    
    # 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 = yes
    ;   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, alex, afra, @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
    
     
Thema: Windows 7 - Zugriff auf Samba-Server
Besucher kamen mit folgenden Suchen
  1. samba client windows

    ,
  2. windows auf samba zugreifen

    ,
  3. wie kann ich auf mein samba konto zugreifen

    ,
  4. auf samba server zugreifen,
  5. samba client zugriff,
  6. windows 7 auf smb zugreifen,
  7. windows 7 samba,
  8. von windows auf samba share zugreifen,
  9. Win 7 und alte Samba server,
  10. samba windows 7 zugriff verweigert,
  11. linux samba encrypt passwords windows problem,
  12. windows 7 zugriff auf samba server,
  13. auf samba freigabe unter win 7 zugreifen,
  14. zugriff auf samba server,
  15. samba log windows 7,
  16. windows 7 samba 3 password,
  17. samba windows 7,
  18. windows 7 zugriff samba,
  19. samba server explorer passwort,
  20. Linux samba win7,
  21. windows samba client,
  22. win7 samba,
  23. samba smb.conf logon path windows 7,
  24. samba 4 windows 7 ohne domäne,
  25. ́windows 7 mit samba server
Die Seite wird geladen...

Windows 7 - Zugriff auf Samba-Server - Ähnliche Themen

  1. Problem beim Zugriff auf Windows 7 - Freigaben mit Solaris 11

    Problem beim Zugriff auf Windows 7 - Freigaben mit Solaris 11: Ich möchte mit Solaris 11 auf meine Windows 7 - freigaben zugreifen. Ich werde normal nach Benutzername und Passwort gefragt, aber wenn ich es...
  2. Schreibzugriff verweigert (SLES 11 / Client: Windows XP)

    Schreibzugriff verweigert (SLES 11 / Client: Windows XP): Hallöchen, ich stehe gerade vor einem Problem, bei dem ich mir bislang die Zähne ausbeiße: Vorweg: Ich habe hier 2 Server (SLES 11) - beide sind...
  3. Zugriff auf Windowsfreigabe aus Domäne

    Zugriff auf Windowsfreigabe aus Domäne: Moin Moin, ich habe hier ein kleines Problem. Aber irgendwie weiss ich nicht, wie ich es lösen kann/soll. Ich habe einen Linux Rechner in...
  4. Windows Services for Unix Zugriff auf Linux?

    Windows Services for Unix Zugriff auf Linux?: Hallo zusammen, kennt zufällig jemand die WSFU? Ich hatte überlegt, ob ich damit evtl. ein Linux System quasi in ein Windows Laufwerk mounten...
  5. MySQL auf Windows: Lange Zugriffszeiten unter Linux

    MySQL auf Windows: Lange Zugriffszeiten unter Linux: Hallo. Ich arbeite in meiner Freizeit in einer Gruppe mit, in der wir gemeinsam verschiedene Softwareprojekte realisieren. Dazu treffen wir uns...