[SOLVED] Error: 0x8007003B - File transfer from Windows 10 Client to Ubuntu Server

Ecronic 0

EDIT: I've marked this post as solved. But, whoever reads this post please bare in mind that this network error doesn't have a single solution. This is what solved my issue.

Before you read through I would advise doing very simple tasks:

Test your LAN cables if you are facing this issue while connected to the network via LAN cables
Restart you devices involved with you issue(client pc(s), server(s), router(s), switch(s), firewall(s) etc.
Update your network drivers to the latest, update you OS with latest updates as well

I learnt it the hard way that sometimes the solution might be very simple.

Good Luck!

Hi Guys,
I'm having issues with my setup. It's been running fine since more than a year and all of a sudden I'm unable to transfer files over LAN network. It's not an issue of the file size like I've read on forums but even if the file is 2MB it still give me the above mention error. I can transfer if I'm connected over WIFI network. There's nothing that is blocking the traffic over LAN as I can stream movies from my server to my client via Plex on the Windows 10 and Nvidia Shield TV.

So far I've tried:

Uninstalling Bitdefender Total Security (Client PC)
Disable Windows Firewall & Windows Defender
Network Reset (Client PC)
Disconnected Mapped drives and Reconnected after restart
Clean installed the network drivers
Don't have any VPN running on my Windows 10 PC so that is definitely not the issue as mentioned in other forums After each step I've restarted the laptop.

My Ubuntu Server specs are:
HP Pro3500 G2 MT PC
Processor: Intel(R) Core(TM) i5-3340 CPU @ 3.10GHz
Installed Physical Memory (RAM): 12.0 GB
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Qualcomm Atheros AR9287 Wireless Network Adapter (rev 01)

My client laptop specs are:
Alienware 14 R2
Processor: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2401 MHz, 4 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM): 16.0 GB
Killer E2200 Gigabit Ethernet Controller
Killer Wireless-N 1202 Network Adapter Thanks
Ecronic

Gary Nebbett 5,851 Reputation points

2023-04-24T16:54:23.2266667+00:00

Hello Ecronic,

Are you prepared to share trace data? Many posters are not prepared to share trace data, quite rightly fearing that the data might reveal sensitive information. Your error (symbolic name: ERROR_UNEXP_NET_ERR) is quite unusual. If you are prepared to share trace data then let us know and I will think about which trace data would be most useful.

Gary
Ecronic 0 Reputation points

2023-04-25T09:58:15.3366667+00:00

Hi Gary, I'm willing to provide all the data required to help me resolve this issue. This is an local home media setup so I have no issues providing any data. But I only request to let me know the steps. I'm not very familiar with Powershell/CMD commands. So if there's anything specific information required please let me know how to acquire it and I will post it here. Thanks.
Gary Nebbett 5,851 Reputation points

2023-04-25T10:25:51.9466667+00:00

Hello Ecronic,

In a command window running as administrator, issue the command netsh trace start provider=Microsoft-Windows-SMBClient report=disabled overwrite=yes tracefile=why.etl to start the trace; reproduce the problem and then stop the trace with the command netsh trace stop. The file why.etl then contains the trace data.

Depending on what this first trace shows, we may need to perform additional traces to focus on specific activities and devices.

Keeping the trace as short as possible (i.e. start trace, quickly reproduce the problem and then stop the trace) is always a good idea.

Gary
Ecronic 0 Reputation points

2023-04-25T14:38:32.8466667+00:00

Hi Gary, I've complete the trace (why.etl) and attached below. For some reason it is now transferring but at a very slow rate. So, I left the trace running for a short time and then cancelled the transfer and stopped the trace. Hope this was correct. TraceFile: https://1drv.ms/u/s!Ai1StriB1seUkpsGfIYsaAkUiOnpdQ?e=I6Xc9j TransferDialog.png Let me know what's next. Thanks.
Gary Nebbett 5,851 Reputation points

2023-04-25T16:38:52.4666667+00:00

Hello Ecronic,

You probably understand that there is quite a big difference between saying that a system is failing with a relatively rare error code and saying that it is working but is perceived to be slow.

The selection of trace provider was driven by the need to understand an error; some of the data can be used to estimate the transfer rate.

The total trace duration was a bit less than 5 seconds and the trace indicates a data transfer rate of 600 megabytes per second; this value might be misleading (not an end-to-end transfer rate). The TransferDialog.png image is not terribly informative, since there is little/no transfer rate history visible and the "Time remaining" estimate is still in the "Calculating..." phase.

I will see if I can find anything unusual in the trace, but my immediate response is that everything seems very healthy.

Gary
Ecronic 0 Reputation points

2023-04-25T17:00:56.1833333+00:00
Hi Gary, I understand the difference between the two. That is why I'm surprised it's working today. Until yesterday I was getting the error code mentioned in my Post subject. Only thing I've done since posting yesterday is:

Samba server restart - Ubuntu Server

Ubuntu Server restart

Windows Client restart - only client on accessing the shares

Router reset Will await you reply if you can spot something unusual in the trace report. In the mean time, I'll keep checking if the error comes back. thanks.
Ecronic 0 Reputation points

2023-04-25T17:25:11.82+00:00
Hi Gary, I understand the difference between the two. That is why I'm surprised how it's transferring today at a slower rate and not showing the error code in my Post title. Only thing I've done after posting here is:

Restart Samba server - Ubuntu Server

Restart Ubuntu Server

Restart Windows Client - only pc that uses the shares

Reset Router I will wait to see if you can find something else in the trace reports. In the meantime I will keep checking if the error shows up again and will keep collecting a trace every time I try to regenerate the error. thanks.
Gary Nebbett 5,851 Reputation points

2023-04-25T18:29:44.5633333+00:00

Hello Ecronic,

There are some minor oddities in the trace, but that might just be related to how you used the user interface (an attempt to create a file named fg-02.bin in the source directory, which fails with STATUS_OBJECT_NAME_COLLISION - as it should).

My speed estimate was also incorrect - the first 5 megabytes seem to have been transmitted at that speed, but there is a 2.4 second delay until the 6th megabyte is sent (the last data in the trace file). These discrepancies are possibly just a side-effect of local buffering (the trace provider is not well suited for this type of performance analysis).

Please feel free to send another trace if the error behaviour returns.

Gary
Gary Nebbett 5,851 Reputation points

2023-04-25T18:54:15.37+00:00

Hello Ecronic,

There are perhaps more oddities than I first thought:

The connection to the share seems to flip-flop between established and unestablished frequently and quickly (200 microseconds, in the example above).

We might be chasing phantoms, so a new clear-cut error case would still be very useful.

Gary
Ecronic 0 Reputation points

2023-04-25T19:20:03.1433333+00:00

Hi Gary, Thanks for taking time to look through this issue thoroughly. I will upload a trace with the previous error if generated and will message you here one I have the file ready. Thanks.
Ecronic 0 Reputation points

2023-04-25T19:46:14.22+00:00

Hi Gary, Got a new trace with the actual error. Attaching the link. I know the screenshot doesn't share much information but still attaching it.

Trace Report: https://1drv.ms/u/s!Ai1StriB1seUkpsIK70tiluERc9Lbw?e=u3F4gK Thanks.
Gary Nebbett 5,851 Reputation points

2023-04-26T10:53:48.72+00:00

Hello Ecronic, The belief that I am currently trying to firm up is that the client is too fast for the server (the server might be overwhelmed) - in both traces the problems seem to being when the client writes 6 or 7 megabytes within a few milliseconds to the server (data rates of 300 to 600 megabytes per second); this data is never acknowledged (at the SMB protocol level). There is an SMB flow control mechanism, but it may be the case that the negotiated flow control values are inappropriate. After a bit more thinking/researching, I will post again. Gary
Gary Nebbett 5,851 Reputation points

2023-04-26T11:41:59.9066667+00:00

Hello Ecronic,

One thing that you could test is to issue the following command in a PowerShell window running as administrator: Set-SmbClientConfiguration -EnableLargeMtu $false.

Now test how well file transfers work. Once you have some results, you can restore the original setting with the command Set-SmbClientConfiguration -EnableLargeMtu $true.

Disabling the large MTU feature limits performance and is perhaps not an ideal long term solution. The test is just intended to see if the large MTU feature is contributing to the problem.

Gary
Ecronic 0 Reputation points

2023-04-26T15:41:50.5666667+00:00

Hi Gary,

Set-SmbClientConfiguration -EnableLargeMtu $false - didn't make any difference. Still no transfer at all and ends up in the error.

Thanks.
Ecronic 0 Reputation points

2023-04-26T15:44:16.2666667+00:00

Hi Gary,

Sorry but I have missed one detail in my first post. A few weeks back I renewed my contract with the ISP and received a new router. The settings of the router - username, password, wifi settings, lan settings, IP settings etc... were auto loaded from the ISP server. I didn't have to configure anything.

Do you think if the new router could be causing the transfer issues?

thanks.
Gary Nebbett 5,851 Reputation points

2023-04-26T16:41:26.2733333+00:00

Hello Ecronic,

Let's extend the trace to include data from the TCP/IP stack: netsh trace start provider=Microsoft-Windows-SMBClient provider=Microsoft-Windows-TCPIP report=disabled overwrite=yes tracefile=why.etl.

If you can create a new trace of the error with that start command then that would be helpful.

Gary
Ecronic 0 Reputation points

2023-04-26T18:06:21.67+00:00

Hi Gary,

Here's the new trace file including the TCP/IP stack - https://1drv.ms/u/s!Ai1StriB1seUkpsJ-S78uIsdv9UOdQ?e=xk94QD

thanks.
Gary Nebbett 5,851 Reputation points

2023-04-27T14:04:30.1633333+00:00

Hello Ecronic,

The data transfer rate is indeed atrocious; this is a pictorial representation:

The Y-axis is data transferred in megabytes and the X-axis is time in seconds. It is taking about 30 seconds to transfer 1 megabyte (30 kilobytes/second). The shapes at the bottom of the graph are points at which "interesting" (often bad) TCP events occur. For a transfer within the same subnet (between 192.168.11.3 and 192.168.11.2) these are unexpected results.

More analysis needed...

Gary
Gary Nebbett 5,851 Reputation points

2023-04-27T15:29:20.47+00:00

Hello Ecronic,

As unlikely as it may seem, the new router could well be the problem. There is nothing wrong at the SMB level; the very slow transfer rate is causing unexpected timeouts on some lengthy SMB operations (such as "write" operations).

Do you have any other multiport device that you could use to connect the client and the server (e.g. an old router)?

Gary
Ecronic 0 Reputation points

2023-04-27T15:39:02.33+00:00

Hi Gary,

Yes, I still have the old router. I was waiting for your analysis to come through after the last trace upload. I will swap the old router and do the test again. Will take some time since I can only work on it at a specific time but will make sure to update the results here.

Thanks again for your time. Will update soon.

thanks.
Ecronic 0 Reputation points

2023-04-28T16:16:40.1533333+00:00

Hi Gary,

I just finished testing with the old router. I still get the same network error. I don't understand why but everything worked well before. Besides all this I'm able to transfer the files when I'm connected to my WIFI network. It's only the wired network that isn't allowing the transfer from Windows 10 client to Ubuntu Server but I can transfer from Ubuntu Server to Windows 10 Client.

Hope there's something more we can test and figure this out. Most likely the only option I have other than this is to reset my Windows 10 OS.

thanks.
Gary Nebbett 5,851 Reputation points

2023-04-29T07:46:28.1633333+00:00

Hello Ecronic,

You could try the following. Search the web for a online network speed test (https://www.speedtest.net/ often comes near the top of the results for me) and test both the client and server.

If the client has a bad result in one or both directions (upload and download) and the server has better results then retest the client using the cable of the server.

Let us know a brief summary of the results.

Gary
Ecronic 0 Reputation points

2023-04-29T16:48:52.38+00:00

Hi Gary,

Thanks for asking to test switching the cables. I don't know why I didn't do this basic test before.

Anyways, here's the test before swapping the cable between Client and Server:

Windows Client Old Cable
D: 309.42Mbps U: 14.42Mbps
Ubuntu Server Old Cable
D: 318.32Mbps U: 102.93Mbps

Windows Client After Cable Swap
D: 315.51Mbps U: 103.51Mbps
Ubuntu Server After Cable Swap
D: 283.01Mbps U: 105.52Mbps

I also tested the internal file transfer (Client to Server) as well. And it started transferring the immediately like it should.

I know it seems like an odd solution but if you still want to do a trace to see the behaviour of the network I can do it. Let me know.

Thanks.
Ecronic 0 Reputation points

2023-04-29T17:21:06.68+00:00

Hi Gary,

Just a quick detail, before I started doing the above tests today, I was going through my Add/Remove Programs and uninstalling unwanted and unused programs. I came across something call "Npcap" in the list. I uninstalled it, restarted the PC and then read your message to do the above test. I'm not sure what that program does but I couldn't find a way to launch it from anywhere on my pc. Do you think it had something to do with my issue?

thanks.
Gary Nebbett 5,851 Reputation points

2023-04-29T18:18:41.7033333+00:00

Hello Ecronic,

I think that "npcap" is possibly a contraction of "network packet capture". If you have installed Wireshark (or a similar tool) in the past then that may explain its presence.

It is possible but unlikely that this driver had an influence on the problem - the failing cable could explain everything.

There is no need for any further trace - attaining an acceptably working configuration is success enough.

Gary
Ecronic 0 Reputation points

2023-04-29T19:20:06.6266667+00:00

Hi Gary,

Thank you so much for your time on helping me solve this issue. These cables are 2-3years old now. I will be changing to a new set of CAT6e cables soon.

thanks very much again!
Alise 0 Reputation points

2024-07-16T10:41:15.19+00:00

Error 0x8007003B indicates a network issue causing file transfer failure between Windows 10 and Ubuntu. To resolve, disable antivirus/firewall, use a wired connection, or try a different transfer method like SCP or FTP. And for Windows 10 keys, go to Hypest Key

3 answers

Limitless Technology 44,121 Reputation points

2023-04-24T12:10:59.0866667+00:00

Use answers to provide solutions to the user's question.Hello there Try changing the SMB Protocal form SMB 3 to 1 and see if that helps. Network Sharing Center>Advanced Sharing>make sure network discovery is turn on and also file and printer sharing for private network is turn on. The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue. https://social.technet.microsoft.com/Forums/windows/en-US/01b5f31b-e911-410f-a24e-f5175ceed709/error-0x8007003b-an-unexpected-network-error-occurred?forum=w8itpronetworking Hope this resolves your Query !! --If the reply is helpful, please Upvote and Accept it as an answer--
Please sign in to rate this answer.
Ecronic 0 Reputation points

2023-04-24T16:05:49.6666667+00:00

I have tried changing from SMB protocol through NT1 - SMB3. But nothing seems to work. The network discovery & file & printer sharing is on. Like I mentioned in my post everything was working fine for a year and a half. True that this problem seems very similar to other posters on the net and forums. But there are so many other solutions available - one of the poster resolved the issue by replacing his router. So don't just assume this is a double post!
Sign in to comment
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
1 deleted comment

Comments have been turned off. Learn more
Alise 0 Reputation points

2024-07-16T10:40:57.11+00:00

Error 0x8007003B indicates a network issue causing file transfer failure between Windows 10 and Ubuntu. To resolve, disable antivirus/firewall, use a wired connection, or try a different transfer method like SCP or FTP. And for Windows 10 keys, go to Hypest Key
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

[SOLVED] Error: 0x8007003B - File transfer from Windows 10 Client to Ubuntu Server

3 answers