similar to: The specified Network Name is no longer available

I'm hoping someone can shed some light on this. I'm using a Linux box in my house as a NAS, so that I can make backups, move large files, etc. The problem is that, whenever I try to move/copy a file larger than 100MB or so off of the linux machine to my Windows machine, I get "Specified network name is no longer available" on the Windows machine and the transfer aborts.

On 14/08/2020 14:08, Gerard Owusu wrote: > Hello again, > > So I made an overall change to the config and removed the sambashare > entirely. > > I just want to have a basic connection before any further modification. > Fair enough, lets just get something straight, you are connecting from Win 10 to Samba, but what OS is Samba running on ? Can you connect from explorer to

Hi, I am struggling to complete my installation of Samba to share files to my Samba Server. The error:The specified network name is no longer available - keeps recurring irrespective of the changes I make from online forums. Please help. Kind regards, Gerard

To answer you questions: Win 10 to Samba, but what OS is Samba running on ? Samba is running on a Centos 7 Server - UNIX Can you connect from explorer to the 'Anonymous' share ? I cannot connect. It gave me the error in the screenshot I sent you. Have you created any Samba users on the Samba server ? I have not created any user apart from 'root' of which I setup a password

Hi Volker, Jordan Coleman, Murray Taylor, David Kennel, Frederic Corne and Stephen Jones all wrote about the problem of a specified network intermittently reported "no longer available" when writing to a file. It's the same problem which I complained about on April 7. I then assumed it had to do with the presence of a w2k3 server in the domain. The problem disappeared after I

I feel stupid even asking, and I have a feeling the solution is something that has been staring me right in the face for hours. I can't seem to access network shared on my samba PDC. I've done this before, and I am using a similar smb.conf file and I am just at the point where I can't get anything else to happen with this thing. My original problem was that I could not get WINXP

hi guys, I'm having trouble accessing samba share files from a windows xp client using a vpn pptp connection. I configured samba and it works excellent on the LAN but when i connect through pptp and access the samba server \\192.168.3.1 I can see the shared folders but when i try to browse them, windows hangs (4 a change!) for a while then returns "the specified network name

I have a user w/ puzzling error. We have not been able to get a tcpdump or significant samba log, but I'm posting to see if anyone else has seen this. I did find some older posts that point to possible client issues. We're running samba 3.0.25b on RHEL4. The user reports: I am getting an error whenever I want to make a copy of a MS Excel file on my shared network drive: (From

I am not sure if this is a windows problem or a Samba problem. We have a network consisting of a mixture of Samba and windows servers running under a windows PDC. The network is a WAN with radio (802.11B) point-to-point links between buildings within the campus, and frame relay and ADSL links to interstate offices. The interstate offices have windows BDC's. Most of the desktops are win2k

I've been tearing my hair out trying to get this to work. Problem: Samba versions 2.2.4 and 2.2.5, running on mandrake 8.2 and 8.1 respectively, both with XFS (the mdk 8.2 machine is using a STOCK kernel 2.4.18-6mdk), the mdk 8.1 machine is using a stock 2.4.18 + xfs 1.1 patch. Windows 2000 SP2 client tries to copy a folder with files in it to the share. Copy seems to start but ends rapidly

Hello again, So I made an overall change to the config and removed the sambashare entirely. I just want to have a basic connection before any further modification. Below is the config setup: [global]? ? ? ? log file = %S.log? ? ? ? log level = 3? ? ? ? workgroup = WORKGROUP? ? ? ? security = user? ? ? ? printing = cups? ? ? ? printcap name = cups? ? ? ? cups options = raw? ? ? ? ntlm auth = yes? ?

Hi, first of all, sorry for my poor english. I have installed Samba4 (stable tarball) on a fresh Centos 6.3 x64 server, with the "classicupgrade" command. With great difficulty I managed to correctly configure the DNS server (bind). "kinit", "smbclient" and "samba_dnsupdate - verbose - all-names" give the desired output. Starting samba daemon, this is the

Hi Rowland, Sorry for the delay, my current smb.conf is: [global]? ? ? ? log file = %S.log? ? ? ? log level = 3? ? ? ? workgroup = WORKGROUP? ? ? ? security = user? ? ? ? passdb backend = tdbsam? ? ? ? printing = cups? ? ? ? printcap name = cups? ? ? ? load printers = yes? ? ? ? cups options = raw? ? ? ? lanman auth = no? ? ? ? ntlm auth = yes? ? ? ? client lanman auth = no [Anonymous]? ? ? ?

Hi Rowland, Made some changes as shown below: [global]? ? ? ? log file = %S.log? ? ? ? log level = 3? ? ? ? workgroup = WORKGROUP? ? ? ? security = user? ? ? ? passdb backend = tdbsam? ? ? ? printing = cups? ? ? ? printcap name = cups? ? ? ? load printers = yes? ? ? ? cups options = raw? ? ? ? lanman auth = no? ? ? ? ntlm auth = yes [Anonymous]? ? ? ? comment = anonymous file share? ? ? ? path =

Hi, I got a weird probleme. I have a fileserver running FreeBSD 6.1 and 2 client running Windows XP. Samba version 3.0.23c is installed on FreeBSD server when I'm downloading something from the server to any of my client machine, I got no probleme even with big file, but when I'm uploading from any client machine to the server if the file or folder is bigger than 20mo, after a few

Hello Samba people, I have been successfully using Samba for several years, across many minor versions of Samba across many minor versions of Linux kernel 2.4.x and 2.6.x, against a Windows 2000 and then in the past couple of years 2003 AD Domain. This morning, something broke... Setting the stage: RedHat Fedora based Linux box, FC8, updated over time using 'yum update'...,

Hi all. I'm trying to set up one of my Unix machines at home so I can access my stuff there via SMB from the Internet at large (read: from Windows-using clients'). I'm behind two NATting devices-- the lame-p Prestige DSL modem provided by Sprint DSL (a.k.a. Earthlink?) and a more typical home DSL/cable gateway device. I've poked holes in BOTH of these devices on ports 137, 138,

I have a samba PDC/BDC setup with a small number of W2k clients. Not too long ago I set up a set of new servers on fresh Fedora 1 boxes using Samba 3.0.1 and migrated my LDAP to the new schema. It was all working quite well until recently. Suddenly, when I try to change permissions on a windows share (from the windows box), after I give the root password, I get a message that "The

I have a reproducible intermittent error large site - "The specified network name is no longer available". This happens when copying large files. Below is part of log level 10 output & strace. Sorry for the long posting. I will probably need to put the loglevel 10 attached to a bugzilla - but thought I would try the lists initially. RHEL4 samba-3.0.25b-1.el4_6.4

hi all i'm experiencing some really funny behavior on our samba server (CentOS5, Samba Version 3.0.25b-1.el5_1.4) from time to time, our xp/2000 users (our workstations are xp/2000 based) are reporting that while they try to copy a file from one location of the file server to another, they are presented with the the error.... "the specified network name no longer exists" if they