[Samba] Connecting to samba server from android TV Box

[Alex]

Hi, thanks so much for your help. This one was taken using tcpdump
directly, and readable in wireshark, although I'm not sure it has all
the info you need. I used the following:

# tcpdump -vvvni any -w ninkbox.pcap host 192.168.1.109

https://drive.google.com/open?id=1zPjZIfs1F73Xa0PJ-oEYYfuhj5N2SqyT

Here also is my smb.conf:

global]
        workgroup = NETDEV
        server string = Samba Server Version %v
        server min protocol = NT1
        netbios name = SAGE
        log file = /var/log/samba/log.%m
        log level = 4
        max log size = 500000
        security = user
        passdb backend = tdbsam
        unix password sync = yes
        lm announce = no
        lanman auth = yes
        ntlm auth = yes
        load printers = yes
        cups options = raw
[printers]
        comment = All Printers
        path = /var/spool/samba
        printable = yes
[dave]
        comment = Alex Home
        path = /home/alex
        read only = no
        browseable = yes
        guest ok = yes
[Videos]
        comment = Movies / TV Shows
        path = /home/alex/Videos
        read only = no
        browseable = yes
        guest ok = yes


On Thu, Jan 23, 2020 at 1:35 PM Jeremy Allison <jra at samba.org> wrote:
>
> On Thu, Jan 23, 2020 at 09:54:49AM -0500, Alex wrote:
> > Hi,
> > I've finally found time to get back to this and have created a
> > wireshark trace that can be found here:
> > https://drive.google.com/open?id=1uLps-uEpyHOiA5BjPMq33OmOASB4rjz7
>
> Unfortunately wireshark can open this but there's some
> encapsulation that prevents wireshark from decoding any
> of the packets as SMB.
>
> Can you load the file you want to send in wireshark,
> ensure it's being decoded correctly as SMB and re-upload
> please.
>
> I can't do anything with that file, sorry.
>
> Jeremy.
>
> > This trace includes from the time the device gets its IP from DHCP
> > until it reports a login failure.
> >
> > I had previously reported the Android box reports "mount fail" despite
> > being able to see the available shares on the SMB host. After the
> > wireshark trace, it appears after it completes the authentication with
> > the SMB server and gets the share list, it stops communicating over
> > the network and just reports "mount fail".
> >
> > Here's the last message produced in the logs for that host:
> >
> > [2020/01/23 09:49:58.409470,  4]
> > ../../auth/auth_log.c:740(log_successful_authz_event_human_readable)
> >   Successful AuthZ: [SMB,NTLMSSP] user [SAGE]\[dave]
> > [S-1-5-21-2538935071-3089878733-2078081524-1000] at [Thu, 23 Jan 2020
> > 09:49:58.4
> > 09463 EST] Remote host [ipv4:192.168.1.109:34726] local host
> > [ipv4:192.168.1.7:445]
> >   {"timestamp": "2020-01-23T09:49:58.409498-0500", "type":
> > "Authorization", "Authorization": {"version": {"major": 1, "minor":
> > 1}, "l
> > ocalAddress": "ipv4:192.168.1.7:445", "remoteAddress":
> > "ipv4:192.168.1.109:34726", "serviceDescription": "SMB", "authType":
> > "NTLMSSP"
> > , "domain": "SAGE", "account": "dave", "sid":
> > "S-1-5-21-2538935071-3089878733-2078081524-1000", "sessionId":
> > "de4cb5c7-1a70-48fc-a136
> > -3ffd1fc43fd6", "logonServer": "SAGE", "transportProtection": "SMB",
> > "accountFlags": "0x00000010"}}
> > [2020/01/23 09:49:58.409528,  3]
> > ../../source3/smbd/password.c:117(register_homes_share)
> >   Using static (or previously created) service for user 'dave'; path =
> > '/home/dave'
> >
> > Why would it succeed to be able to get the list of shares then be
> > unable to open them? It must be something about the information it's
> > already received.
> >
> > Thanks for any ideas. The information I reported previously on this is
> > printed below.
> >
> > On Fri, Jan 3, 2020 at 1:24 PM Jeremy Allison <jra at samba.org> wrote:
> > >
> > > On Fri, Jan 03, 2020 at 01:14:45PM -0500, Alex via samba wrote:
> > > > Hi, I have one of those TV boxes that can be used to connect to a
> > > > samba server to play media files on a TV but I can't get it to
> > > > connect. Their support is nonresponsive. I'm a relatively experienced
> > > > Linux user and have samba working with another media box on the same
> > > > network.
> > > >
> > > > The android media box with the problem is from Ninkbox and it's the N1
> > > > Max. The box says it's Android 9.0 using a RK3318 quad-core processor.
> > > > I can enter in the username and password for the share, and it appears
> > > > to login and display the list of available shares, but then returns
> > > > "mount fail" with no other indication as to what the problem could be.
> > >
> > > Get a wireshark trace on port 445 to see exactly what it is trying to do