21 replies to this topic

[davebrust]

Hello there,

I recently built a new server and I am experiencing extremely slow transfer speeds between the server and the win7 client.

After I completed the build and got everyone seeing one another on the network I began the process of moving music and pictures over.

The process of moving files to the server seemed adequately fast - although I usually walked away during this process.

Now when I try to access the server from the client through the shared folders the process is painfully slow. Just the task of navigating to the sub-folders takes a fair amount of time then actually trying to open a simple jpg seems to take about a minute of time. Playing music from the server works but it stutters to the point of not being usable.

However, when I accessed the server with my Denon DLNA receiver music played fine....same thing with the Xbox (pictures and music worked fine).

The server is wired to a gigabit router and the laptop is wireless, but I still get the problem even when I give the laptop a wired connection. The receiver and the xbox are wired connections as well.

When I google the issue I get countless entries for a similar problem but nothing has led me to a solution.

I am a bit of a novice when it comes to this stuff so if any other details are needed please let me know.

Thank you,

[jmwills]

There are a ton of factors in the mix here.

• What is your network layout? Most folks here would suggest an internal Gigabit switch to which your internal LAN is connected. Do not rely upon the router to do this.
• Wired or wireless? Wired is better.
• Adequate free space on the client/server. Speaks for itself
• What method are you using to copy files? Copy and paste is horrible. Use something like TerraCopy, RoboCopy, or others.

[jazzerjay]

2011 or V1?

Also, make sure your wireless is turned off on your laptop when going from wi-fi to LAN. (Some do not switch automatically)

Server specs? Drive specs? Hardware vs software RAID? No RAID?

[davebrust]

Okay here is what I am working with:

Server using 2011 software

• Shuttle model SH61R4
• Intel Core i3-2100
• (2) Seagate Barracude ST31000524AS 1TB / 7200rpm / SATA / 6gb/s
• 4GB Kingston HyperX Blu SDRAM

This is wired into a Netgear GS105 Gigabit switch --> then into a Netgear 600

The client computer that I am having trouble with is on a wifi connection using Win7 Home Premium.

Then to answer some of your preliminary questions:

• Plenty of free space on the drives as this is a brand new build.
• Right now I use the copy/paste method. But the real issue is accessing the data on the server after it has been moved over.

Thanks for any help!

[jmwills]

As a baseline test you should test the same systems but with the client wired to the switch. We can start to eliminate some problem areas that way.

[davebrust]

I just wired the laptop to the switch and experienced the same levels of speed. No marked improvement.

[jmwills]

The issue seems to be server side. Try replacing the ethernet cable from the server to the switch. Do you have any other switch you could replace the current one with?

[davebrust]

Seems like a logical conclusion given that when I remote to the server from this laptop I can flip through pictures with a swiftness.

I will snag a network cable and a possibly a spare switch today from work to try that. Thanks for the continued help.

[jmwills]

Hold the phone.....there are two clients involved? One works fine and the other one does not? If so, I'm betting on a bad NIC/driver in one client.

[ikon]

Hold the phone.....there are two clients involved? One works fine and the other one does not? If so, I'm betting on a bad NIC/driver in one client.

Exactly my thought too. When I read, "The client computer that I am having trouble with....", I figured he must have other clients that are working OK.

[davebrust]

Sorry for the confusion....there is only one client computer in the loop. I do have an old XP machine I could introduce, but with all the problems I was having I did not want to introduce new issues. If you think a separate client is the place start next let me know and I will hook it up tonight.

Thanks

[ikon]

It would help in order to divide the problem in two - the basis of all troubleshooting. Is the problem with the client or is it outside of the client? If another client can transfer files OK (using the exact same network connection) then the problem is with the original client. If both clients have problems, then there is a problem on the network of the server.

[jmwills]

Agreed, you need to eliminate the issue by introducing another client. the same issue would point back to either a server issue or network issue.

[davebrust]

sounds like a plan. XP box will get added tonight and I will report back.

[davebrust]

ugg. No fun turning on a PC that has not been fired up in a few years.....spent the night letting it run updates. Then when I finally get to the connector portion it keeps saying there is already a computer associated with that name.

So I rename the XP box and still get the same error.....any thoughts to this one?

[jmwills]

http://titlerequired...1-essentials-2/

I know the article refers to SBSE but the process is the same except for the domain part. Make sure you have .Net 3.5 installed (v 4.0 is not 3.5 inclusive) and both machines are in the same time zone.

Had this XP machine ever been connected to the server before? If so, you will have to rename it.

[ikon]

Just a thought. Might be faster just to reinstall from scratch, maybe with win7, and a completely different name. I wouldn't bother with updates. It's unlikely they will affect the transfer speed, at least not enough to find out if the problem is with the original client or not.

[jazzerjay]

Just a thought. Might be faster just to reinstall from scratch, maybe with win7, and a completely different name. I wouldn't bother with updates. It's unlikely they will affect the transfer speed, at least not enough to find out if the problem is with the original client or not.

I would certainly try this as well. Three ways a server can know a client IMO; MAC address, name (DNS or otherwise) or SID. This seems odd if the two have never met before.

[jmwills]

Renaming it should have given it a new SID. I'd flush the DNS cache on the server also. ipconfig /flushdns

[pest]

Does your server have mulitple ethernet ports? Back in the v1 days one of my ports didn't play nice with WHS. It would connect to all the clients/internet but transfer speeds would be low and it would stutter on video playback. It actually partially corrupted tons of my photos in the transfer process. This was some kind of driver issue I guess, but the easiest fix was moving that ethernet cable 1/2 an inch...