Bug Description

The error reported is "Software caused connection abort". See the screenshot.

It pops up right at the end of the copy operation. This doesn't happen when copying the very same file using a different protocol. Neither does it happen when using another device to copy the very same file over SMB.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Step 1
create folders in your home directory which then serve as mountpoints. For each share, you need one folder.
example: /home/user/myshare_on_NAS

Step 2
Next, create a text file that contains your credentials that are needed to access your shares on the server, name it something like ".mynascred" Edit this file, it should then look like this:
username=myusername_for_server
password=mypassword_for_server
Save, then make sure no one except you can access that file (right-click, properties->permissions)

This is all. Log off and back, then you should be able to access your shares using at least Ubuntu/Xubuntu standard filemanager. No additional mount commands or scripts are required with Ubuntu 14.04 (this might be different with older versions)

Medion Life NAS, 1.5TB, all routers irrelevant- same issue. Absolutely no problems with Win7, XP, Ubuntu KK, MM 10.10, LL with either accessing, copying or uploading files to any folder.

11.04 can upload files and create folders, but cannot download files, be it copy, send to or open. All file types tried and the only ones I can pull from the NAS are small text files and .htm or .html files which will work ok.

I can however open a *.jpg in GIMP from the NAS which I cannot copy from the NAS- mmm, interesting.

I just fired up an old Lucid Lynx box and a Karmic Koala box and it works seamlessly. Issue only occurs with 11.04.

I have just changed from Nautilus to Nemo and there is NO difference- the issue still occurs.

The Samba developers are pretty adamant that this isn't a bug in any version of their software. They place the blame for this problem squarely on the shoulders of Iomega, Zyxel, and anybody else who modified their code for their NAS boxes. The problem, apparently, is that newer versions of Samba hit servers with multiple requests at the same time, and for some reason the Zyxel and Iomega boxes can't handle this. The best solution they've come up with is to modify the smb.conf file on your server to include this setting: "max mux = 1".

Hi I am having this issue as of about a week ago running 14.04 Ubuntu on Intel® Core™ i7-3770 CPU @ 3.40GHz × 8 This is my conf file. Happy to provide any other info.

more /etc/samba/smb.conf
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

Same issue happens for me with a Shuttle Omninas KD20, which doesn't give shell access (and the known hack to get shell access doesn't work on latest firmware). Strange thing is that it doesn't happen on every file. Also, it seems that smbclient will happily fetch the files without issues, even though Nautilus will consistently fail to copy the file, as will gedit fail to open it. I filed a support request at shuttle with a link to samba bug 10548 (https://bugzilla.samba.org/show_bug.cgi?id=10584), hoping that will get me somewhere.