Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Samba Bug? Cant 't connect to Windows Network Share

  1. #1

    Default Samba Bug? Cant 't connect to Windows Network Share

    Good Morning,
    I am running OpenSuse 13.1 XFCE Desktop. I am trying to connect to Network share that has been accessible to any Windows/Linux box that i have installed. I have been spending some tine doing some Google searches to resolve the issue.

    smbclient --list 192.168.1.80 -d10
    INFO: Current debug levels:
    all: 10
    tdb: 10
    printdrivers: 10
    lanman: 10
    smb: 10
    rpc_parse: 10
    rpc_srv: 10
    rpc_cli: 10
    passdb: 10
    sam: 10
    auth: 10
    winbind: 10
    vfs: 10
    idmap: 10
    quota: 10
    acls: 10
    locking: 10
    msdfs: 10
    dmapi: 10
    registry: 10
    scavenger: 10
    dns: 10
    ldb: 10
    lp_load_ex: refreshing parameters
    Initialising global parameters
    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    INFO: Current debug levels:
    all: 10
    tdb: 10
    printdrivers: 10
    lanman: 10
    smb: 10
    rpc_parse: 10
    rpc_srv: 10
    rpc_cli: 10
    passdb: 10
    sam: 10
    auth: 10
    winbind: 10
    vfs: 10
    idmap: 10
    quota: 10
    acls: 10
    locking: 10
    msdfs: 10
    dmapi: 10
    registry: 10
    scavenger: 10
    dns: 10
    ldb: 10
    params.cm_process() - Processing configuration file "/etc/samba/smb.conf"
    Processing section "[global]"
    doing parameter workgroup = HOME
    doing parameter name resolve order = bcast host lmhosts wins
    doing parameter netbios name = linux-7ed5
    doing parameter passdb backend = tdbsam
    doing parameter printing = cups
    doing parameter printcap name = cups
    doing parameter printcap cache time = 750
    doing parameter cups options = raw
    doing parameter map to guest = Bad User
    doing parameter include = /etc/samba/dhcp.conf
    params.cm_process() - Processing configuration file "/etc/samba/dhcp.conf"
    doing parameter usershare allow guests = Yes
    pm_process() returned Yes
    lp_servicenumber: couldn't find homes
    added interface enp2s0 ip=192.168.1.175 bcast=192.168.1.255 netmask=255.255.255.0
    Netbios name list:-
    my_netbios_names[0]="LINUX-7ED5"
    Client started (version 4.1.6-3.18.1-3208-SUSE-oS13.1-x86_64).
    Enter WC2L's password:
    Connecting to 192.168.1.80 at port 445
    Connecting to 192.168.1.80 at port 139
    Socket options:
    SO_KEEPALIVE = 0
    SO_REUSEADDR = 0
    SO_BROADCAST = 0
    TCP_NODELAY = 1
    TCP_KEEPCNT = 9
    TCP_KEEPIDLE = 7200
    TCP_KEEPINTVL = 75
    IPTOS_LOWDELAY = 0
    IPTOS_THROUGHPUT = 0
    SO_REUSEPORT = 0
    SO_SNDBUF = 23400
    SO_RCVBUF = 93120
    SO_SNDLOWAT = 1
    SO_RCVLOWAT = 1
    SO_SNDTIMEO = 0
    SO_RCVTIMEO = 0
    TCP_QUICKACK = 1
    TCP_DEFER_ACCEPT = 0
    session request ok
    convert_string_talloc: Conversion error: Incomplete multibyte sequence()
    Conversion error: Incomplete multibyte sequence()
    protocol negotiation failed: NT_STATUS_INVALID_PARAMETER

    Here is my smb.conf
    # smb.conf is the main Samba configuration file. You find a full commented
    # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
    # samba-doc package is installed.
    [global]
    workgroup = HOME
    name resolve order = bcast host lmhosts wins
    netbios name = linux-7ed5
    passdb backend = tdbsam
    printing = cups
    printcap name = cups
    printcap cache time = 750
    cups options = raw
    map to guest = Bad User
    include = /etc/samba/dhcp.conf
    # logon path = \\%L\profiles\.msprofile
    # logon home = \\%L\%U\.9xprofile
    # logon drive = P:
    usershare allow guests = Yes
    [homes]
    comment = Home Directories
    valid users = %S, %D%w%S
    browseable = No
    read only = No
    inherit acls = Yes
    [profiles]
    comment = Network Profiles Service
    path = %H
    read only = No
    store dos attributes = Yes
    create mask = 0600
    directory mask = 0700
    [users]
    comment = All users
    path = /home
    read only = No
    inherit acls = Yes
    veto files = /aquota.user/groups/shares/
    [groups]
    comment = All groups
    path = /home/groups
    read only = No
    inherit acls = Yes
    [printers]
    comment = All Printers
    path = /var/tmp
    printable = Yes
    create mask = 0600
    browseable = No
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    write list = @ntadmin root
    force group = ntadmin
    create mask = 0664

    Any ideas how to resolve this?
    TNX Will

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    9,467
    Blog Entries
    1

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    Quote Originally Posted by wliporace View Post
    Good Morning,
    I am running OpenSuse 13.1 XFCE Desktop. I am trying to connect to Network share that has been accessible to any Windows/Linux box that i have installed. I have been spending some tine doing some Google searches to resolve the issue.

    smbclient --list 192.168.1.80 -d10
    INFO: Current debug levels:
    all: 10
    tdb: 10
    printdrivers: 10
    lanman: 10
    smb: 10
    rpc_parse: 10
    rpc_srv: 10
    rpc_cli: 10
    passdb: 10
    sam: 10
    auth: 10
    winbind: 10
    vfs: 10
    idmap: 10
    quota: 10
    acls: 10
    locking: 10
    msdfs: 10
    dmapi: 10
    registry: 10
    scavenger: 10
    dns: 10
    ldb: 10
    lp_load_ex: refreshing parameters
    Initialising global parameters
    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    INFO: Current debug levels:
    all: 10
    tdb: 10
    printdrivers: 10
    lanman: 10
    smb: 10
    rpc_parse: 10
    rpc_srv: 10
    rpc_cli: 10
    passdb: 10
    sam: 10
    auth: 10
    winbind: 10
    vfs: 10
    idmap: 10
    quota: 10
    acls: 10
    locking: 10
    msdfs: 10
    dmapi: 10
    registry: 10
    scavenger: 10
    dns: 10
    ldb: 10
    params.cm_process() - Processing configuration file "/etc/samba/smb.conf"
    Processing section "[global]"
    doing parameter workgroup = HOME
    doing parameter name resolve order = bcast host lmhosts wins
    doing parameter netbios name = linux-7ed5
    doing parameter passdb backend = tdbsam
    doing parameter printing = cups
    doing parameter printcap name = cups
    doing parameter printcap cache time = 750
    doing parameter cups options = raw
    doing parameter map to guest = Bad User
    doing parameter include = /etc/samba/dhcp.conf
    params.cm_process() - Processing configuration file "/etc/samba/dhcp.conf"
    doing parameter usershare allow guests = Yes
    pm_process() returned Yes
    lp_servicenumber: couldn't find homes
    added interface enp2s0 ip=192.168.1.175 bcast=192.168.1.255 netmask=255.255.255.0
    Netbios name list:-
    my_netbios_names[0]="LINUX-7ED5"
    Client started (version 4.1.6-3.18.1-3208-SUSE-oS13.1-x86_64).
    Enter WC2L's password:
    Connecting to 192.168.1.80 at port 445
    Connecting to 192.168.1.80 at port 139
    Socket options:
    SO_KEEPALIVE = 0
    SO_REUSEADDR = 0
    SO_BROADCAST = 0
    TCP_NODELAY = 1
    TCP_KEEPCNT = 9
    TCP_KEEPIDLE = 7200
    TCP_KEEPINTVL = 75
    IPTOS_LOWDELAY = 0
    IPTOS_THROUGHPUT = 0
    SO_REUSEPORT = 0
    SO_SNDBUF = 23400
    SO_RCVBUF = 93120
    SO_SNDLOWAT = 1
    SO_RCVLOWAT = 1
    SO_SNDTIMEO = 0
    SO_RCVTIMEO = 0
    TCP_QUICKACK = 1
    TCP_DEFER_ACCEPT = 0
    session request ok
    convert_string_talloc: Conversion error: Incomplete multibyte sequence()
    Conversion error: Incomplete multibyte sequence()
    protocol negotiation failed: NT_STATUS_INVALID_PARAMETER

    Here is my smb.conf
    # smb.conf is the main Samba configuration file. You find a full commented
    # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
    # samba-doc package is installed.
    [global]
    workgroup = HOME
    name resolve order = bcast host lmhosts wins
    netbios name = linux-7ed5
    passdb backend = tdbsam
    printing = cups
    printcap name = cups
    printcap cache time = 750
    cups options = raw
    map to guest = Bad User
    include = /etc/samba/dhcp.conf
    # logon path = \\%L\profiles\.msprofile
    # logon home = \\%L\%U\.9xprofile
    # logon drive = P:
    usershare allow guests = Yes
    [homes]
    comment = Home Directories
    valid users = %S, %D%w%S
    browseable = No
    read only = No
    inherit acls = Yes
    [profiles]
    comment = Network Profiles Service
    path = %H
    read only = No
    store dos attributes = Yes
    create mask = 0600
    directory mask = 0700
    [users]
    comment = All users
    path = /home
    read only = No
    inherit acls = Yes
    veto files = /aquota.user/groups/shares/
    [groups]
    comment = All groups
    path = /home/groups
    read only = No
    inherit acls = Yes
    [printers]
    comment = All Printers
    path = /var/tmp
    printable = Yes
    create mask = 0600
    browseable = No
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    write list = @ntadmin root
    force group = ntadmin
    create mask = 0664

    Any ideas how to resolve this?
    TNX Will
    First, although your post seems reasonably clear to me, it's proper form to post data in "CODE" tags (the hash button in your text editor if you're using the Forums web client).

    I'm sure you need to provide more concrete information about your problem, eg
    - What command and/or app client are you using to connect to your Network Share?
    - What was the response if you weren't successful (post exact error returned)?

    Some other minor things I notice in your smb.conf
    - You list bcasts first in order of name resolution. Although it's possible to do this, most Admins list it last to minimize noise on the network.
    - Don't know if I'm reading this right, but you might be permitting guests to connect when it looks like you are serving Users' Home directories?

    TSU

  3. #3

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    Whoops. I was trying to include most things......
    The share is basically a HD on a NIC. Been using it forever it seems. This is the first time I have had an issue connecting to it No real "home user directories". The workgroup is called home.

    If I open the file manager and type smb://192.168.1.80/Hdd_a, I get Failed to open"File System". Failed to mount Windows Share: Connection timed out.

    File Manager - Super User and Dolphin:
    smb://192.168.1.80/hdd_a
    Timeout on server 192.168.1.80

    sudo mount -t cifs //192.168.1.80/hdd_a
    mount: can't find //192.168.1.80/hdd_a in /etc/fstab

    Not sure what to do from here...

  4. #4
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    18,961
    Blog Entries
    1

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    Quote Originally Posted by wliporace View Post
    Whoops. I was trying to include most things......
    The share is basically a HD on a NIC. Been using it forever it seems. This is the first time I have had an issue connecting to it No real "home user directories". The workgroup is called home.

    If I open the file manager and type smb://192.168.1.80/Hdd_a, I get Failed to open"File System". Failed to mount Windows Share: Connection timed out.
    Starting from basics, can you ping the address?
    Code:
    ping 192.168.1.80

  5. #5

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    Yes I can ping the device. I can even browse to the web interface. I have a Linux Mint 15 box that I can get to it from.

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    18,961
    Blog Entries
    1

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    Quote Originally Posted by wliporace View Post
    Yes I can ping the device. I can even browse to the web interface. I have a Linux Mint 15 box that I can get to it from.
    What response does the following give?
    Code:
    smbclient -L 192.168.1.80 -N

  7. #7
    Join Date
    Nov 2009
    Location
    ND, USA
    Posts
    1,131

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    On 4/19/2014 9:16 PM, deano ferrari wrote:
    >
    > wliporace;2638028 Wrote:
    >> Yes I can ping the device. I can even browse to the web interface. I
    >> have a Linux Mint 15 box that I can get to it from.

    > What response does the following give?
    >
    > Code:
    > --------------------
    > smbclient -L 192.168.1.80 -N
    > --------------------
    >
    >

    Wilporace;

    In addition to above make sure that Samba Server, Netbios server and Samba client are all allowed services through the
    firewall:

    YaST>Security and Users>Firewall>Allowed Services

    Make sure smb and nmb are both started:
    [code]
    systemctl status smb.service
    systemctl status nmb.service
    [code]

    ( I suppose you do not really need smb for just the client, but you indicate shares in your smb.conf and need smb for
    those.)

    If these two services are not started then you can start them with:
    [code]
    su -
    systemctl start smb.service
    systemctl start nmb.service
    exit
    [code]
    and then enable them at boot time with:
    Code:
    systemctl enable smb.service
    systemctl enable nmb.service
    To mount a cifs share you will need the full mount command. See:
    http://swerdna.dyndns.org/susesambacifs.html
    for a good explanation. ( This site is often down so if you cannot reach it post back here.)

    --
    P.V.


  8. #8

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    To answer the first question:

    Code:
    ping 192.168.1.80
    PING 192.168.1.80 (192.168.1.80) 56(84) bytes of data.
    64 bytes from 192.168.1.80: icmp_seq=1 ttl=64 time=1.49 ms
    64 bytes from 192.168.1.80: icmp_seq=2 ttl=64 time=0.258 ms
    64 bytes from 192.168.1.80: icmp_seq=3 ttl=64 time=0.260 ms
    64 bytes from 192.168.1.80: icmp_seq=4 ttl=64 time=0.263 ms
    64 bytes from 192.168.1.80: icmp_seq=5 ttl=64 time=0.276 ms
    64 bytes from 192.168.1.80: icmp_seq=6 ttl=64 time=0.266 ms
    --- 192.168.1.80 ping statistics ---
    6 packets transmitted, 6 received, 0% packet loss, time 5001ms
    I currently have the firewall disabled and I have the services enabled. I finally figured out that I needed to create a mount point on my PC. /mnt/hdd_a then issue the command:
    Code:
    sudo mount -t cifs -o guest //192.168.1.80/hdd_a /mnt/hdd_a
    This allowed me to mount the directory. My other question then becomes, Why can't I just browse to the area like I have always done? Why do I have to mount it to see it?

    TNX Will

  9. #9
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    9,467
    Blog Entries
    1

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    Quote Originally Posted by wliporace View Post
    To answer the first question:

    Code:
    ping 192.168.1.80
    PING 192.168.1.80 (192.168.1.80) 56(84) bytes of data.
    64 bytes from 192.168.1.80: icmp_seq=1 ttl=64 time=1.49 ms
    64 bytes from 192.168.1.80: icmp_seq=2 ttl=64 time=0.258 ms
    64 bytes from 192.168.1.80: icmp_seq=3 ttl=64 time=0.260 ms
    64 bytes from 192.168.1.80: icmp_seq=4 ttl=64 time=0.263 ms
    64 bytes from 192.168.1.80: icmp_seq=5 ttl=64 time=0.276 ms
    64 bytes from 192.168.1.80: icmp_seq=6 ttl=64 time=0.266 ms
    --- 192.168.1.80 ping statistics ---
    6 packets transmitted, 6 received, 0% packet loss, time 5001ms
    I currently have the firewall disabled and I have the services enabled. I finally figured out that I needed to create a mount point on my PC. /mnt/hdd_a then issue the command:
    Code:
    sudo mount -t cifs -o guest //192.168.1.80/hdd_a /mnt/hdd_a
    This allowed me to mount the directory. My other question then becomes, Why can't I just browse to the area like I have always done? Why do I have to mount it to see it?

    TNX Will
    Glad to hear you solved your mount problem.

    From what I've seen, you can mount manually (the method you're using) or Desktops seem to have the ability to dynamically discover and mount using some other method and using a supported protocol (eg smb, ftp, http, etc). The requirements to browse network resources are strict... You need to be a member of the same workgroup or domain to "see" resources, and you need appropriate permissions to access (and maybe see) the resource.

    When you talk about browsing network resources (typically network shares), you can test using a web browser because browsers today typically understand all most used protocols and often return usable error messages. You can also test using a command line tool like curl (there are others (deano suggested one).

    Also, if you're not running a domain, a workgroup can suffer anomalies, especially for a machine first booting up into the network when it somehow doesn't know which machine in the workgroup is the browse master.

    HTH,
    TSU

  10. #10

    Default Re: Samba Bug? Cant 't connect to Windows Network Share

    Did you try to add the following line to the the /etc/samba/smb.conf file:
    Code:
    wins support = yes

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •