Receiving SMB1 fail attempting to UNC to Server 2003

Andrew N. Kowtalo
Andrew N. Kowtalo used Ask the Experts™
on
Has anyone ran across this issue?  I am just seeing this for the 1st time.   I have a users running 1903 patch on a windows 10 pro laptop.   When he tries to UNC to his server he is getting this error..

You can't connect to the file share because its not secure.   This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.   Your system requires SMB2 or higher.  For more info on resolving this issue, see:
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows

The file server is 2003 however other machines in the company on the same domain running Windows 10 pro with almost the latest feature patch ARE able to access the 2003 server share.   I can't UNC to the file server from his machine either get the same error

[Window Title]
\\alpha2

[Content]
\\alpha2

You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.
Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747


[OK]

He needs to access these files to work.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
A lack of information provides a lack of a decent solution.
Commented:
Andrew N. KowtaloSupport Center Engineer

Author

Commented:
Hi Alex where am I doing this from?  The file server or his machine?
AlexA lack of information provides a lack of a decent solution.

Commented:
his machine, your file server is fine, it's just massively outdated. Yes, you need to upgrade/migrate to a new OS.

Regards
Alex
AlexA lack of information provides a lack of a decent solution.

Commented:
Oh that's meant to be run in powershell btw
Andrew N. KowtaloSupport Center Engineer

Author

Commented:
Alex I will give this a try.  I just wonder why its on his machine and everyone else is able to still connect all on the same domain.    His feature updates are way out I thought maybe upgrading him to 1909 would fix it.
AlexA lack of information provides a lack of a decent solution.

Commented:
Because by default SMBv1 is disabled and it's entirely possible someone else went around and enabled it for those users :-)

Regards
Alex
Andrew N. KowtaloSupport Center Engineer

Author

Commented:
Alex was fast and accurate thank you very much.
AlexA lack of information provides a lack of a decent solution.

Commented:
Excellent, you're very much welcome, anything else give me a shout.

Regards
Alex

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial