RND4000 WIn 10 Unexpected Network error

[kohdee]

---

@Andy_Larkins wrote:

Jumbo frames on the W10 machine are currently disabled.

---

Then you should not have Jumbo Frames enabled on the NAS. 

ReadyNAS would try to send you packets that are 9000 but since Windows is 1500, the ReadyNAS'll have to resend the packets until they fit the 1500 window size. 

Turn off jumbo frames on the NAS. They were really useful in slow networks but not as much anymore. 

[StephenB]

---

@kohdee wrote:

I don't have a RAIDiator box near me but if you use the UI to download the set of logs, then it should be there. It would either be called smbd or samba or smb.log. Maybe even something with "cifs"

---

It is smbd.log

Click on the status choice on the frontview home screen, then logs.  Download all logs is a link on the top right.  Be patient, it takes a while for the download to start (the NAS collects and zips the log files).

[StephenB]

---

@kohdee wrote:

---

@Andy_Larkins wrote:

Jumbo frames on the W10 machine are currently disabled.

---

Then you should not have Jumbo Frames enabled on the NAS. 

---

Kohdee is of course correct.  You want to match the ethernet frame size across your local LAN.  

So JF should be off if:

-you have a mix of fast ethernet and gigabit

-the nas connects to some equipment that doesn't support JF

-JF is turned off in some equipment.

Otherwise you either end up with packet fragmentation or (or as Kohdee says) packet retransmission.  Both are bad, so you want to avoid them. 

---

@kohdee wrote:

---

Turn off jumbo frames on the NAS. They were really useful in slow networks but not as much anymore. 

---

I basically do agree, and there are cases reported here where turning on JF actually reduced performance.

Its not really about the speed of the network though (JF is only for gigabit).  Its about the speed of the devices that connect to the network.  Every packet generates an interrupt and creates some processing load on the devices.  When jumbo frames help, it is because they are reducing the CPU load on the devices.  They don't help the network performance overall, and in some ways they actually hurt it.

Devices get faster over time (so the packet rate doesn't load them down as much), and modern NIC cards can do more on-board processing, which helps off-load the main CPU.  So the performance gain is not as important as it used to be.

So it makes sense to test your performance both ways (on and off) before you commit to them.

[Andy_Larkins]

JF not enabled on NAS

[Andy_Larkins]

Have to step out a bit but will setup a new share and try that tonight.  Im EST US.  Thx

[Andy_Larkins]

Setup new Share called Test.

Same System Error 58

[Andy_Larkins]

[Andy_Larkins]

Tried NEt use on new share without a user name and got prompted with the 3 certs.  Selected 1 and got error 58 again

[BrianL2]

Hi Andy_Larkins,

Thanks for this screenshot and the other details that you have provided. Could you tell us the exact OS version of this computer? Also, you haven't answered if the PC network ID is in a WORKGROUP or Domain.

Kind regards,

BrianL
NETGEAR Community Team

[Andy_Larkins]

Thanks to all of you for continuing to help me dig through this.

The computer is not part of a domain

Workgroup ID on both the NAS and the Laptop is "WORKGROUP" 

Hardware: Laptop is a Lenovo Y50-70

OS version is Win 10 Home ver 1511 OS Build 10586.71

[StephenB]

Did you try "net use" with admin credentials?

net use t: \\192.168.1.2\C /user:admin nasadminpassword

Reboot first if you are nervous about the net use * /delete.  Also, log in with your password, not PIN.

[Andy_Larkins]

Logging in with PW.  I never set a pin up.

Tried command prompt run as administrator this time

net use t: \\192.168.1.2\Test /user:admin password

That generated a system error 58

[StephenB]

---

@Andy_Larkins wrote:

Logging in with PW.  I never set a pin up.

Tried command prompt run as administrator this time

net use t: \\192.168.1.2\Test /user:admin password

That generated a system error 58

---

If you are using user mode security, try 

net use t: \\192.168.1.2\C /user:admin password

The "C" was intentional, it should map the entire data volume (and requires administrator credentials).

[Andy_Larkins]

Welp - I tried another W10 pc and it connected no problem.

Obviously something is jacked up with this software load post last Windows Update.

Im entertaining a full re-load as this laptop will be with me a while.

UGH

[Andy_Larkins]

net use t: \\192.168.1.2\C /user:admin password generated a system error 58

[BrianL2 · Accepted solution]

Hi Andy_Larkins,

It seems like that's our best hope of resolving this problem. Clearly, not a problem with your ReadyNAS.

Keep this thread updated on what happens.

Kind regards,

BrianL
NETGEAR Community Team 

[Andy_Larkins]

Did A windows 10 "RESET THIS PC" which returned the laptop to original W10 load then stepped through the updates.  It found the NAS immediately.

Sorry to kick this thing in circles this long but....W10 will with with RND4000 there is no doubt.