Extremely slow performance ONLY on my Macbook Pro (Mavericks)

Hi guys,

I recently just installed my 2TB My Cloud and seem to be only getting poor performance on one of my computers. I have an older computer running Win XP via wifi that transfers files incredibly fast, as well as a 2010 Macbook Pro that also handles file transfers via wifi relatively quickly. However, I have a new 2013 15" i7 Macbook Pro with 16 gigs ram that just seems barely handle transfers at all. Both Macbooks are running Mavericks, however, the 15 inch takes FOREVER to transfer data via wifi. It took five days to do a 34 gig Time Machine backup. I have no idea what the problem could possibly be. Both macs are running the same exact OS, but the newer one is transferring at around 10 kb/s at the slowest, however I’ve gotten it up to almost 1 mb/s occassionally. Regardless, the 15 inch Macbook is ridiculously slower at transfers than any of the other computers. I should mention that these are all within my home network, no external access.

Router Model: Actiontec C1000A

I have the WD MC plugged directly into my router/modem and am accessing it via wifi on my home workgroup.

What I’ve tried:

-SMB via “go to server” in finder

-Transferring via the My Cloud app

-Forcing SMB over AFP in finder

-Different LAN port on wifi router

No difference with any of those methods.

I don’t think this is a problem with the My Cloud itself because all of the other computers in the house seem to read/write to it just fine and I don’t have any other issues with my Macbook’s wireless functionality either. Any ideas? Thanks in advance!

There could be a problem with the NIC of that computer when wireless. If so then that’s a physical problem.

Test it out by connecting the MC via ethernet.

1 Like

Thanks for the response. I actually thought this may be the issue so I tried running my Windows 7 Boot Camp partition and, low and behold, everything worked completely normally. From all of this, it just appears to be a Mavericks issue because I’ve pretty much ruled out hardware as the culprit at this point. I’m just not sure where to go from this point.Â