archlinux smbclient problem

Diskutiere archlinux smbclient problem im Sonstige Linux Distributionen Forum im Bereich Linux Distributionen; Hi !! Habe folgendes problem ! Ich habe samba installiert und konfiguriert! ich kann von einem windows pc auf eine Freigabe unter linux...

  1. #1 Hannes3, 28.02.2006
    Zuletzt bearbeitet: 28.02.2006

    Hannes3 Doppel-As

    Dabei seit:
    Hi !!

    Habe folgendes problem !
    Ich habe samba installiert und konfiguriert! ich kann von einem windows pc auf eine Freigabe unter linux zugreifen. Jedoch kann ich nicht von dem Linux rechner auf die windowsfreigabe zugreifen!

    Konqueror smb:/ zeigt mir den pc und die Arbeitsgruppen im Netzwerk an, jedoch sobald ich auf den PC zugreife erscheint folgende fehler message:
    Internal Error
    Please send a full bug report at
    libsmbclient reported an error, but did not specify what the problem is. This might indicate a severe problem with your network - but also might indicate a problem with libsmbclient.
    If you want to help us, please provide a tcpdump of the network interface while you try to browse (be aware that it might contain private data, so do not post it if you are unsure about that - you can send it privately to the developers if they ask for it)
    Fersuche ich esüber die console mit smbclient IP des Win Rechners kommt folgende Ausgabe:

    [hannes@frequency ~]$ smbclient -L
    Domain=[WINPC] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
            Sharename       Type      Comment
            ---------       ----      -------
    Error returning browse list: NT_STATUS_OK
    session request to failed (Called name not present)
    session request to 192 failed (Called name not present)
    Domain=[WINPC] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
            Server               Comment
            ---------            -------
            Workgroup            Master
            ---------            -------
    smbclient Eigene IP
     [hannes@frequency ~]$ smbclient -L
    Domain=[MSHEIMNETZ] OS=[Unix] Server=[Samba 3.0.21b]
            Sharename       Type      Comment
            ---------       ----      -------
            Unnamed         Disk
            HANNESHANNES    Disk      /home/hannes/hannes
            IPC$            IPC       IPC Service (Samba Server)
            ADMIN$          IPC       IPC Service (Samba Server)
    Domain=[MSHEIMNETZ] OS=[Unix] Server=[Samba 3.0.21b]
            Server                Comment
            ---------                 -------
            FREQUENCY    Samba Server
            WINPC              Momo
            Workgroup            Master
            ---------                   -------
    Meine smb.conf
    #======================= Global Settings =====================================
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
    workgroup = MSHEIMNETZ
    # server string is the equivalent of the NT Description field
    server string = Samba Server
    # Security mode. Defines in which mode Samba will operate. Possible
    # values are share, user, server, domain and ads. Most people will want
    # user level security. See the Samba-HOWTO-Collection for details.
    security = share
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    ;   hosts allow = 192.168.1. 192.168.2. 127.
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    load printers = yes
    # you may wish to override the location of the printcap file
    ;   printcap name = /etc/printcap
    # on SystemV system setting printcap name to lpstat should allow
    # you to automatically obtain a printer list from the SystemV spool
    # system
    ;   printcap name = lpstat
    # It should not be necessary to specify the print system type unless
    # it is non-standard. Currently supported print systems include:
    # bsd, cups, sysv, plp, lprng, aix, hpux, qnx
    ;   printing = cups
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    ;  guest account = pcguest
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/log.%m
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
    # Use password server option only with security = server
    # The argument list may include:
    #   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    #   password server = *
    ;   password server = <NT-Server-Name>
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    ;   realm = MY_REALM
    # Backend to store user information in. New installations should
    # use either tdbsam or ldapsam. smbpasswd is available for backwards
    # compatibility. tdbsam requires no further configuration.
    ;   passdb backend = tdbsam
    # 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.
    # Note: Consider carefully the location in the configuration file of
    #       this line.  The included file is read at that point.
    ;   include = /usr/local/samba/lib/smb.conf.%m
    # Most people will find that this option gives better performance.
    # See the chapter 'Samba performance issues' in the Samba HOWTO Collection
    # and the manual pages for details.
    # You may want to add the following on a Linux system:
    #         SO_RCVBUF=8192 SO_SNDBUF=8192
    socket options = TCP_NODELAY 
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    ;   interfaces =
    # Browser Control Options:
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    ;   local master = no
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    ;   os level = 33
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    ;   domain master = yes
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    ;   preferred master = yes
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations.
    ;   domain logons = yes
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    ;   logon script = %m.bat
    # run a specific logon batch file per username
    ;   logon script = %U.bat
    # Where to store roving profiles (only for Win95 and WinNT)
    #        %L substitutes for this servers netbios name, %U is username
    #        You must uncomment the [Profiles] share below
    ;   logon path = \\%L\Profiles\%U
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    ;   wins support = yes
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    #	Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ;   wins server = w.x.y.z
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one	WINS Server on the network. The default is NO.
    ;   wins proxy = yes
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The default is NO.
    dns proxy = no
    restrict anonymous = no
    domain master = no
    preferred master = no
    max protocol = NT
    ldap ssl = No
    server signing = Auto
    # These scripts are used on a domain controller or stand-alone
    # machine to add or delete corresponding unix accounts
    ;  add user script = /usr/sbin/useradd %u
    ;  add group script = /usr/sbin/groupadd %g
    ;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
    ;  delete user script = /usr/sbin/userdel %u
    ;  delete user from group script = /usr/sbin/deluser %u %g
    ;  delete group script = /usr/sbin/groupdel %g
    #============================ Share Definitions ==============================
    comment = Home Directories
    browseable = no
    read only = no
    # Un-comment the following and create the netlogon directory for Domain Logons
    ; [netlogon]
    ;   comment = Network Logon Service
    ;   path = /usr/local/samba/lib/netlogon
    ;   guest ok = yes
    ;   writable = no
    ;   share modes = no
    # Un-comment the following to provide a specific roving profile share
    # the default is to use the user's home directory
    ;    path = /usr/local/samba/profiles
    ;    browseable = no
    ;    guest ok = yes
    # NOTE: If you have a BSD-style print system there is no need to
    # specifically define each individual printer
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    # Set public = yes to allow user 'guest account' to print
    guest ok = no
    printable = yes
    case sensitive = no
    guest ok = yes
    msdfs proxy = no
    hosts allow =
    path = /home/hannes/hannes
    comment = /home/hannes/hannes
    guest ok = yes
    wide links = no
    case sensitive = no
    msdfs proxy = no
    hosts allow =
    Das pingen des Windowsrechners funktioniert einwandfrei und er ist über den Linux Pc im Internet!

    Hoffe mir kann da jemand weiterhelfen ! :hilfe2:

    MFG Hannes
  2. Anzeige


    Wenn du mehr über Linux erfahren möchtest, dann solltest du dir mal folgende Shellkommandos anschauen.

    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. theton

    theton Bitmuncher

    Dabei seit:
    Berlin, Germany
    Versuchs mal mit

    smbmount \\<server-ip-hier>\<freigabename-hier> /mountpoint -o \
  4. #3 Bâshgob, 05.03.2006

    Bâshgob freies Radikal

    Dabei seit:
    Ich kenne das so: Der KDE-Konqueror kann nur SMB/CIFS wenn LISa installiert und konfiguriert ist. Zur Konfiguration hats einen Eintrag im KDE-Kontrollzentrum.

  5. theton

    theton Bitmuncher

    Dabei seit:
    Berlin, Germany
    smb:// geht im konqueror auch ohne LiSa, solange man die Workgroup und den Freigabe-Namen mit angebibt.
  6. #5 Bâshgob, 05.03.2006

    Bâshgob freies Radikal

    Dabei seit:
    Ähhh... Nö. Zumindest nicht unter NetBSD/KDE 3.4.3
  7. #6 Hannes3, 05.03.2006

    Hannes3 Doppel-As

    Dabei seit:
    Also hab das jetz so gelöst erstmal ! ich komme auf die freigaben des win Pcs wenn ich das so eingeben smb://PC name/freigabe!

    wenn ich es über die arbeitsgruppe versuchen und dann auf den Rechner klicke kommt immer noch dieser fehler ! Hat lisa auch nichts dran geändert bekomme dann immer einen Time out mitlerweie ! Naja solange es so schonmal läuft ist ja schonmal ein Anfang ! :)

archlinux smbclient problem

Die Seite wird geladen...

archlinux smbclient problem - Ähnliche Themen

  1. vbox - archlinux und IP

    vbox - archlinux und IP: Hallo Habe archlinux per architect (besserer Installer als dieser dumfug via chroot), funktioniert soweit fast alles. Das fast ist, wie bekomme...
  2. xdm-archlinux Frage

    xdm-archlinux Frage: Hallo Archlinux für amd64, incl. xdm-archlinux. Jetzt hab ich in der /etc/X11/xdm/archlinux/Xresources den Text fürs userlogin geändert....
  3. fehlerhaftes Grub nach ArchLinux-Installation

    fehlerhaftes Grub nach ArchLinux-Installation: Hey. Erstmal 'schuldigung, wenn dieses Thread hier falsch platziert sein sollte. Bin ganz neu in diesem Forum, und suche eine freundliche...
  4. ArchLinux Basic [Quick&Dirty]

    ArchLinux Basic [Quick&Dirty]: Inhaltsverzeichnis 1. Installation
  5. ArchLinux + TS154USB (ndiswrapper)

    ArchLinux + TS154USB (ndiswrapper): Morgen^^, oder ist es abend?!:D Also hier meine Frage: Ich will auf Arch umsteigen! Jetzt ein paar Fragen: 1) Unterstützt es dual cores 2)...
  1. Diese Seite verwendet Cookies um Inhalte zu personalisieren. Außerdem werden auch Cookies von Diensten Dritter gesetzt. Mit dem weiteren Aufenthalt akzeptierst du diesen Einsatz von Cookies.
    Information ausblenden