NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Basic USB connection help, R7000
Hello, I have read through a ton of USB-related posts, I'm a slightly computer literate user and cannot find answers in the PDF manual nor in many, many threads RE USB connection issues. So I ask, a...
Morels wrote:I do not have SMBv1 enabled on my windows 10 machine, (ver 1809, build 17763.615) and I have no problem connecting to the R7000.
Wthout the SMB 1.0/CIFS Client feature, there is no NetBIOS name resolution and no NetBIOS based discovery. Netgear has still not implemented WS-Discovery which would substitute this requirement.
Morels wrote:But if I try to network an old XP machine, I get an error meassage that specifies the SMBv1 issue.
No idea what SMPv1 issue you talk about - show a message, a screenshot, whatever.
XP is - with a few exceptions - for embedded solutions dead and no longer maintained for consumers, updates are not available to the public anymore.
Morels wrote:Perhaps Netgear has addressed the SMBv1 issue with firmware updates. I have no idea how to check which SMB version the R7000 is using.
Some routers have got SMB 2.x and SMB 3.0 transport protocol. However nothing that does supersede NetBIOS. Thus \\[IP-address]\ and \\[IP-address]\[sharedfolder] can work, but nothing that requires a name resolution like \\readyshare or ping readyshare ...
Morels wrote:It all works, clumsy though. My reason for posting was to find out if it is clumsy by design, which now I see that seems to be the case. In addition, I hoped to put some info out there for others of my level in network skills, that is, not much. I had no idea what \\readyshare means, and I don't think I am alone in that.
\\readyshare does address a host announced on the network (or in business environments \\[servername] it's DNS) named readyshare - or whatever the Nighthawk owner might have configured - accessing it form an application does call for the enumeration of the available shared folders.
There should be no network skills required. It's not a secret that I don't agree with the absent WD-discovery on the Netgear consumer devices (in place e.g. on ReadyNAS OS 6) - making noise almost every week again (if not every day). This is what makes the installation of the Windows 10 SMB 1.0/CIFS feature mandatory - it was removed from existing Windows 10 installations if not used for a certain time, or isn't installed on new scratch installs of current Windows 10 systems - when you expect the full functionality on your Nightawk router ReadyShare feature for your Windows 10 system(s).
Thank you Schumaku
My R7000 shows an icon in Network folder, not in This PC.
But clicking the icon only brings up the router login page, and then the control interface, even with a USB dsrive plugged into the router.
Firmware: V1.0.9.88_10.2.88
If there is a USB device plugged in, then it is possible to access using \\R7000, (manual could have said \\router model, would have saved me a lot of time.) Or I can use the share name of the drive, \\share name.
If there is no drive plugged in, then computer will not connect.
I do not have SMBv1 enabled on my windows 10 machine, (ver 1809, build 17763.615) and I have no problem connecting to the R7000.
But if I try to network an old XP machine, I get an error meassage that specifies the SMBv1 issue.
Perhaps Netgear has addressed the SMBv1 issue with firmware updates. I have no idea how to check which SMB version the R7000 is using.
It all works, clumsy though. My reason for posting was to find out if it is clumsy by design, which now I see that seems to be the case. In addition, I hoped to put some info out there for others of my level in network skills, that is, not much. I had no idea what \\readyshare means, and I don't think I am alone in that.
Thanks again
Morels wrote:I do not have SMBv1 enabled on my windows 10 machine, (ver 1809, build 17763.615) and I have no problem connecting to the R7000.
Wthout the SMB 1.0/CIFS Client feature, there is no NetBIOS name resolution and no NetBIOS based discovery. Netgear has still not implemented WS-Discovery which would substitute this requirement.
Morels wrote:But if I try to network an old XP machine, I get an error meassage that specifies the SMBv1 issue.
No idea what SMPv1 issue you talk about - show a message, a screenshot, whatever.
XP is - with a few exceptions - for embedded solutions dead and no longer maintained for consumers, updates are not available to the public anymore.
Morels wrote:Perhaps Netgear has addressed the SMBv1 issue with firmware updates. I have no idea how to check which SMB version the R7000 is using.
Some routers have got SMB 2.x and SMB 3.0 transport protocol. However nothing that does supersede NetBIOS. Thus \\[IP-address]\ and \\[IP-address]\[sharedfolder] can work, but nothing that requires a name resolution like \\readyshare or ping readyshare ...
Morels wrote:It all works, clumsy though. My reason for posting was to find out if it is clumsy by design, which now I see that seems to be the case. In addition, I hoped to put some info out there for others of my level in network skills, that is, not much. I had no idea what \\readyshare means, and I don't think I am alone in that.
\\readyshare does address a host announced on the network (or in business environments \\[servername] it's DNS) named readyshare - or whatever the Nighthawk owner might have configured - accessing it form an application does call for the enumeration of the available shared folders.
There should be no network skills required. It's not a secret that I don't agree with the absent WD-discovery on the Netgear consumer devices (in place e.g. on ReadyNAS OS 6) - making noise almost every week again (if not every day). This is what makes the installation of the Windows 10 SMB 1.0/CIFS feature mandatory - it was removed from existing Windows 10 installations if not used for a certain time, or isn't installed on new scratch installs of current Windows 10 systems - when you expect the full functionality on your Nightawk router ReadyShare feature for your Windows 10 system(s).
Thanks, your replies as well as the others have given me plenty of homework. I do think the Netgear people could make it easier for a non-technical person to use their routers. But from my position, it is hard for me to judge their decisions. Some of you are better positioned to do so, I hope Netgear listens.
As for the SMBv1 issue, that is where my USB questions started. I was using an old XP machine for storage on my local network. I started to have connection issues, and it was the SMBv1. Seems that some releases of windows10 were disabling the protocol. The laptop wouldn't connect anymore, but the PC would. Explored the problem online, and I got everything back to working. But, I learned that maybe I shouldn't enable the SMBv1 anyway. Which led me to explore the option of connecting some storage to the R7000, something I had never even tried. Now that I know a bit more, I see it as an option. It was hard though, and made me think something was wrong with the router.
My initial question has been answered more than well enough.
But you asked me about the SMB error message, so here it is.
Now that I have disabled SMB1, I can no longer connect to the XP machine, see photo, windows10 doesn't think it is a good idea.
That is the error message.
I am not really sure how dangerous it is, but until I learn more, it remains disabled.
There are a few things tied to SMB 1. Absence can cause a host of problems, for all Windows PC's connected to a LAN.
SMB 1 works with the Master Browser and Computer Browser Service. Once that is 'broken' with no SMB 1 running, other Window's PC's usually will fail as well. It is actually reliant on what PC was turned on first sometimes even. You can Google these for more info if you wish to know more. Some to look at:
This one is even better:
http://woshub.com/network-computers-not-showing-windows-10/
However, that REQUIRES WSD to be running as the SHARE discovery method. Look at my Screen Capture on the upper left of this post. It is looking at my network and the discovery methods. Note the PC's use WSD (both are W10 with SMB 1 enabled.
As for SMB 1, WannaCry virus attacked the SMB Server. Also today most if not all Security suites protect against that too, but for safety only the SMB 1 Client should be enabled. Still, SMB 1 is considered a risk to run. However even MS said if you need it, enable it, for Network useability.
See https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Stop-using-SMB1/ba-p/425858, and from it:
=============
Explorer Network Browsing
The Computer Browser service relies on SMB1 in order to populate the Windows Explorer Network (aka "Network Neighborhood"). This legacy protocol is long deprecated, doesn't route, and has limited security. Because it cannot function without SMB1, it is removed at the same time.
However, some customers still use the Explorer Network in home and small business workgroup environments to locate Windows computers. To continue using Explorer Network, you can perform the following steps on your Windows computers that no longer use SMB1:=====================
