TS-459 PRO cannot be accessed on Win 11 computer. Okay on Win 10

English Storage
1

Hi,

I got myself into a situation where I can access the shared folders on a TS-459 PRO NAS from withing my Win11 computers but can access from Win10 boxes.

My NAS info is:

TS-459 PRO II, F/W is 4.2.6.20240618, Network Setup is Single Port.

I cannot see or access the NAS in Windows File Explorer or can it be seen as a network device. I can access the NAS via Qfinder by double clicking the NAS and entering the login and password info. When I highlight the NAS and try to map network drives, I get a login error on the screen and I can see the login error in the system log of the NAS. I can connect from the various Win10 computers correctly and the Users that can access it include admin, guest, and my first name and can be SAMBA and HTTP. The login errors are from a user that is my email address that, apparently is what Windows11 is trying to send to the NAS as the User.

I have tried adding an additional user to the NAS that is my email addresss but no luck.

Does anyone have any idea where else to look or what to try? I hesitate to set up another account on the Win11 boxes just to be able to access this little NAS.

Thanks in advance!

2

login via SSH and issue:

smb3enable and see if it works now

3

Thanks for the offer to help:

I installed PuTTY and gave logging in a try via port 22 and got a fatal error "Couldn’t agree a host key algorithm (available:)

I’ll continue to try and get into the device via SSH.

4

if you use windows you can just open a command window and type


ssh admin@NASIP

no need to install anything

5

Thanks. Wilco. I know just enough to be dangerous. I’ll keep you posted.

Same thing almost: "I got an “Unable to negotiatie with 192.168.x.xx port 22: no matching host key found, Their offer:”

6

If you don’t mind using SMB 1.0…

Windows Search > “Turn windows features on or off” > SMB 1.0/CIFS File Sharing Support"
Enable all options & reboot.

7

I don’t mind doing that even though it’s highly discouraged. I’ll give it a try. Windows 10 must be less finicky about that version on SMB.

All things considered, I probably should just retire that old NAS.

8

Just enable SMB2 instead of fallback to SMB1 for each machine

9

No joy with enabling SMBv1 here either. It’s got me stumped.

10

Seems to be a common theme on the internet, W11 unable to see networked devices. The only other W11 specific tweak I can think of is a security setting that has prevented me accessing network devices in the past (it’s easily reversed).

RUN IN POWERSHELL AS ADMINISTRATOR

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force

Set-SmbClientConfiguration -RequireSecuritySignature $false -Force

Set-SmbServerConfiguration -RequireSecuritySignature $false -Force

11

Thanks Richard, I will give this a try in a bit.

Also, as an aside, the version of firmware running in this particular TS-459 PRO II NAS is version 4.2.6.20240618 and the SMB settings available in this firmware version does not allow for the selection or deselection of any particular version of SMB in the advanced settings tab as do the other three NAS systems I have including an older TS-879 PRO running version 4.3.6.2805.

12

Bingo! Touchdown and the crowd went wild! Many thanks!

13

You’re welcome :grin:

14

So you rather enable insecure SMB1 on Windows than SMB2 on your NAS..OK?

15

In the firmware version on the particular NAS that I have there are zero options, that I can find via the web interface at least, to select or deselect any and all versions of SMB. Maybe there are other command line or SSH (which I can’t seem to get to work) options but I can’t figure them out.

16

Did you try that simple command via SSH on windows shell?

17

Yes I did per your earlier recommendation. I got the following similar error:

Not sure what a host key is or where to find it.

18

But that was with putty, did you try it via windows command prompt?

If it happens there too, we might have to change the command slightly to allow insecure ciphers

19

Yes. Yes. That last message I relayed to you was the result of an elevated Powershell or command prompt. As I mentioned, although not the same as what I got back from PuTTY, it was similar enough because it mentioned the term “host key”.

20

See here

ssh -m hmac-sha2-256 admin@NASIP