Win10 laptop suddenly refusing SMB1 connections

bro67 · 10 Sep 2017

You will continue to see SMBv1 blocked in Android OS, the developer tools and all OS's since the last wipeout worm that caused so many headaches a few months ago, gave a wakeup call to Microsoft and those who are developing tools. Only issue that we are dealing with are those who continue to not update the Java tools that people are relying on for keeping their older applications working with outdated devices that do not support the latest versions of Android.

Nothing silly. ES has zero issues working with SMBv2, since Google has killed SMBv1 from Android. It has also been stated that ES File Explorer needs to not be used anymore, because the developer has failed to keep up with the better apps that do not allow for various security holes.

There are plenty of better utilities out there. At this point since you are doubting the information that you are being given, it is done at this point and you have already been offered advice and told that Android no longer allows SMBv1 connections because of the security risks. This will back up why I am stating that you cannot use SMBv1 anymore. Stop using SMB1 | Storage at Microsoft

bro67 · 10 Sep 2017

Google releases Samba client for Android, adds Windows file shares to the Downloads/Files app A better SMB utility that I use on my NVIDIA Shield. https://play.google.com/store/apps/d...ysesoft.andsmb

If you have anymore issues about android development, I would suggest asking in the Android forums for help, along with developing for the latest versions of Android OS and to start using SMBv2 & 3.

Writerman · 11 Sep 2017

Bro67, I don't doubt the information I am being given and I have the greatest respect and gratitude for your help. You have my unreserved apologies if I have mistakenly given a different impression. I was particularly interested to hear that ES file explorer is no longer in favour. For some time now, I have hated that product with a vengeance. It used to be useful but has lately descended into something little better than malware, displaying spurious panic messages in my notifications area intended, no doubt, to dupe me into purchasing some unnecessary piece of bloatware. I now tend to uninstall it whenever I'm not actively using it. I don't suppose you have a recommendation for an alternative product?

As for raising my question in the Android development forum, I fear I fall between two stools and that the advice there would be to raise my enquiry in the Windows forum.

Following your advice, I shall attempt to convert my app to SMB2 as soon as possible but "as soon as possible" is unlikely to be this week or next. In the meantime, I have come up with a bodge so I can complete my testing. I have written a little program to run on my laptop that mirrors my shared folder with a share on my NAS drive, which my app is still able to access. My Android app is thus able to exchange files with my laptop using the NAS drive as an intermediary. Clunky, yes, but it gets me out of a hole.

I remain curious as to why, a week ago, I was able to access both my Windows 10 PCs from Android but now can only access one of them, the other being unaffected, but that's mere curiosity. I'd be interested to learn whether whatever change has occurred can be undone or simply to understand it better but that's no longer a matter of urgency.

Thanks once again for your advice and apologies again for any misunderstanding.

flhthemi · 12 Sep 2017

If you like ES buy the pro version...no adds, no problems and it looks like it used to look, pretty much.

Writerman · 13 Sep 2017

flhthemi said:

If you like ES buy the pro version...no adds, no problems and it looks like it used to look, pretty much.

I did wonder about that but, unfortunately, I am so disgusted by the company's underhand tactics with the free version that I will never buy anything of theirs. This is partly a matter of principle and partly the fact that I could never trust a company so unscrupulous as to distribute free software that then puts out spam messages (which they know darned well are a pack of lies) in my notifications area.

lx07 · 13 Sep 2017

You do have SMB1 turned on in Windows Features?

Win10 laptop suddenly refusing SMB1 connections-capture.png

I use SMB1 to connect from my Arch VM to Windows and it works OK. I know nothing about Android though so please excuse me if this is not relevant but I guess it is the Windows side you are asking about.

Writerman · 13 Sep 2017

lx07 said:

You do have SMB1 turned on in Windows Features?

I use SMB1 to connect from my Arch VM to Windows and it works OK. I know nothing about Android though so please excuse me if this is not relevant but I guess it is the Windows side you are asking about.

You are right, it's the Windows side I was asking about. I can confirm that SMB1 is checked under Windows features so I remain perplexed.

Thanks for the suggestion though. I may try turning it off, rebooting then turning it back on again to see if that makes a difference. However, this is no longer urgent for me as I have a work around so it may be a while before I have time to try that experiment.

Thanks again
Keith

cereberus · 13 Sep 2017

Writerman said:

This is getting silly. To "keep" using SMB2 is not an option for me. What ES does or does not do is irrelevant. I am talking about my app that I am developing. Much as I would like to move to SMB2, the SMB libraries shipped with Android Studio were, unfortunately, SMB1 and that is what I developed against. I have recently found some SMB2 libraries but the interface is different and I don't have the time or resources to upgrade my app to SMB2 at this time. It was working perfectly well talking to both my laptop and my tower PC a week or so ago. Now it only works talking to the tower PC. I just want to get my laptop back to where it was.

These philosophical discussions as to whether one should, or should not, use SMB1 are very interesting and I have learned a lot from them but the bottom line is that I want to complete my testing so that my bridge club (who are the end user) can start using the scoring system. To do that, I need my laptop to accept an SMB1 connection. As I said before, the network upon which it is ultimately to be used is closed off from the outside world so I don't forsee any security threats. Once I've got the initial version up and running then, and only then, might I have time to look into upgrading it to use SMB2. As for Google/Android enforcing SMB2, that's a non issue so far as I am concerned. The version of Android in use on our kit is an old one that patently does permit SMB1 and that is unlikely to change in the near future, if ever.

So can we please put aside issues of whether I should, or should not, be using SMB1 and just accept the fact that, rightly or wrongly, that is what I wish to do. That said, can anyone now help me with my original question. What might have happened to my laptop to cause it to appear to Android as requiring SMB2 and is there any way to reverse that change?

Your whole argument is that MS should retain an insecure SMB1 system because your application/android system is not able to properly handle SMB2.

This is a totally ridiculous expectation.

Buy new android kit that does handle SMB2 - end of story.

lx07 · 13 Sep 2017

cereberus said:

This is a totally ridiculous expectation.

Possibly. Possibly I should sell all my records and buy a CD player but that wasn't the question either.

The OP wants to use it. SMB 1 is deprecated but has not (yet) been removed either in Server 2016 or Windows 10.

Microsoft to Disable SMBv1 in Windows Starting This Fall

It certainly still works for me on latest insider build. The question isn't "is it a good idea?" but "how do I make it go?".

cereberus · 13 Sep 2017

lx07 said:

Possibly. Possibly I should sell all my records and buy a CD player but that wasn't the question either.

The OP wants to use it. SMB 1 is deprecated but has not (yet) been removed either in Server 2016 or Windows 10.

Microsoft to Disable SMBv1 in Windows Starting This Fall

It certainly still works for me on latest insider build. The question isn't "is it a good idea?" but "how do I make it go?".

Yes but issue is really at Android end but OP is saying it effectively blaming MS. MS are not going to do anything, and there is probably no solution at OP's end, as using old android kit. In the end the two systems are no longer compatible. It would probably be better to go on the android forums to see if the android device can have a newer compatible OS flashed.