crisscross

Extremely Slow Network Browsing

8 posts in this topic

I have this strange problem where my network slows down to a crawl whenever I access my WHS files using Windows Explorer. I also have Windows XP installed and when I use Windows XP opening a network folder is no different from opening a local folder.

The PC is connected to a wireless router through a Network cable.

Any suggestions?

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

I have this strange problem where my network slows down to a crawl whenever I access my WHS files using Windows Explorer. I also have Windows XP installed and when I use Windows XP opening a network folder is no different from opening a local folder.

The PC is connected to a wireless router through a Network cable.

Any suggestions?

**************

Can you provide more detailed information about your network setup

and your WHS/PC hardware? That would be helpfull in helping you diagnose

your problem.

Share this post


Link to post
Share on other sites

Garry: Thank you for your reply.

I have a Buffalo Router WHR HP-G54.

The WHS runs on a AMD Sempron LE-1250 Processor and onboard Gigabit LAN. HD's are a WD and Samsung green drives.

The Windows 7 Machine is a Core i7860 processor with a Gigabyte motherboard connected through onboard LAN.

As mentioned, it's really fast on Windows XP on the same machine but Windows 7 really crawls and I think it might be a driver or settings issue?

Link to MotherboardGA-MA74GM-S2

Share this post


Link to post
Share on other sites

Can you clarify what version of WHS? ie WHSv1 or WHS 2011. Also

are you by chance using an advanced format WD drive with WHSv1

and if so have you jumpered pins 7/8 ? If you are using an advanced

format drive as your OS drive, that will cause many problems and

is not supported by MS.

Outside of the drives. Be sure to update your NIC drivers with the

latest.

1 person likes this

Share this post


Link to post
Share on other sites

Can you clarify what version of WHS? ie WHSv1 or WHS 2011. Also

are you by chance using an advanced format WD drive with WHSv1

and if so have you jumpered pins 7/8 ? If you are using an advanced

format drive as your OS drive, that will cause many problems and

is not supported by MS.

Outside of the drives. Be sure to update your NIC drivers with the

latest.

Hi Garry,

Thank you for your reply. I think I solved the problem. It was the NIC drivers. :) Windows 7 detected my NIC and I didn't bother checking the motherboard manufacturer's site as I figured Windows Update would take care of it.

Thank you for pointing me in that direction. I am running WHS1 and while I am using advanced format drive, I am not using them for the OS drive.

Speeds are much improved now, and now I can finally watch movies on the network and also burn CD's without having to first copy them over to my desktop.

Share this post


Link to post
Share on other sites

Hi Garry,

I realize this thread is over a year old, but I still wanted to thank you for suggesting updating the NIC drivers. Just like crisscross, I checked the device driver version (by clicking the "Update Driver" button in device manager), but Windows informed me I was on the latest and greatest. I then went to the Realtek website and found that the latest version was much more recent. After downloading and installing that driver, the gridlock I was experiencing when moving, copying or opening files on my WHS 2011 server was resolved.

Thanks again

mrwassen

Share this post


Link to post
Share on other sites

Chalk up one more in 2014! I use Win 7 Ultimate and WHS 2011 with a hardwired connection. I was able to use the update in device manager on my Realtek NIC and it worked great. Went from like 13KB/s and lots of "not responding" messages to 20MB/s and no messages. I wish all bugs were this easy to fix! :)

Share this post


Link to post
Share on other sites

Live2Surf, 

 

Yeah, Realtek drivers are .... crap.

 

Also, for performance, check my signature. It will also help.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • Dave, can you clarify what you mean by this?
    • I had no problem with Windows 10.  However, I just completed the anniversary update and now the "Connector" won't run to conclusion.  It backs itself out and reports an unspecified error.
    • Apologies if I'm being stupid, but I'm having great trouble understanding how Lightsout backup and the Server Essentials 2012 backup work together (or fight with each other). I find the Lightsout documentation on this very unclear, and various threads have left me no wiser. I'd appreciate some help! Here's the setup: Lightsout is running nicely on the server. Before backups were set up, I established that the server hibernated when the clients were switched off. The server woke up when a client was powered up. (This behaviour broke when backups were set up.) The server is Essentials 2012, with a number of client laptops: a mix of Windows 7, 8 & 10. The Essentials backup window is 22:00 - 07:00. No backup settings are currently made in Lightsout. Here's what I'd like to achieve: At the end of the working day all the clients are put to sleep or hibernate (or switched off completely, I don't care which). Ten minutes after that, Lightsout hibernates the server. Sometime during the night (22:00 - 07:00) the server wakes up, then wakes up the various clients in turn, backs them up, and puts them back to sleep / hibernate / shutdown (I don't care which). Here's what actually happens (when I look at the uptime chart the next morning): At the end of the day (about 17:15) the clients are put to sleep / hibernate. (I tell the team not to shut down their client laptops because I assume the server can't wake a completely shut down client - is that correct?) The server does not hibernate. Approximately 90 minutes after the clients were put to sleep / hibernate, they all wake up simultaneously (around 18:45, but I don't know why this happens). The clients then stay awake all night. Later, from 22:00, some of the backups take place (but not all of them). The backups are spread wide apart in the 22:00 - 07:00 window with lots of time when nothing is going on at all. The clients do not go back to sleep / hibernate after their backups. ...can anyone suggest what combination of settings I should be using to get the desired behaviour? Here are the sort of things that are confusing me, but I can't find definitive answers (and each experiment I do takes 24 hours to give any results!): I know I can specify clients' individual backup times in Lightsout, but I don't know how long a client's backup will take, so I could have backups overlapping each other and causing a traffic jam. Should I worry about this? If I set Lightsout backups, what do I set for the Essentails backup window? What if it's not long enough to get all the backups done? If I make settings in the Lightsout backup dialog do I have to complete everything in that dialog box? Does this make the Essentials 2012 backup settings redundant? What about the Essentials 22:00 - 07:00 backup window, does that matter any more? I tried setting client backup times in Lightsout with an end action of 'sleep'. The backups didn't happen at all and clients all spontaneously went to sleep in the middle of the working day (the server / clients clocks all match, I checked). Can Lightsout wake up a client laptop that is completely shut down? Thanks for reading this long post and sorry if these seem like stupid questions. I already have WHS2011 / Lightsout running perfectly on another setup (where my backups take place during the day), but nocturnal backups are a new level of complexity for me!
    • Christopher wrote:  << And to clarify, if you want multiple backup drives to be cycled offsite, you MUST connect all of them at the same time when you set up the backups. >> I'm not clear about this. To the best of my recollection, I never connected both of my backup drives to the server at the same time,  For test purposes, I just initiated a recovery (using the WHS Installation Disk) with each of them hooked up.  The one that has been offsite and the one that backed up last night were both found by the "Repair an existing installation" procedure.  Perhaps I'm misreading your clarification.
    • Please check if task scheduler is still working. If not use this tool here https://repairtasks.codeplex.com/ If that does not help you may try to reinstall WHS Connector.
  • Popular Contributors