Unable to get local wired transfer speeds higher than 11 MB/s

[shadowbeh2]

Hello, here is my issue:

I have two PCs, one is my everyday use gaming desktop, the other is a small Plex server that I have recently built. My issue is that I am unable to transfer files between these two PCs faster than 11MB/s. I find it odd because both PCs can achieve higher transfer rates over the internet than they can locally, seems backwards to me.

Here is some extra info that may be useful:

Gaming PC:

• 
  Operating System: Windows 10 Pro 64-bit
  CPU: Intel Core i7 4770K @ 3.50GHz
  RAM: 16.0GB Dual-Channel DDR3
  Motherboard: MSI Z87-GD65 GAMING

Plex Server:

• 
  Operating System: Windows Server 2012 R2 Datacenter 64-bit
  CPU: AMD FX-6300
  RAM: 8.00GB Dual-Channel DDR3
  Motherboard: ASUSTeK Computer INC. M5A78L-M PLUS/USB3

Both of these PCs are connected to a 5 port gigabit switch, which is connected to an Asus RT-ACRH13 router.

Thank you!

 

[bill001g]

Try running the old IPERF program on both machine. It is a really simplistic program that only tests the network it is not affect by memory or disk or even cpu on large machines. You should see about 850-900mbits/sec when they are connected like your are.

Normally I would say you have a 10mbit connection because 11MB is about what you get on a 10mbit ethernet with the overhead. Since it runs faster to the internet then your cables/ports are fine.

If iperf runs good I would supect something in the disk system. Also a large number of small files will transfer much slower than 1 large file. Many times the name of the file and directory take up more room than the file itself, this is especially true when you copy some games that have many thousands of extremely tiny files.

 

[shadowbeh2]

I have found the IPERF program but I am unsure on how to run the tests you are looking for, any tips?

Also, most of the files I am transferring are single large MP4s or MKVs

 

[bill001g]

You just run iperf -s on one end and iperf -c xx.xx.xx.xx on the other where xx.xx.xx.xx is the ip of the machine you used the -s option on. There are many options but the most simplistic test generally will show if you have any issues.

 

[shadowbeh2]

Okay, I seem to have run into an issue.

Running the server side on my Plex box, its sitting with the "Server listening on 5201" message

On the client end i enter "iperf.exe -c *serverIP*" and am met with "error - unable to connect to server: connection timed out"


I have verified that the IP for the server is correctly entered.

 

[My Username]

Okay, I seem to have run into an issue.

Running the server side on my Plex box, its sitting with the "Server listening on 5201" message

On the client end i enter "iperf.exe -c *serverIP*" and am met with "error - unable to connect to server: connection timed out"


I have verified that the IP for the server is correctly entered.

Their system must be down.
https://www.youtube.com/watch?v=ILVfzx5Pe-A

 

[bill001g]

Okay, I seem to have run into an issue.

Running the server side on my Plex box, its sitting with the "Server listening on 5201" message

On the client end i enter "iperf.exe -c *serverIP*" and am met with "error - unable to connect to server: connection timed out"


I have verified that the IP for the server is correctly entered.

Pretty much the only way that can happen especially if you can share files to the same server address is some firewall is blocking iperf. iperf is really stupid it opens a simple tcp session between the 2 ip and transfers data. It is as simple as it gets.

 

[shadowbeh2]

Got it through the firewall, here is what I got on the server end, I cannot currently get the output of the client side as I am at work and my remote connection is not working right now.

Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.50.29, port 50252
[ 5] local 192.168.50.83 port 5201 connected to 192.168.50.29 port 50253
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 11.1 MBytes 93.3 Mbits/sec
[ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 2.00-3.00 sec 11.3 MBytes 94.8 Mbits/sec
[ 5] 3.00-4.00 sec 11.3 MBytes 94.8 Mbits/sec
[ 5] 4.00-5.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 5.00-6.00 sec 11.3 MBytes 94.8 Mbits/sec
[ 5] 6.00-7.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 7.00-8.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 8.00-9.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 9.00-10.00 sec 11.3 MBytes 94.8 Mbits/sec
[ 5] 10.00-10.03 sec 360 KBytes 94.8 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.03 sec 0.00 Bytes 0.00 bits/sec sender
[ 5] 0.00-10.03 sec 113 MBytes 94.7 Mbits/sec receiver
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------

 

[bill001g]

You must have a port that is running at 100mbit rather than 1gbit. Best place to look is in your switch if it has the ability to let you log in. Many switches also have lights. Otherwise you can dig around, microsoft is very inconsistent between software versions where they display the negotiated speeds.

Unless the speed is set to 100m ina end device or your switch can only run 100m the problem is almost always a damaged cable. Only takes a slightly loose cable end on one wire to cause it to drop to 100m.

 

[shadowbeh2]

Okay, I'll swap some cables around and see what that does when I get home

 

[shadowbeh2]

Issue has been resolved. Problem was a combination of wonky switch and some bad cat6 cables.

Thank you bill001g for your help =]