The posted smb.conf file is just for configuring the samba server/shares on Hermes-III and does not have any bearing on connecting to the NAS. Have you tried to manually mount a NAS share?
I agree with bab1 in your thread on the ubuntu forum it could be a bug in the samba 4 client and whatever version of samba is running on the NAS. |
Quote:
I have just found out the the Ubuntu firewall is also part of the problem. One post suggested that this should be disabled: Code:
sudo ufw disable But when I enable it again Code:
sudo ufw enable Is there a way to register the network with the firewall? Paul. |
Just a follow up, have "excluded" the ports from the Ubuntu Fire Wall (thanks to info in someone else's post) and all appears to be running OK now; I again have access to all my network shares excepting those on the little NAS.
Just as an aside, as I understand it the NAS is running a cut-down version of Samba. I just wonder whether the problem is related to some protocol changes or restrictions from Ubuntu 13.10, which had no problems linking to the shares of the little NAS, and Ubuntu 14.04 which is the version giving me all these problems. Paul. |
Cannot connect to my Snake OS NAS with Ubuntu 14.04
The flow of TCP is processed at a pace slower compared to the accuracy of the net. TCP offload engine solves this issue through getting rid of the burden or offloading from the I/O subsystem as well as the microprocessor.
|
Quote:
|
Just a follow up.
I have set up basic FTP via the "Snake OS" operating system of the little NAS (WLX-652 gwydion). This is mounted at boot by Gigolo on the Ubuntu machine and works to a fashion as it allows me to update files from the network by FTP download. But it is one way only and hardly ideal. I also noted the setup of the little NAS and have listed this below in case the problem lies there. Code:
HTTP Web Admin Port: 80 |
Has anyone figured this out? I have the same device and same problem. Not sure if it is a permissions issue. I am somewhat new to Linux as well. I have done all the above recommended, which did help with getting my other computer to show up in the browse networks. And my NAS device shows up. But I get the same timeout message. And when I do the smbclient -L 192.168.1.106 I get:
Conversion error: Incomplete multibyte sequence() protocol negotiation failed: NT_STATUS_INVALID_PARAMETER It asks me for my system password first. I can connect to my NAS via FTP, but like paul1945 mentioned it does not allow for the update of the files? Any ideas? Thanks. |
anonku,
I recommend you open a new thread. This is an old thread, and is unlikely to draw much attention. It would help if you posted more details about the NAS you have, and how its configured. Quote:
|
No resolution to Samba but FTP works fine.
I have not been able to come up with a resolution to this problem, even though I have tried many different approaches. I had also posted the problem on the Ubuntu Forum, but no-one there seemed to be able to come up with an answer. The suggestion was made that the little NAS has a cut-down version of Samba that is not compatible with the later versions of Samba (probably relates to security features lacking on Samba of the NAS).
I therefore use FTP which works fine and with some help have been able to set it up so it works both ways and therefore fulfills my needs the same way Samba would have done. If you want the details of setting up access via FTP on the NAS, I have kept a copy of the instructions, please let me know. Paul. |
think I will just make due
Thanks Paul for the reply. I have the FTP setup as the work around as well. Thanks for the info, but perhaps will just make due. It is only for home use anyhow. Thanks for all your work and to all others on this issue. Might be time for a NAS upgrade.
|
All times are GMT -5. The time now is 03:47 PM. |