NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Morels's avatar
Morels
Aspirant
Jul 20, 2019
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...
  • schumaku's avatar
    schumaku
    Jul 21, 2019

    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).