Re: [Samba] Can't connect to my NAS after samba 4 update

[Richard llom]

Still have this issue, any help is appreciated.

Richard llom wrote:
> This is the output with debug lv 10, hth:
>
> [richard@chakra ~]$ smbclient --list linkstation -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.c:pm_process() - Processing configuration file
> "/etc/samba/smb.conf" Processing section "[global]"
> doing parameter workgroup = MYGROUP
> doing parameter server string = Samba Server
> doing parameter printcap name = /etc/printcap
> doing parameter load printers = yes
> doing parameter log file = /var/log/samba/%m.log
> doing parameter max log size = 50
> doing parameter security = user
> doing parameter dns proxy = no
> pm_process() returned Yes
> lp_servicenumber: couldn't find homes
> added interface wlp0s26f7u2 ip=192.168.22.46 bcast=192.168.22.255
> netmask=255.255.255.0
> Netbios name list:-
> my_netbios_names[0]="CHAKRA"
> Client started (version 4.1.1).
> Enter richard's password:
> Opening cache file at /var/cache/samba/gencache.tdb
> tdb(/var/cache/samba/gencache.tdb): tdb_open_ex: could not open file
> /var/cache/samba/gencache.tdb: Keine Berechtigung
> gencache_init: Opening cache file /var/cache/samba/gencache.tdb read-only.
> Opening cache file at /var/cache/samba/gencache_notrans.tdb
> sitename_fetch: No stored sitename for
> internal_resolve_name: looking up linkstation#20 (sitename (null))
> no entry for linkstation#20 found.
> resolve_lmhosts: Attempting lmhosts lookup for name linkstation<0x20>
> resolve_lmhosts: Attempting lmhosts lookup for name linkstation<0x20>
> startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was Datei
> oder Verzeichnis nicht gefunden
> resolve_wins: WINS server resolution selected and no WINS servers listed.
> resolve_hosts: Attempting host lookup for name linkstation<0x20>
> remove_duplicate_addrs2: looking for duplicate address/port pairs
> namecache_store: storing 1 address for linkstation#20: 192.168.22.2
> Adding cache entry with key=[NBT/LINKSTATION#20] and timeout=[Do Dez 12
> 00:18:03 2013 CET] (660 seconds ahead)
> internal_resolve_name: returning 1 addresses: 192.168.22.2:0
> Connecting to 192.168.22.2 at port 445
> Connecting to 192.168.22.2 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 = 87380
> 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
>
>
> Richard llom wrote:
>> I updated my system to samba 4:
>> [richard@chakra ~]$ uname -a
>> Linux chakra 3.10.18-1-CHAKRA #1 SMP PREEMPT Sat Nov 9 20:18:15 UTC 2013
>> x86_64 GNU/Linux
>> [richard@chakra ~]$ samba --version
>> Version 4.1.1
>> [richard@chakra ~]$ smbclient --version
>> Version 4.1.1
>>
>> And now all of sudden I cannot any longer connect to my NAS, this is the
>> message I get in console:
>> [richard@chakra ~]$ smbclient --list linkstation
>> Enter richard's password:
>> Conversion error: Incomplete multibyte sequence()
>> protocol negotiation failed: NT_STATUS_INVALID_PARAMETER
>>
>> Note that I do not need any credentials to connect to my NAS.
>> Before it just worked.
>>
>> Any help is appreciated, tia.
>> richard

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

[Chris Rowson]

Check DNS. Can you resolve linkstation?

[Richard llom]

Chris Rowson wrote:
> Check DNS. Can you resolve linkstation?

[richard@chakra ~]$ host linkstation
linkstation.Linksys_domain has address 192.168.22.2
[richard@chakra ~]$ ping linkstation
PING linkstation.Linksys_domain (192.168.22.2) 56(84) bytes of data.
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=1 ttl=64
time=75.3 ms

looks fine to me?

[Tiemen Ruiten]

Do you know the samba version on your NAS? You might be running into
this bug: https://bugzilla.redhat.com/show_bug.cgi?id=905996

(BTW, first hit on google for 'Conversion error: Incomplete multibyte
sequence NT_STATUS_INVALID_PARAMETER')

On 10-12-13 01:02, Richard llom wrote:
> Hello,

> I updated my system to samba 4:
> [richard@chakra ~]$ uname -a
> Linux chakra 3.10.18-1-CHAKRA #1 SMP PREEMPT Sat Nov 9 20:18:15 UTC 2013
> x86_64 GNU/Linux
> [richard@chakra ~]$ samba --version
> Version 4.1.1
> [richard@chakra ~]$ smbclient --version
> Version 4.1.1
>
> And now all of sudden I cannot any longer connect to my NAS, this is the
> message I get in console:
> [richard@chakra ~]$ smbclient --list linkstation
> Enter richard's password:
> Conversion error: Incomplete multibyte sequence()
> protocol negotiation failed: NT_STATUS_INVALID_PARAMETER
>
> Note that I do not need any credentials to connect to my NAS.
> Before it just worked.
>

> Any help is appreciated, tia.
> richard
>

[Richard llom]

Tiemen Ruiten wrote:
> Do you know the samba version on your NAS? You might be running into
> this bug: https://bugzilla.redhat.com/show_bug.cgi?id=905996
>

My NAS is actually a commercial product (Buffalo Linkstation). I doubt they
are running SAMBA on it. But if they do, they didn't deliver license file
with it! :-)

> (BTW, first hit on google for 'Conversion error: Incomplete multibyte
> sequence NT_STATUS_INVALID_PARAMETER')
>

I tried searching, too. But didn't come up with anything which seems
related.

cheers
richard

> On 10-12-13 01:02, Richard llom wrote:
>> Hello,
>> I updated my system to samba 4:
>> [richard@chakra ~]$ uname -a
>> Linux chakra 3.10.18-1-CHAKRA #1 SMP PREEMPT Sat Nov 9 20:18:15 UTC 2013
>> x86_64 GNU/Linux
>> [richard@chakra ~]$ samba --version
>> Version 4.1.1
>> [richard@chakra ~]$ smbclient --version
>> Version 4.1.1
>>
>> And now all of sudden I cannot any longer connect to my NAS, this is the
>> message I get in console:
>> [richard@chakra ~]$ smbclient --list linkstation
>> Enter richard's password:
>> Conversion error: Incomplete multibyte sequence()
>> protocol negotiation failed: NT_STATUS_INVALID_PARAMETER
>>
>> Note that I do not need any credentials to connect to my NAS.
>> Before it just worked.

[Tiemen Ruiten]

Again, first hit for 'buffalo linkstation samba version':

http://buffalo.nas-central.org/wiki/Samba_-_a_Windows-readable_file_share

Down at the end of that page, you'll find this link:

http://buffalo.nas-central.org/wiki/FAQ#What_version_of_Samba_does_the_stock_LinkStation_come_with.3F_Netatalk.3F_thttpd.3F_WU-FTPD.3F_ProFTPD.3F

[Richard llom]

Tiemen Ruiten wrote:
> Again, first hit for 'buffalo linkstation samba version':
>
> http://buffalo.nas-central.org/wiki/Samba_-_a_Windows-readable_file_share
>
> Down at the end of that page, you'll find this link:
>
> http://buffalo.nas-central.org/wiki/FAQ#What_version_of_Samba_does_the_stock_LinkStation_come_with.3F_Netatalk.3F_thttpd.3F_WU-FTPD.3F_ProFTPD.3F
>

Uhmm, oops ... Totally didn't thought of this. Never expected my linkstation
to run on linux, seems like I missed something.

So according to the wiki, the samba version is:
Samba 2.2.8a-ja-1.1-beta5

Which then indeed leads to the redhat bug.
Good in a sense that I'm not alone, bad in the sense that this can't be
fixed easily... :-/

So I'll watch this bug.


Tiemen, thanks a lot for your research! (Should really have come up with
this my self! :-[ )
richard

> On 19-12-13 00:07, Richard llom wrote:
>> Tiemen Ruiten wrote:
>>> Do you know the samba version on your NAS? You might be running into
>>> this bug: https://bugzilla.redhat.com/show_bug.cgi?id=905996
>>>
>> My NAS is actually a commercial product (Buffalo Linkstation). I doubt
>> they are running SAMBA on it. But if they do, they didn't deliver license
>> file with it! :-)
>>
>>> (BTW, first hit on google for 'Conversion error: Incomplete multibyte
>>> sequence NT_STATUS_INVALID_PARAMETER')
>>>
>> I tried searching, too. But didn't come up with anything which seems
>> related.

[Ricky Nance]

Just a side note, but 73 ms ping inside your lan isn't good... that to me
would indicate a problem with a nic/nic driver/switch/ or cable. It may be
a different issue, but I'd definitely check out that... how does your ping
to other devices in your network look? Do all of them ping that high to
your NAS? Most if not all LAN's I have dealt with are less than a 3 ms ping
from edge to edge.

ping raspberrypi

Pinging raspberrypi [192.168.1.100] with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<1ms TTL=64


--Ricky

[Tiemen Ruiten]

On 12/19/13 01:13, Richard llom wrote:
> Tiemen Ruiten wrote:
>> Again, first hit for 'buffalo linkstation samba version':
>>
>> http://buffalo.nas-central.org/wiki/Samba_-_a_Windows-readable_file_share
>>
>> Down at the end of that page, you'll find this link:
>>
>> http://buffalo.nas-central.org/wiki/FAQ#What_version_of_Samba_does_the_stock_LinkStation_come_with.3F_Netatalk.3F_thttpd.3F_WU-FTPD.3F_ProFTPD.3F
>>
> Uhmm, oops ... Totally didn't thought of this. Never expected my linkstation
> to run on linux, seems like I missed something.
>
> So according to the wiki, the samba version is:
> Samba 2.2.8a-ja-1.1-beta5
>
> Which then indeed leads to the redhat bug.
> Good in a sense that I'm not alone, bad in the sense that this can't be
> fixed easily... :-/
>
> So I'll watch this bug.
>

Well, the page I linked to is part of a site dedicated to hacking the
Buffalo Linkstation. From a quick look at the frontpage, it appears to
be possible to flash the firmware:

"This community-driven site is geared towards Buffalo Technology/Melco's
amazing Network-attached storage (NAS) devices called the Linkstation,
Kurobox and Terastation. Notice that this page is totally unrelated to
the producer. There are currently several models available, so click on
the links on the right to find out which variant you have.
There are several custom firmwares such as Debian, Gentoo, Foonas, and
Openlink that will give you unix shell access to your device."

That should come with a newer version of samba.
Sounds better to me than waiting for someone else to fix that issue.

[steve]

On Thu, 2013-12-19 at 00:11 +0100, Tiemen Ruiten wrote:
> Again, first hit for 'buffalo linkstation samba version':
>
> http://buffalo.nas-central.org/wiki/Samba_-_a_Windows-readable_file_share

Hi
Mmm. This suggests that you have to install it yourself. . .

>
> Down at the end of that page, you'll find this link:
>
> http://buffalo.nas-central.org/wiki/FAQ#What_version_of_Samba_does_the_stock_LinkStation_come_with.3F_Netatalk.3F_thttpd.3F_WU-FTPD.3F_ProFTPD.3F
>

. . . but this suggests it's already installed

The first link also suggests that you have root access and a terminal,
so can you post the output of
cat /etc/samba/smb.conf
and if nothing
cat /etc/smb.conf

or have a poke around for evidence of any smb.conf?
Cheers,
Steve

[steve]

On Thu, 2013-12-19 at 01:13 +0100, Richard llom wrote:
> Tiemen Ruiten wrote:
> > Again, first hit for 'buffalo linkstation samba version':
> >
> > http://buffalo.nas-central.org/wiki/Samba_-_a_Windows-readable_file_share
> >

> > Down at the end of that page, you'll find this link:
> >
> > http://buffalo.nas-central.org/wiki/FAQ#What_version_of_Samba_does_the_stock_LinkStation_come_with.3F_Netatalk.3F_thttpd.3F_WU-FTPD.3F_ProFTPD.3F
> >

> Uhmm, oops ... Totally didn't thought of this. Never expected my linkstation
> to run on linux, seems like I missed something.

Hi
(Sorry, I'm out of sync with the posts.)

>
> So according to the wiki, the samba version is:
> Samba 2.2.8a-ja-1.1-beta5
>
> Which then indeed leads to the redhat bug.
> Good in a sense that I'm not alone, bad in the sense that this can't be
> fixed easily... :-/
>
> So I'll watch this bug.

It seems as though the OP has root access so we should be able to
install a better samba version. Pls. see my earlier reply.

[Richard llom]

Ricky Nance wrote:
> Just a side note, but 73 ms ping inside your lan isn't good... that to me
> would indicate a problem with a nic/nic driver/switch/ or cable. It may be
> a different issue, but I'd definitely check out that... how does your ping
> to other devices in your network look? Do all of them ping that high to
> your NAS? Most if not all LAN's I have dealt with are less than a 3 ms
> ping from edge to edge.
>
> ping raspberrypi
>
> Pinging raspberrypi [192.168.1.100] with 32 bytes of data:
> Reply from 192.168.1.100: bytes=32 time<1ms TTL=64
>

Thanks for your concern, but I think this was just coincidentally:

[richard@chakra ~]$ ping linkstation
PING linkstation.Linksys_domain (192.168.22.2) 56(84) bytes of data.
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=1 ttl=64

time=15.8 ms
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=2 ttl=64
time=2.29 ms
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=3 ttl=64
time=1.39 ms
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=4 ttl=64
time=1.35 ms
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=5 ttl=64
time=1.25 ms
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=6 ttl=64
time=1.82 ms
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=7 ttl=64
time=1.41 ms
64 bytes from LINKSTATION.Linksys_domain (192.168.22.2): icmp_seq=8 ttl=64
time=1.41 ms
^C
--- linkstation.Linksys_domain ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7012ms
rtt min/avg/max/mdev = 1.256/3.354/15.890/4.749 ms

richard


PS:
Pls don't send copies to email, I'm reading this group via gmane.

[Richard llom]

Tiemen Ruiten wrote:

> On 12/19/13 01:13, Richard llom wrote:
>> Tiemen Ruiten wrote:
>> Uhmm, oops ... Totally didn't thought of this. Never expected my
>> linkstation to run on linux, seems like I missed something.
>>

>> So according to the wiki, the samba version is:
>> Samba 2.2.8a-ja-1.1-beta5
>>
>> Which then indeed leads to the redhat bug.
>> Good in a sense that I'm not alone, bad in the sense that this can't be
>> fixed easily... :-/
>>
>> So I'll watch this bug.
>>

> Well, the page I linked to is part of a site dedicated to hacking the
> Buffalo Linkstation. From a quick look at the frontpage, it appears to
> be possible to flash the firmware:
>

Yes, but this will require some carefully read-in, since I don't want to
brick my NAS or my current setup. I will do this on the weekend or during
holidays.

>
> That should come with a newer version of samba.
> Sounds better to me than waiting for someone else to fix that issue.
>

True.

[Richard llom]

steve wrote:

> On Thu, 2013-12-19 at 00:11 +0100, Tiemen Ruiten wrote:
>> Again, first hit for 'buffalo linkstation samba version':
>>
>> http://buffalo.nas-central.org/wiki/Samba_-_a_Windows-readable_file_share
>

> Mmm. This suggests that you have to install it yourself. . .
>

Yes, I thought so, too at first. :-)

>>
>> Down at the end of that page, you'll find this link:
>>
>> http://buffalo.nas-central.org/wiki/FAQ#What_version_of_Samba_does_the_stock_LinkStation_come_with.3F_Netatalk.3F_thttpd.3F_WU-FTPD.3F_ProFTPD.3F
>>

> . . . but this suggests it's already installed
>
> The first link also suggests that you have root access and a terminal
>

Hmm? Sorry, I don't see this. The installation part refers to your
linkstation, when you have it already hacked. But I'm not at this stage (yet
:-).

I'll look into this subject, but it will take some time...

> so can you post the output of
> cat /etc/samba/smb.conf
> and if nothing
> cat /etc/smb.conf
>
> or have a poke around for evidence of any smb.conf?
> Cheers,
> Steve

cheers
richard

[steve]

On Thu, 2013-12-19 at 23:15 +0100, Richard llom wrote:
> steve wrote:
> > On Thu, 2013-12-19 at 00:11 +0100, Tiemen Ruiten wrote:
> >> Again, first hit for 'buffalo linkstation samba version':
> >>
> >> http://buffalo.nas-central.org/wiki/Samba_-_a_Windows-readable_file_share
> >
> > Mmm. This suggests that you have to install it yourself. . .
> >
> Yes, I thought so, too at first. :-)
>
> >>
> >> Down at the end of that page, you'll find this link:
> >>
> >> http://buffalo.nas-central.org/wiki/FAQ#What_version_of_Samba_does_the_stock_LinkStation_come_with.3F_Netatalk.3F_thttpd.3F_WU-FTPD.3F_ProFTPD.3F
> >>
> > . . . but this suggests it's already installed
> >
> > The first link also suggests that you have root access and a terminal
> >
> Hmm? Sorry, I don't see this. The installation part refers to your
> linkstation, when you have it already hacked. But I'm not at this stage (yet
> :-).

Hi
Ah, I see. I assumed that as you had posted the links then you already
had e.g. Debian installed. The method for linkstation Pro is here:

http://buffalo.nas-central.org/wiki/Install_Debian_on_the_Linkstation_Pro/Live

It will make your life a lot easier.
Good luck,
Steve

[Helmut Hullen]

Hallo, Richard,

Du meintest am 19.12.13:

> So according to the wiki, the samba version is:
> Samba 2.2.8a-ja-1.1-beta5

That version is more than 10 years old ...

Viele Gruesse!
Helmut