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, first, forget about NG doing ANYTHING about SMB1 or WSD to make Router USB drive sharing easy. I went round and round for almost a year documenting, detailing, teaching support about the problem. Common response back, it is an MS problem. Eventually they came around to understanding the problem. Final answer, they are NOT in the Spec and therefore will not be implemented. Again I proved they were exposing the USB share using NETBIOS and that requires SMB1 which has be 'depricated' by MS as it is a security exposure.
So, with that said, you have to use SMB 1 Client in order to see the share. And it must be on ALL PC's otherwise Computer Browser function will not work.
There are a lot of threads here on this problem, SEARCH SMB 1 USB in the forum. Some you might want to read:
Basically you need to enable SMB 1 Client. If you do that and open a CMD prompt and enter NET VIEW you'll see this for the router if you used the DEFAULT Router and Sharename for the USB drive:
==============
C:\>net view
Server Name Remark
-------------------------------------------------------------------------------
\\IRV8700 Irv's 8700
\\READYSHARE readyshare
The command completed successfully.
==============
If you get an ERROR, you do NOT have SMB 1 Client enabled.
Once you do that you can use NET VIEW \\READYSHARE and you'll see the main folder for the USB drive:
-------------------
C:\>net view \\readyshare
Shared resources at \\readyshare
readyshare
Share name Type Used as Comment
-------------------------------------------------------------------------------
Movies Disk read:all-no password;write:all-no password
USB_2.0_Storage Disk read:admin;write:admin
The command completed successfully.
----------------------
Lastly can do NET USE to assign a drive letter to \\READYSHARE\SHARENAME where SHARENAME is the Share Name you set, MOVIES or USB_2.0_STORAGE in my case.