Question NAS Running Horrendously Slowly, Only from One Machine Though

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
kanewolf said:
This thread has gone so long, I have lost some memory ... Have you booted a portable Linux and tested ? That is the only definite way to eliminated a Windows issue.
Click to expand...
If rebooting the machine resolves the issue, rebooting into Linux doesn't prove much of anything, but yes.

I couldn't type in the IP into the File Manager, but I was able to navigate to the NAS through the navigation bar on the left of the File Manager, and it all worked fine. I was also able to mount it from the terminal. But again, a fresh Windows boot is also fine, although I'm not sure how long for, so it's difficult to say whether the Linux boot working means Linux is fine or just that fresh boots are always fine.

WinSCP access to the NAS works just fine. YouTube has become unusably slow, with videos hanging entirely midway through. I'm at a loss here.
 
And nothing seems amiss in Task Manager, Resource Monitor, Process Explorer, Task Scheduler, Reliability History, and Event Viewer?

No log entry or event that occurs just before the issue returns and you are forced to reboot?

This:

"I couldn't type in the IP into the File Manager, but I was able to navigate to the NAS through the navigation bar on the left of the File Manager, and it all worked fine."

Go through the process you use and take some screenshots. Post the screenshots here via imgur (www.imgur.com). What IP Static IP addresses are assigned to the NAS(s)?
 
Event viewer has a lot of these under Applications/Microsoft/Windows/SMBClient/Connectivity:
A network connection was disconnected.
Instance name: \Device\LanmanRedirector
Server name: [ServerName]
Server address: [IP Address]:445
Connection type: Wsk
InterfaceId: 17
Guidance:
This indicates that the client’s connection to the server was disconnected.
Frequent, unexpected disconnects when using an RDMA over Converged Ethernet (RoCE) adapter may indicate a network misconfiguration. RoCE requires Priority Flow Control (PFC) to be configured for every host, switch and router on the RoCE network. Failure to properly configure PFC will cause packet loss, frequent disconnects and poor performance.
Click to expand...

And these, under Applications/Microsoft/Windows/SMBClient/Security:
The SMB client failed to connect to the share.

Error: {Access Denied}
A process has requested access to an object, but has not been granted those access rights.

Path: \[IP Address]\[Share]
Click to expand...

Both errors are present for both NAses.

Also this under Connectivity:
The server name cannot be resolved.

Error: The object was not found.

Server name: .sync

Guidance:
The client cannot resolve the server address in DNS or WINS. This issue often manifests immediately after joining a computer to the domain, when the client's DNS registration may not yet have propagated to all DNS servers. You should also expect this event at system startup on a DNS server (such as a domain controller) that points to itself for the primary DNS. You should validate the DNS client settings on this computer using IPCONFIG /ALL and NSLOOKUP.
Click to expand...

Reliability Monitor shows a lot of "Stopped working", mostly just background update processes (Java, Windows), but also something called "Trafsvc service".

Ralston18 said:
"I couldn't type in the IP into the File Manager, but I was able to navigate to the NAS through the navigation bar on the left of the File Manager, and it all worked fine."

Go through the process you use and take some screenshots.
Click to expand...
Not sure the benefit of this? As I said a clean Windows boot works fine, so how I'm accessing it in Linux doesn't seem super helpful.

Ralston18 said:
What IP Static IP addresses are assigned to the NAS(s)?
Click to expand...
192.168.0.2 and 192.168.0.171.
 
A network connection was disconnected.
Instance name: \Device\LanmanRedirector
Server name: [ServerName]
Server address: [IP Address]:445
Connection type: Wsk
InterfaceId: 17
Guidance:
This indicates that the client’s connection to the server was disconnected.
Frequent, unexpected disconnects when using an RDMA over Converged Ethernet (RoCE) adapter may indicate a network misconfiguration. RoCE requires Priority Flow Control (PFC) to be configured for every host, switch and router on the RoCE network. Failure to properly configure PFC will cause packet loss, frequent disconnects and poor performance.
Click to expand...

This is INTEL server grade NIC's feature, how would Windows 10 recognize your Killer E2200 as high performance server grade NIC and try to use the feature is beyond me.

https://www.intel.com/content/www/u...technology/ethernet/rdma-resource-center.html
 
Last edited:
Apparently Killer E2200 does not have this feature yet Windows 10 tried to use it so it causes poor performance, as pointed out by the Event Viewer.

Or see if Killer E2200 has wrong RDMA property that you can disable

https://imgur.com/a/OHunGoY
View: https://imgur.com/a/OHunGoY


Also reset Windows Networking see if works. if not, I have mentioned what to do before.

www.action1.com

How to Quickly Reset the Network Settings of Windows 10

A new way to reset network settings, as well as network connection settings in Windows 10 when you have problems with the Internet and local network
www.action1.com www.action1.com
 
Last edited:
lantis3 said:
if not, I have mentioned what to do before.
Click to expand...
You mean uninstalling the Killer driver? I still have no idea how to do that, the only Killer thing I can find listed on my system refuses to uninstall via the Control Panel.

Resetting the network requires resetting the computer, so that's again going to take some time to figure out if it works or not. Blegh.
 
Uninstalling the driver will not delete driver files. Reboot Windows and it will be re-detected and reinstall the driver. Reset the network also will not reset Windows.

52XdaE3.png


Buy a new NIC then if you don't want to do either step.

https://www.amazon.com/Cudy-2-5Gbps-Express-2-5GBase-T-PE25/dp/B08L8PK1SF

I have done my best. You make your choice.
 
  • Like
Reactions: Ralston18
lantis3 said:
Reset the network also will not reset Windows.
Click to expand...
I meant to say reboot, not reset, with regards to Windows. It's just a pain because it's obviously going to work in the short term, as rebooting Windows works all by itself, without resetting the network.

Nonetheless, I did the network reset and it broke again almost immediately. I have a Blu-ray on my NAS with an unneeded audio track, that I'm trying to remove using MKVToolnix, and doing so seems to lock the entire NAS up. I'm wondering if it's something to do with MKVT, or with that specific file, or a mix of both...it's obviously having knock-on effects if so, because it's also affecting the other NAS, but there seems to be some sort of interaction there. Either way, it definitely seems like it's currently functioning as a "break everything immediately" button, which is useful for troubleshooting if nothing else.
 
The fact is this Killer NIC is buggy since it's released years ago. You can find the complaints all over the internet.

Just buy a new NIC and be done with it, at least on the Windows side. Whether you still have other issues on the NAS is a different story.
 
lantis3 said:
The fact is this Killer NIC is buggy since it's released years ago. You can find the complaints all over the internet.

Just buy a new NIC and be done with it,
Click to expand...
I don't have a separate NIC currently, ethernet is connected directly to the motherboard, which is a Gigabyte G1 somethingorother, I think.
 
@koberulz:

When you copy and paste the various Event Viewer errors etc. are you editing out any information? If so, do not do so, At most mask out the last few letters of the computer or server name if you believe that those names could be personally identifying.

The reason for screenshots is to ensure that what is being done is 1) applicable to the the overall described network environment, and 2) correct for that environment. Typo's are notoriously hard to notice sometimes.

As for the NAS static IP addresses, they can be as you chose provided that the chosen static IP's are outside of the DHCP IP address range allowed to the router and that each assigned NAS static IP address is reserved for the NAS via the respective NAS's MAC. I would use 192.168.0.2 (already in use - ok) and 192.168.0.3 (if not in use) for the second NAS. Makes the NAS IP addresses easy to find and/or identify when problems occur.

Key is to have some consistent IP addressing scheme in use with respect to the use of DHCP and Static IP addresses.

I use a scheme that allows me to recognize what a device may be: major network component, shared, wired, wireless. Apple "i" device, camera, misc (electrical system monitor), guest.

You really need to have an overall network diagam that shows all network devices, their connectivity, IP addresses (DHCP/Static), MAC's etc.. And then use "ipconfig /all", "arp -a" etc. to confirm that all is correct. And also look in the router's admin screens/menus or device lists to ensure that all is consistent - no duplicates.

That all said, at this point I believe that @lantis3 is narrowing this all down. My suggestion is to order the other NIC, wait the week+ (if necessary), and then proceed as posted.

Indeed the problem may be related to "Killer's" long history of issues. However, that is likely being complicated by misconfigurations and/or other errors and problems with respect to network devices.

The problem is in your network and all we can do is to try to help by guiding and suggesting. You must be much more proactive on your end with respect to trying to resolve the issues at hand. And that can be quite frustrating - no easy answers sometimes.

If you do not understand something then start googling and reading. E.g., how to disable or uninstall a device driver. Check end user documentation via the applicable manufacturer's websites.
 
I'm wondering if this actually has nothing to do with networking at all. I just connected an external USB drive with video files on it, ran ffmpeg, then suddenly got an error about the disk "not being ready" because "maybe the door is open" or something. The Windows Explorer window in which I have the root of that drive open simply says "Working on it..." instead of listing any files and folders, with the green bar sloooooowly moving across the address bar. Like, it's been half an hour and it's still not there yet. Even completely unplugging the drive hasn't changed anything, it's still "Working on it..." and hasn't even thrown a "this drive doesn't exist anymore" error.
 
Attempting to interact with that Windows Explorer window locked up my entire computer, necessitating a reboot. Now I'm getting a "Microsoft OneDrive is restarting..." dialogue ever few minutes.
 
So I replaced the network card, and a port I had forwarded is no longer forwarded. It gave the new network adapter a different IP, but even changing the IP of the port-forwarding rule in the router hasn't opened the port up. Not sure what else could be going on.
 
Starting over.

Make and model information for modem, router, and new network card.

Who has full admin rights to the router?

First, run "ipconfig /all" (without quotes) via the Command Prompt. Copy and paste the full results into your next post.

Second, provide more information about the port-forwarding that is being attempted. Details?

Third, take some screenshots of the router's port forwarding pages. Post the screenshots here via imgur (www.imgur.com).

Fourth, are there still OneDrive related errors/problems? If so, what error messages, pop-up windows etc. are being presented. Screenshots?
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom