Windows 10: windows 10 20H2 cannot connect to SMB1, why isn't it fixed ?

I Need to connect to old linux server but windows 10 does not let me! It worked fine from windows 7 and I can ping the server and connect to other ports no problem.

I have already added "Turn windows features on or off" -> SMB 1.0... and the pc restarted 2-3 times and now they show as marked but does not work.

If I take off any of the marks from SMB 1.0.. I get undefined error.



SO HOW CAN I CONNECT!?

https://preview.redd.it/g1yzdjjwl10...bp&s=25f01c6bc541081b78261dcee20fbcbb39cb2fb0

submitted by /u/1donthaveusername
[link] [comments]

:)

 

Printer isn´t working after latest update.

After the latest update from Windows, my Canon Pixma ip6600 printer isnt working. In Device Manager it shows up as working properly but when I go to print it isn´t listed as an option in any programs. Troubleshoot suggests it´s a USB 2 printer on a USB
3 port and that that´s the problem but that cant be since it worked fine before the update. I´ve tried to uninstall and plug it back in but that doesn´t work either.

 

SMB1 Error

Hi Greg,

Thank you so much for your advice. I enabled SMB1 Client by following the steps in one of the links that you supplied.

How to fix "You can't connect to the file share because it's not secure" message in Windows 10 while mapping network share?

Thank you once again.

 

Windows 10 1803 and applications on SMB1 shares can't connect to anything

Talking Client side, since the server (2003) didn't change: SMB1 is not blocked, otherwise I wouldn't be even able to see the share. The issue is not that I can't see the share or open the files there, the issue is that if I run an exe from a SMB1 share
that exe won't be able to establish connections. If I run it from a SMB2/SMB3 share or from a local disk on my PC it all works as before.

I can't see an option like "Allow exe's on SMB1 shares to establish connections" in Windows Features, only Client and Server and, obviously, they are both ON. I tried disabling and restarting then re-enabling and restarting and it didn't resolve the issue.

I checked under monitoring, as you say: the "Advanced Options" link is grayed out, This is due to internal policies, and I received assuration that no changes were made to the policies, or to F-Secure, which is listed as the agent responsible for all the 3
networks listed and is controlled by a Policy: also F-Secure hasn't changed, since under the same policies and F-Secure settings we have both Windows 10 1709 PCs and Windows 10 1803 PCs and only the latter have the issue.

The only change one needs to have the issue, is to perform the 1803 WIndows 10 update