[Samba] Cannot connect to Samab

John Serink john_serink at trimble.com
Fri Dec 23 14:19:26 UTC 2016


Comments below:

On Fri, Dec 23, 2016 at 8:56 PM, Reindl Harald via samba <
samba at lists.samba.org> wrote:

> first keep your mail on the list and only the list
>
> it makes me tired when people deliver denugging infos in pieces

Me too. :)

>   - what about "telnet host port"

A telnet server is not running. I think that's why you don't see it.

> - what makes you sure that a low level connection even works and no
> firefwall

jserinki7 jserink # iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A INPUT -i tap0 -j ACCEPT
-A FORWARD -j ACCEPT

This is the script I use to set everything up "IF" i'm going to run
windows7 in a VM:
#!/bin/bash
vde_switch --numports 4 --mod 777 --group users --tap tap0 -x -d
ip addr add dev tap0 192.168.100.1/24 brd 192.168.100.255
ip link set dev tap0 up
echo "1" > /proc/sys/net/ipv4/ip_forward
dnsmasq --log-queries --interface=tap0
#iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE
iptables -t nat -A POSTROUTING -o wlp3s0 -j MASQUERADE
iptables -A FORWARD -j ACCEPT
iptables -A INPUT -i tap0 -j ACCEPT

samba starts at bootup:
jserinki7 vde # rc-update show default
            alsasound | default
            bluetooth | default
           consolekit | default
               cronie | default
                cupsd | default
                 dbus | default
                  gpm | default
              hddtemp | default
                local | default
              metalog | default
          net.enp0s25 | default
             netmount | default
                samba | default
                 sshd | default



192.168.100.1 is the tap0 connection
jserinki7 jserink # ip addr show tap0
5: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN group default qlen 1000
    link/ether da:e5:47:2e:1b:f5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global tap0
       valid_lft forever preferred_lft forever
    inet6 fe80::d8e5:47ff:fe2e:1bf5/64 scope link
       valid_lft forever preferred_lft forever


or whatever device blocks the connection and as long that is not clear any
> other debugging is useless
>
So this error message "protocol negotiation failed: NT_STATUS_IO_TIMEOUT"
means something is blocking the connection?
Ok, good.

>
> and i still don't get why in the world don't you start with a default
> configuration and then add param by param so that you can see what is
> responsible when something stps to work
>
Like I said, it was previously working. This is what I started with which
used to work.
global]
workgroup = TNS
wins support = yes
hosts allow = 10. 127. 192.168.
socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 IPTOS_LOWDELAY
use sendfile = yes
log level = 0 passdb:0 auth:0
client signing = yes
passdb backend = smbpasswd
max protocol = smb2

[WINDOWSD]
path = /home/jserink/folders/InfraStructure/
valid users = jserink
read only = no
write list = jserink jserinkwin7
fstype = ext4




>
> Am 23.12.2016 um 13:34 schrieb John Serink:
>
>> jserinki7 jserink # netstat -lnptu
>> Active Internet connections (only servers)
>> Proto Recv-Q Send-Q Local Address           Foreign Address
>> State       PID/Program name
>> tcp        0      0 0.0.0.0:53 <http://0.0.0.0:53>
>>  0.0.0.0:*               LISTEN      3711/dnsmasq
>> tcp        0      0 127.0.0.1:631 <http://127.0.0.1:631>
>> 0.0.0.0:*               LISTEN      2849/cupsd
>> tcp        0      0 192.168.100.1:445 <http://192.168.100.1:445>
>> 0.0.0.0:*               LISTEN      27998/smbd
>> tcp        0      0 127.0.0.1:445 <http://127.0.0.1:445>
>> 0.0.0.0:*               LISTEN      27998/smbd
>> tcp        0      0 192.168.100.1:139 <http://192.168.100.1:139>
>> 0.0.0.0:*               LISTEN      27998/smbd
>> tcp        0      0 127.0.0.1:139 <http://127.0.0.1:139>
>> 0.0.0.0:*               LISTEN      27998/smbd
>> tcp        0      0 0.0.0.0:22222 <http://0.0.0.0:22222>
>> 0.0.0.0:*               LISTEN      2992/sshd
>> tcp        0      0 127.0.0.1:7634 <http://127.0.0.1:7634>
>>  0.0.0.0:*               LISTEN      2906/hddtemp
>> tcp6       0      0 :::53                   :::*
>>  LISTEN      3711/dnsmasq
>> tcp6       0      0 ::1:631                 :::*
>>  LISTEN      2849/cupsd
>> tcp6       0      0 :::22222                :::*
>>  LISTEN      2992/sshd
>> udp        0      0 0.0.0.0:5353 <http://0.0.0.0:5353>
>>  0.0.0.0:*                           6048/libpepflashpla
>> udp        0      0 0.0.0.0:53 <http://0.0.0.0:53>
>>  0.0.0.0:*                           3711/dnsmasq
>> udp        0      0 0.0.0.0:68 <http://0.0.0.0:68>
>>  0.0.0.0:*                           4102/dhcpcd
>> udp        0      0 192.168.100.255:137 <http://192.168.100.255:137>
>> 0.0.0.0:*                           28004/nmbd
>> udp        0      0 192.168.100.1:137 <http://192.168.100.1:137>
>> 0.0.0.0:*                           28004/nmbd
>> udp        0      0 0.0.0.0:137 <http://0.0.0.0:137>
>> 0.0.0.0:*                           28004/nmbd
>> udp        0      0 192.168.100.255:138 <http://192.168.100.255:138>
>> 0.0.0.0:*                           28004/nmbd
>> udp        0      0 192.168.100.1:138 <http://192.168.100.1:138>
>> 0.0.0.0:*                           28004/nmbd
>> udp        0      0 0.0.0.0:138 <http://0.0.0.0:138>
>> 0.0.0.0:*                           28004/nmbd
>> udp6       0      0 :::53                   :::*
>>        3711/dnsmasq
>>
>>
>> On Fri, Dec 23, 2016 at 6:57 PM, Reindl Harald via samba
>> <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote:
>>
>>
>>
>>     Am 23.12.2016 um 05:29 schrieb John Serink via samba:
>>
>>         I then tried from a bash prompt and get his:
>>         jserinki7 jserink # smbclient -L 192.168.100.1 -U jserink -m SMB2
>>         Enter jserink's password:
>>         protocol negotiation failed: NT_STATUS_IO_TIMEOUT
>>         hosts allow = 192.168.100. 127.0.0.
>>         interfaces = 192.168.100.1/24 <http://192.168.100.1/24>
>>         127.0.0.1/24 <http://127.0.0.1/24>
>>         bind interfaces only = yes
>>
>>
>>     why in teh world are you *starting* with such nonsense
>>     configurations you obviosuly don't understand (otherwise you won't
>>     list CIDR masks in interface settings)?
>>
>>     * first you srtart with looking if the service is listening correctly
>>     * second you try to connect with "telnet host port"
>>     * and AFTER thatis successful you have a point to touch a native
>> client
>>
>>     so what says "netstat --numeric-hosts --numeric-ports --programs -u
>>     -t -l" on the server?
>>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba




-- 
John Edward Serink
Product Applications Engineer,
Advanced Positioning
Trimble Navigation Singapore PTE Ltd.
80 Marine Parade Road,
Co. Reg. No. 199204958W
#22-06 Parkway Parade
Singapore 449269
Tel 65-6348-2212
Fax 65-6348-2232
DID 65-6348-2178
HP  65-9129-4250
Skype: johnserink


More information about the samba mailing list