Jump to content
bigshotking

File Transfer results in Error 0x8007003B

55 posts in this topic Last Reply

Recommended Posts

Hello,

 

This is the first issue I've ever had with moving files to my unraid server. I just got back from a week long vacation and wanted to move some new files onto the server. I'm able to open files and even transfer them from the unraid server to my desktop with no issues at all. When I try to copy a file from my Windows 10 machine to any of my shares the transfer window will popup but won't start, time remaining is just left on calculating before it errors out with: Error 0x8007003B: An unexpected network error occurred.

 

What I've tried:

- Rebooted the unraid server

- Rebooted my Windows 10 desktop

- Disabled my antivirus and firewall

- Rebooted my switch and router

- Removed any Windows 10 updates that I could that were installed while I was gone.

- Googled the problem and searched the forums (Tried disabling antivirus/firewall, rebooting router/switch, removed Windows updates)

 

System Info:

Unraid v6.6.7

Windows 10 Pro 64bit (Version 1809) (EDIT: Forgot the version number! Sorry!)

 

Screenshot of the error I'm having:

745429760_TransferError.PNG.04df54fa48ee2fa9e740ec6efd7df297.PNG

 

Here is my unraid system log:

towernas-syslog-20190417-1431.zip.

 

Any help would be greatly appreciated.

 

Thank you.

Edited by bigshotking

Share this post


Link to post

Have you found this one:

 

     https://windowsreport.com/network-error-0x8007003b-fix/

 

(Found with Google and 'Error 0x8007003B: An unexpected network error occurred' as the target.)  As much as you may not like it, it appears that MS is 'owning' this one.  I can tell you that my WIN10 Pro-64Bit (version 1809) is not having this problem.  (If you don't know what version is currently running on your Windows computer, type   winver   in the search box and click on the result.)  By the way, when asking about Win10 issues, always list the version number, variety --Home, pro, etc-- and whether 32-or-64 Bit.   All of these have minor differences that make them unique! 

 

EDIT:   Are you using a Mapped drive or working from the Network location in Windows Explorer?  

Edited by Frank1940

Share this post


Link to post
53 minutes ago, Frank1940 said:

Have you found this one:

 

     https://windowsreport.com/network-error-0x8007003b-fix/

 

(Found with Google and 'Error 0x8007003B: An unexpected network error occurred' as the target.)  As much as you may not like it, it appears that MS is 'owning' this one.  I can tell you that my WIN10 Pro-64Bit (version 1809) is not having this problem.  (If you don't know what version is currently running on your Windows computer, type   winver   in the search box and click on the result.)  By the way, when asking about Win10 issues, always list the version number, variety --Home, pro, etc-- and whether 32-or-64 Bit.   All of these have minor differences that make them unique! 

 

EDIT:   Are you using a Mapped drive or working from the Network location in Windows Explorer?  

Thanks for the reply! That is one of the sites I found while googling, I tried the various different things it suggested and didn't get anywhere. I'm running the same version of Windows as you are, Win 10 Pro-64bit (1809) (I posted it in the original post, guess you didn't see it).

 

I'm using a mapped drive for my different shares.

 

I don't know what I did but I tried to copy another file to a different folder on the share and boom it worked. Went back and tried to move the original file that was giving problems and boom, that worked as well. Now I'm having no issues at all with copying files. I have no idea what I did to fix the issue, but it works now.

 

Thanks again for the reply, if I figure out what fixed the issue I'll be sure to post it here.

Share this post


Link to post

First, try using the Windows Explorer to as the destination window that you drag-and-drop the file into:

 

515418201_Annotation2019-04-17212112.thumb.jpg.94f0d5aec3af6a0826a666cfbed18c4d.jpg

 

If that does not work.  MS is trying to add more and more security to SMB usage in Windows.  Here is a thread to read.  Start on page three as it contains the most recent stuff that MS is doing to the default settings. 

 

    https://forums.unraid.net/topic/53172-windows-issues-with-unraid/

 

 

Do check to see if Your computer has updated on April 9th or later.  (The April updates are a real disaster!   They should be fixed with re-released updates sometime later this month...)  If it was, see if you roll them back and see if that fixes things. 

Share this post


Link to post

Hi, did you find a solution? I have the same problem, sometimes files do not copy with the same error message,,,,,

Share this post


Link to post

I've also got this issue happening when I copy large files from the unRAID box down to my Windows 10 machine. I've tried this on two different physical Windows 10 boxes and got the same error.

unRAID is V6.7.2

Windows 10 is 1803 Build 17134.885

 

Capture.JPG

Share this post


Link to post

I also have the same type of problem.

 

- Very often I cannot copy the file as everyone else mentioned

- It occurs even if I use a third party copier (TeraCopy)

- For a few minutes I cannot remove or overwrite the partially copied file. If I try later, I either get the same error or the partial file can be overwritten

- When I am copying/moving many files, it will only happen at the start of the copy. i.e., if the 1st file is copied the error does not occur for the following files.

 

As mentioned before, it might be some changes with how Win treats Samba, but, either way, a solution would be welcome, otherwise UnRaid is rentered practically unusable for us Windows users

Share this post


Link to post

i have the same problem the transfer rates drop down to 0 and then this errors apears... i expect a software i paid for to work and dont make this kind of problems...

Share this post


Link to post
1 hour ago, threiner said:

i have the same problem the transfer rates drop down to 0 and then this errors apears... i expect a software i paid for to work and dont make this kind of problems...

Are we sure the problem is on Unraid? Because it might be on the windows side.

 

Although it would be nice if somehow UnRaid could mitigate it

Share this post


Link to post
3 minutes ago, papnikol said:

Are we sure the problem is on Unraid? Because it might be on the windows side.

 

Although it would be nice if somehow UnRaid could mitigate it

i got a freenas and a few other NAS machines the problem only comes up on UNRAID, but it seems the problem is known for over three years and nobody cares...

Edited by threiner

Share this post


Link to post

It seems the Problem is not the SMB, i have mounted now the share over NFS and is the same theater the speed drops down and in the end i get the same stupid error. seems unraid is useless on this point on a windows machine.

 

Share this post


Link to post

Many of us are using Unraid with Windows and we don't encounter this problem. Have you tried any of the Frank1940 suggestions?

 

Are you mapping drives in Windows? I haven't seen any need to do this in many, many years. Most applications can browse the network and work with files on other computers just fine without assigning a drive letter to network shares.

Share this post


Link to post
3 minutes ago, trurl said:

Many of us are using Unraid with Windows and we don't encounter this problem. Have you tried any of the Frank1940 suggestions?

 

Are you mapping drives in Windows? I haven't seen any need to do this in many, many years. Most applications can browse the network and work with files on other computers just fine without assigning a drive letter to network shares.

i have read the forum up an down, have tried different windows PC with WIN 10 Enterprise, with win 10 PRO with WIN 10 Home. i have changed the Cabels the switch the NIC everything the result is the same. 

 

I use Enterprise Grade Network Equipment, i have now absolutley no idea anymore where this errors come from, when i install freenas on the same Machinbe sit runs as without any problem, but i like to use UNRAID as i like the concept. but it seems it just does not work.. over AFP with my MAc it runs with the same switch and the same cabel with nearly stable 100 MB/s if i use the SMB service on my mac i get the same thater. so it seems a problem on the UNRAID side.

 

 

Share this post


Link to post

Post your Unraid diagnostics when you encounter the problem.

Share this post


Link to post

here the diagnostics file...

 

is always the same transfer speed goes up after the error and clicking try again, to about 80 - 100 MB /s then it drops to 4- 6 MB/s after about 15-20 sec and then it can take between 1 and 5 minutes till it crases again with the error...

lastic-diagnostics-20190731-2345.zip

Share this post


Link to post

Any idea what these are all about?

Aug  1 00:23:22 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt/rawphotos (/): not exported
Aug  1 00:23:22 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt (/): not exported
Aug  1 00:23:22 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt/rawphotos (/): not exported
Aug  1 00:23:33 LASTIC rpc.mountd[16044]: can't get hostname of 192.168.1.52
Aug  1 00:24:18 LASTIC emhttpd: req (22): shareNameOrig=JPEG+SPORT+PROCESSED&shareName=JPEG_SPORT_PROCESSED&shareComment=Processed+Pictures+SPORT&shareAllocator=highwater&shareFloor=25000&shareSplitLevel=&shareInclude=&shareExclude=&shareUseCache=yes&cmdEditShare=Apply&csrf_token=****************
Aug  1 00:24:18 LASTIC emhttpd: shcmd (3150): mv '/mnt/user/JPEG SPORT PROCESSED' '/mnt/user/JPEG_SPORT_PROCESSED'
Aug  1 00:24:18 LASTIC emhttpd: shcmd (3151): mv '/boot/config/shares/JPEG SPORT PROCESSED.cfg' '/boot/config/shares/JPEG_SPORT_PROCESSED.cfg'
...
Aug  1 00:24:54 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt/JPG_SPORT_PROCESSED (/): not exported
Aug  1 00:24:54 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt (/): not exported
Aug  1 00:24:54 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt/JPG_SPORT_PROCESSED (/): not exported
Aug  1 00:25:05 LASTIC rpc.mountd[16044]: can't get hostname of 192.168.1.52
Aug  1 00:25:11 LASTIC rpcbind[22113]: connect from 192.168.1.52 to getport/addr(mountd)
Aug  1 00:25:11 LASTIC rpcbind[22114]: connect from 192.168.1.52 to getport/addr(nfs)
Aug  1 00:25:11 LASTIC rpcbind[22115]: connect from 192.168.1.52 to getport/addr(nlockmgr)
Aug  1 00:25:11 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /JPG_SPORT_PROCESSED (/): not exported
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug  1 00:25:22 LASTIC rpc.mountd[16044]: can't get hostname of 192.168.1.52
Aug  1 00:25:53 LASTIC rpcbind[22221]: connect from 192.168.1.52 to getport/addr(mountd)
Aug  1 00:25:53 LASTIC rpcbind[22222]: connect from 192.168.1.52 to getport/addr(nfs)
Aug  1 00:25:53 LASTIC rpcbind[22223]: connect from 192.168.1.52 to getport/addr(nlockmgr)
Aug  1 00:25:53 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /JPEG_SPORT_PROCESSED (/): not exported
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug  1 00:26:03 LASTIC rpc.mountd[16044]: can't get hostname of 192.168.1.52
...
and so on

Something seems to be trying to access things that don't actually exist on Unraid.

Share this post


Link to post

this was problems connectiing by NFS, but now it is connected. But this have nothing to do with the errors... 

 

First unraid requested a hostname, so i had to put it in the hosts file, and then there was the \user\ missing so the path was not found, but as you can see more down in the log it was resolved. but it does not change anything even over NFS the transfer rate drops down and the same windows error comes up

Edited by threiner

Share this post


Link to post
1 hour ago, trurl said:

Any idea what these are all about?


Aug  1 00:23:22 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt/rawphotos (/): not exported
Aug  1 00:23:22 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt (/): not exported
Aug  1 00:23:22 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt/rawphotos (/): not exported
Aug  1 00:23:33 LASTIC rpc.mountd[16044]: can't get hostname of 192.168.1.52
Aug  1 00:24:18 LASTIC emhttpd: req (22): shareNameOrig=JPEG+SPORT+PROCESSED&shareName=JPEG_SPORT_PROCESSED&shareComment=Processed+Pictures+SPORT&shareAllocator=highwater&shareFloor=25000&shareSplitLevel=&shareInclude=&shareExclude=&shareUseCache=yes&cmdEditShare=Apply&csrf_token=****************
Aug  1 00:24:18 LASTIC emhttpd: shcmd (3150): mv '/mnt/user/JPEG SPORT PROCESSED' '/mnt/user/JPEG_SPORT_PROCESSED'
Aug  1 00:24:18 LASTIC emhttpd: shcmd (3151): mv '/boot/config/shares/JPEG SPORT PROCESSED.cfg' '/boot/config/shares/JPEG_SPORT_PROCESSED.cfg'
...
Aug  1 00:24:54 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt/JPG_SPORT_PROCESSED (/): not exported
Aug  1 00:24:54 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt (/): not exported
Aug  1 00:24:54 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /mnt/JPG_SPORT_PROCESSED (/): not exported
Aug  1 00:25:05 LASTIC rpc.mountd[16044]: can't get hostname of 192.168.1.52
Aug  1 00:25:11 LASTIC rpcbind[22113]: connect from 192.168.1.52 to getport/addr(mountd)
Aug  1 00:25:11 LASTIC rpcbind[22114]: connect from 192.168.1.52 to getport/addr(nfs)
Aug  1 00:25:11 LASTIC rpcbind[22115]: connect from 192.168.1.52 to getport/addr(nlockmgr)
Aug  1 00:25:11 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /JPG_SPORT_PROCESSED (/): not exported
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug  1 00:25:22 LASTIC rpc.mountd[16044]: can't get hostname of 192.168.1.52
Aug  1 00:25:53 LASTIC rpcbind[22221]: connect from 192.168.1.52 to getport/addr(mountd)
Aug  1 00:25:53 LASTIC rpcbind[22222]: connect from 192.168.1.52 to getport/addr(nfs)
Aug  1 00:25:53 LASTIC rpcbind[22223]: connect from 192.168.1.52 to getport/addr(nlockmgr)
Aug  1 00:25:53 LASTIC rpc.mountd[16044]: refused mount request from 192.168.1.52 for /JPEG_SPORT_PROCESSED (/): not exported
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug  1 00:26:03 LASTIC rpc.mountd[16044]: can't get hostname of 192.168.1.52
...
and so on

Something seems to be trying to access things that don't actually exist on Unraid.

Any other ideas?

Share this post


Link to post
2 hours ago, threiner said:

looks like no more help here 😞

You have Intel & Realtek NIC in bonding bridge, pls try remove Intel from the bridge and plug LAN cable in Realtek only.

Edited by Benson

Share this post


Link to post
9 hours ago, Benson said:

You have Intel & Realtek NIC in bonding bridge, pls try remove Intel from the bridge and plug LAN cable in Realtek only.

Just wanted to mention that this is not the case for me (and I am guessing other people who have the same problem), so I hope this helps the particular user but it is not a general solution

Share this post


Link to post
12 hours ago, papnikol said:

Just wanted to mention that this is not the case for me (and I am guessing other people who have the same problem), so I hope this helps the particular user but it is not a general solution

for me the same the two nics are recognized as faiover by the system but it does not change anything if i have one or two pluged in or one nic removed... 😞

Share this post


Link to post

hmm so how this will now get solved`? seems not to be a good plan to charge for a piece of software and then ignore the problems... 

Share this post


Link to post

Help us understand what is different about your setup that makes it have this problem when so many of us are using Windows and Unraid together without this problem.

 

You never answered this question:

On 7/31/2019 at 6:48 PM, trurl said:

Are you mapping drives in Windows?

If you are then that would be one thing you are doing differently than I am. Not saying it should matter, just trying to get more information. I always work with files on other computers like Frank1940 explained here:

 

https://forums.unraid.net/topic/79454-file-transfer-results-in-error-0x8007003b/?do=findComment&comment=737866

 

Nobody in this thread seems to have responded directly to the suggestions in that post.

Share this post


Link to post

i have read all the suggestions in Frank1940 thread, and yes sure i map the Drives. I have no idea why this is happen, i have exchanged nearly everything but still have the same result. 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.