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

Tiemen Ruiten tiemen at dgr.am
Wed Dec 18 16:11:49 MST 2013


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


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.
>
> cheers
> richard
>
>
>> On 10-12-13 01:02, Richard llom wrote:
>>> Hello,
>>> I updated my system to samba 4:
>>> [richard at 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 at chakra ~]$ samba --version
>>> Version 4.1.1
>>> [richard at 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 at 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.



More information about the samba mailing list