NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
radon85
Dec 14, 2019Guide
Readyshare not working Windows 10.
I'm tired of waiting on the SMB1 fix. Am I missing something or wouldn't it be easier if Netgear simply added support for an additional user (other than guest and admin)?
radon85
Dec 18, 2019Guide
I would keep it at 2 levels of access; i.e. root and non-root, where non-root supports "user"/pw. And while I have no interest in guest access, I expect Netgear would likely continue to support it for backward compatibility; i.e. users could connect with "user"/pw -or- if they're not running into the SMB1 guest issue, they could connect using "guest" without password.
Thanks for the links, once this thread goes dormant I'll go ahead and submit something and we'll see what happens.
I have little concern regarding the "user" password being leaked; i.e. it's simply a replacement for the guest access which does not have one.
However, having said that, I would still like to be able to set the user password and be able to disable the "guest" access; i.e. while a shared password is poor security, I'd consider it a step above no password.
IrvSp
Dec 18, 2019Master
You are STILL confused over SMB 1 and Guest it seems:
radon85 wrote:if they're not running into the SMB1 guest issue, they could connect using "guest" without password.
There is NO 'guest' and SMB 1 problem. Read the links I posted about this above. This is for access to a Windows Server that it was changed.
The 'Guest' SSID can access the USB drive IF given LAN access, not just Internet (via a router setting), but due to Windows 10, will need to be running SMB 1. Another thing, once any W10 PC connects to your LAN, if they are not running SMB 1 as well, you may lost Sharing capability with the router and other PC's... just the way that MS has created the problem with depricating SMB 1 while some installations of W10 require it and the Computer Browser operating with NETBIOS.
- radon85Dec 18, 2019Guide
I've read them plenty. Would you prefer "deprecated SMB1 guest issue", or how would you prefer I concisely phrase the root cause?
- radon85Dec 18, 2019Guide
Hmm, I just noticed you again said "Guest" SSID. So again I must repeat that I'm not interested in the Guest SSID. I'm simply refering to the "guest" account with no password that is used to access readyshare over the LAN; i.e. hardwired ethernet; no wireless involved.
- IrvSpDec 18, 2019Master
'Guest' and 'SMB 1' have no concept of any relationship or problem in what you were asking for.
Guest means 2 different things in this discussion.
- Guest is a set of 2 or 3 SSID's depending on the router that can be isolated from the LAN if one wishes.
- In Windows parlance it is a PC that can connect to a Server without credentials and have some level of access.
You are confusing #2 with a problem that doesn't exist on the router. Probably because SMB 1 must be running on the Client device in order to use shares from the router.
- radon85Dec 18, 2019Guide
I'm glad you understand that I am talking about #2; the Windows 10 clients are not running SMB1.
As you state "Probably because SMB 1 must be running on the Client device in order to use shares from the router."
However, these clients do connect when using the admin/pw credentials. They only fail to connect when using the guest UID with no password. The lack of SMB1 does not appear to affect the admin access. Thus, your above statement appears to only be about SMB1 and guest access.
The issue you had earlier seemed to be with my verbage of "SMB1 guest issue". Since even your above statement clarifies the issue by mentioning SMB1, I assume there is some symantic change you'd like to see when referring to this particular problem.
So I'll again ask if you have some other concise phrase you would prefer to see when refering to #2 as the root cause of the failed guest logins?
For example, "deprecated SMB1 guest issue"; i.e. this conveys the fact that the issue was caused by the deprecation of SMB1 in Windows 10.
- DawngJan 05, 2020Aspirant
I enabled SMB1 in windows features on the Windows 10 laptop and now I can see all my network computers again and the readyshare. I mapped the readyshare drive. It all works great. I'm using the readyshare on an AC2100 router that is running as a AP. My main router is R8000P.
- radon85Jan 06, 2020Guide
Dawng, Thanks for your response. Yes you can do that, but it does open you up to security issues. The point of this thread is to collect input on an alternate solution that I believe would be easy for Netgear to implement. Then based on the feedback, I plan to submit a proposal soon.
- DawngJan 07, 2020Aspirant
I understand that it's a security risk. I would love to find an alternate way to accomplish this but after wasting the whole day searching and trying people's ideas I had to get into my harddrive. I was trying to help other desperate people. Of course I could have pulled it off the router and plugged it into a computer, which is where I used to have one before I thought this way would be a good idea. I guess I picked up the wrong thread. Thank you for understanding.
- IrvSpJan 07, 2020Master
radon85 wrote:The point of this thread is to collect input on an alternate solution that I believe would be easy for Netgear to implement. Then based on the feedback, I plan to submit a proposal soon.
I guess you miss the point of the responses here too? See mine starting @ 2019-12-16 03:59 AM for instance.
I went round and round with Netgear Support on this issue for many many months. Even with the Moderator's here. Support would close my case often stating the router was working correctly. Moderator's would re-open it, and the same circle of comments with the same result. FINAL result (the point I gave up at after months of this):
- NG routers ARE running SMB 3 (mostly).
- SMB 3 alone doesn't 'cut it', they have to be exposed to the LAN (read that as WSD must be implented as well in the router).
- For the R7000 and R8000 at least WSD is not implemented. Only sharing method is NETBIOS which requires SMB 1.
- There is NO design for WSD in some routers.
- Support will not IMPLEMENT WSD in those routers without a design and spec for it.
- NG will not design and spec. WSD for those routers that do not have it.
- They WILL buy back MY router IF under the 1 year warranty (to make me go away I guess).
- NG is NOT alone in this situation. Probably all other routers produced before MS deprecating/removal of SMB 1 have this same problem.
- Some MFG's have PUBLICALLY stated you MUST run SMB 1 with the router they sell.
If you think you can do better, go for it, but I would expect to be able to 'move a mountain'. As it stands now, NG is removing functions from the routers that sort of make the USB port an artifact. No TIVO, DLNA, or TIME MACHINE support. Some MFG's also have removed the Printer from being used with the USB port.
On the otherhand, with today's A/V's and Firewall's, if kept current, the threat of someone attacking SMB 1 is lessened. MFG's are also including Security s/w in the routers too, although from my experience with a router that has that and when the device's Norton 360 report are quite different. Probably router bases Security is a weak sister to device based Security based on execution, not where the TCP/IP packets come from, but what the device does with those packets after they are assembled.
Again, GOOD LUCK... with a company that can't seem to even produce a stable firmware with 'fixes', much less add a function and have it work right out of the box.
- radon85Jan 07, 2020Guide
IrvSp,
Yes, I understand the battles and the headwinds. And I appreciate all the effort put forth beforehand. I'm simply looking to take a different approach and hoping it might be fruitful. Organizations like low hanging fruit and I believe this may be an easy way to workaround the issue. For a small amount of effort they could eliminate a problem with their customer base. Whether it is pursued is dependent upon how big of an issue it is with current customers and the direction of the marketing roadmap. Thanks again for the input.