Absurdly slow transfer speeds

[ARF1410]

I have a new 220+, to replace an aging QNAP. Until Santa comes, I am temporarily using some older 2 TB hard drives, that arent on synology's list.
My QNAP was slow, with transfer rates of about 10MB/s. On that same network, my synology is only transfering data at about 200-300 kbps. I have hooked the synology directly to a laptop, and the transfer speed seems good (a 4.4 gb file in about 1 minute). So what sort of setting / configuration in the synology is making it so much slower than the QNAP on teh same network?

This post includes affiliate links. As an Amazon Associate, SynoForum.com may earn a commission if you make a purchase — at no extra cost to you.
It helps support our community! Learn more...

 

[Rusty]

I have a new 220+, to replace an aging QNAP. Until Santa comes, I am temporarily using some older 2 TB hard drives, that arent on synology's list.
My QNAP was slow, with transfer rates of about 10MB/s. On that same network, my synology is only transfering data at about 200-300 kbps. I have hooked the synology directly to a laptop, and the transfer speed seems good (a 4.4 gb file in about 1 minute). So what sort of setting / configuration in the synology is making it so much slower than the QNAP on teh same network?

More details are needed. Whats the other device, what is the network like, and what network switch/router (or both) are you using? What protocol? etc..

 

[fredbert]

You aren't using a 100 Mbps device (switch, hub!, router) somewhere in the network chain, are you?

Other thought would be your requests are going out to the Internet and back in again. Are you accessing the NAS using the LAN IP address or some other way?

 

[ARF1410]

I found a few older Cat 5 cables in my network, and replaced them with Cat 5e, or Cat 6, and that helped the QNAP. With the synology, If I use the synology "app" logged directly into the synology, and test moving a 160 MB file, it happens almost instaneously. However, if I use map network drive, and map the Synology as z: and move the same file... it is ridiculously slow... ie ~300 KBps . I have verified my switches hubs, routers and network cards are all gigbit speed.

 

[EAZ1964]

Possibly something in network settings.
Are all settings on pc and NAS side default?
like mtu, SMB3 etc, you might want to reset to default on both sides of the cable.
No antivirus that is checking all data on the PC? No VPN?
No wifi in between?
please share the resource manager screens of the syno and pc while copying..

 

[Rusty]

I found a few older Cat 5 cables in my network, and replaced them with Cat 5e, or Cat 6, and that helped the QNAP. With the synology, If I use the synology "app" logged directly into the synology, and test moving a 160 MB file, it happens almost instaneously. However, if I use map network drive, and map the Synology as z: and move the same file... it is ridiculously slow... ie ~300 KBps . I have verified my switches hubs, routers and network cards are all gigbit speed.

and just to be clear, mapping is done using the local IP address right, Not some public FQDN?

 

[ARF1410]

mapping was done by NAME, but when I re-mapped by IP address, it appeared to solve the problem. YIPEEE! Any idea why the difference?

 

[EAZ1964]

Yes, that is a windows feature when network DNS are messed up. several post on internet / this forum address the issue of resetting windows network configuration.

 

[Gerard]

and just to be clear, mapping is done using the local IP address right, Not some public FQDN?

mapping was done by NAME, but when I re-mapped by IP address, it appeared to solve the problem. YIPEEE! Any idea why the difference?

So smb was open through the internet if using the public FQDN???

 

[Rusty]

So smb was open through the internet if using the public FQDN???

No, I don't think this was the case. I think OP used a local name instead of an IP while making the network map

 

[Gerard]

No, I don't think this was the case. I think OP used a local name instead of an IP while making the network map

There’s a difference with speeds just based on local name vs local ip? Is that a limitation with the protocol or something?

 

[EAZ1964]

No this should never be the case The only difference should be the minute hit for the time needed to resolve the name vs ip on the network.

 

[ARF1410]

while maybe it shouldnt be the difference... but it is! I am not smart enough to figure that out on my own, but I read elsewhere (I forget where specifically) that others have observed the same thing. I just tested it again this morning. Doing a LAN speed test again, to the drive mapped by name, the speed is ~ 1.6 Mbps. When I do the test via the drive mapped by an IP address, I get ~ 600 Mbps. Should I quit now, as its working, or is there some simple fix / improvement I can do, with no risk of my screwing up my system? I am a NOVICE, so be gentle with me!

EDIT: Found a reddit post from 3 years ago: "WOW!! I've been struggling with extremely slow transfer speeds on my brand new fully loaded Synology DS619+. I mapped by IP and voila!! problem solved. thank you sir"

FQDN and SMB are greek to me!

 

[EAZ1964]

Maybe I was not clear, It should not happen, but it happens more often and can be resolved by resettting Windows network settings, the instructions are available on internet.

 

[ARF1410]

doesn't that reset the network card on a single computer? I had this same issue on the 3 different computers I tried. So you think I should do that on all 3 computers (plus, a couple more I have not yet tried connecting with?). And best I can tell, I shouldn't actually have to reconfigure my network, all the setting and connections will be remembered after doing this?

 

[EAZ1964]

You may have to enter new login data for your devices and possibly wifi password and loss of bluetooth connection to BT devices. for the rest not too much will change:

1. In the search box on the taskbar click Start, type command prompt, right-click the command prompt result and then select Run as administrator and confirm.
2. At the command prompt (decline restarting your machine until you have entered the final command):
   1. Type ipconfig /release and press Enter.
   2. Type ipconfig /flushdns and press Enter.
   3. Type ipconfig /renew and press Enter. (This will stall for a moment.)
   4. Type netsh int ip reset and press Enter. (Don’t restart yet.)
   5. Type netsh winsock reset and press Enter.
3. Now restart your machine using Start > Power > Restart once more and test to see if the issue is resolved.

You might want to delete your network card from hardware, confirm to delete drivers as well, restart and have windows re-detect and install the network card. It is always better to search for latest ethernet drivers for your specific network card.

On the nas, also clear the SMB cache.
check if ws discovery is enabled on the nas.

some time ago, there was another post on this, Netbios was mentioned, have a look:

SMB: Name vs IP speed difference copying files Windows???

I am no network engineer, so I dont know if this is normal or not, but this is absolutely repeatable for me give or take a few mbs/sec... I am getting different speeds copying files over the network on my Windows machines to my Nas. If I use \\IP\folder its a faster transfer by about double! vs...

www.synoforum.com

 

[ARF1410]

tried all that, and no difference... still unusably slow when mapped by name. However, as long as it works OK when mapped by IP address, I guess I wont worry about it...

 

[EAZ1964]

Yes, frustrating, but there is a workaround.
last one: did you try switching off ipv6 and smb1 in the NAS and or on the PC?