@Razorwindmo60 

 

Common problem, MS one created I suspect too.

 

Well, if you run NET VIEW, you will get an error, so that indicates to me an SMB problem.

 

You might get this one even (others are Permission errors):

 

C:\>net view
System error 6118 has occurred.

The list of servers for this workgroup is not currently available

 

All is NOT lost, you CAN get to the other devices and the USB router drive. All you need do is use the NET VIEW device name OR IP Address. Can also create an Icon for the device using the same.

 

For instance, to see my USB router drive I can do this:

 

C:\>net view \\tp-share
Shared resources at \\tp-share

Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
G           Disk  V:
The command completed successfully.

 

As you can see, I have done a NET USE to assign the USB drive (called G) to my PC as a V: drive. Using that, I have complete access.

 

If any other PC on the LAN wants to access my PC, they can use this:

 

C:\>net view \\irvxps8940
Shared resources at \\irvxps8940

Irv's XPS8940

Share name   Type  Used as  Comment

-------------------------------------------------------------------------------
C            Disk

 

I've gone round and round over this, and MS doesn't seem to care. SMB1 recently has had some 'protection' added to it.

 

Google "24h2 smb1 changes" for more about 'signing',

 

Like this:

 

============

What changed

In Windows 11 24H2, we've made two major security changes that can affect mapping drives to third-party consumer NAS or routers with USB storage:

 

1. By default, SMB signing is required on all connections. This increases your security by preventing tampering on the network and stops relay attacks that send your credentials to malicious servers.
2. Guest fallback is disabled on Windows 11 Pro edition. This increases your security when connecting to untrustworthy devices. Guest allows you to connect to an SMB server with no username or password. While convenient for the maker of your NAS, it means that your device can be tricked into connecting to a malicious server without prompting for credentials, then given ransomware or having your data stolen.

SMB signing has been available in Windows for 30 years but, for the first time, is now required by default on all connections. Guest has been disabled in Windows for 25 years and SMB guest fallback disabled since Windows 10 in Enterprise, Education, and Pro for Workstation editions. Both changes will make billions of devices - not just Windows, but everything running SMB that wants to talk to Windows - more secure. They've been in Windows Insider Dev and Canary builds for a year.

============

 

I've seen changed to Group Policy Editor, but I don't have the Pro version with it. You can 'add' GPEDIT to Home, but I didn't want to, so this is what I tried

:

 

===================

I know this thread is getting ali’l old now but here are some mitigations that were posted on YouTube by computer repair tech Carey Holzman that may fix these Win11 drive sharing issues:

Turn off SMB Client Signing With PowerShell (for Windows 11 Home or Pro)

Step 1 – Type PowerShell in the Windows search box on your taskbar.

Step 2 – Hit the Run as administrator option under the Windows PowerShell section.

Step 3 – In the PowerShell command line window, type [or copy] the following command and press Enter to turn off the SMB signing requirement:

Set-SmbClientConfiguration -RequireSecuritySignature $false

Step 4 – Type Y to confirm the operation.

Enable guest fallback

Step 1 – In the PowerShell command line window, type [or copy} the following command:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true

Step 2 – Type Y to confirm the operation.

No reboot is necessary. Now see if you can access your shares!

 

===========

 

I did make those changes, and they did not work for me:

 

RequireSecuritySignature              : False

EnableInsecureGuestLogons             : True

 

 

Did that, didn't help, but some people said it did?

  @Razorwindmo60 

 

That YOU TUBE didn't work for me.... first I have HOME Edition. Secondly, all the Windows Settings were correct for me. NO GPEDIT in Windows Home, but as I had shown above, I used Powershell to set those values, the alternate way to do it if on had a Home Edition.

 

Note, the ERROR the YT video shows, completely different from mine.

 

It did work for me using an  OLDER BE65 F/W, and TP-Link support did connect to me and did some debug... they pointed the finger at MS.... Not the F/W I think caused it.

 

I do have the BE65 Deco's connected, and I have an AX55 normal router.... well, we switched over to that one, and the problem existed.

 

I don't know what specific fix you got and made that made yours work, but I have all the same settings as in the video.

 

My root problem is the List of Servers.... normally held by the Master unit browser, and that would be the first PC turned on, otherwise the Router maintians the list and will send it to the first PC connect, and possibly to the one logging on after that. However in my case, the NET VIEW error, "The list of servers for this workgroup is not currently available" means it can't get the list of connected devices. Packets capture from that command show no device reports it has the list, and it was sent to the router.

 

The error message "The list of servers for this workgroup is not currently available" (system error 6118) often indicates issues with network discovery or SMB (Server Message Block) functionality, which can be caused by firewalls, incorrect workgroup settings, or disabled features. Since SMB and Network Discovery is on, Firewall was the next suspect. Eacy to check, turn them both off and try again.... nope, it isn't those?

 

In Windows File Explorer I can see my Wife's PC, but NOT mine...

 

Something is wrong here, that is for sure... and she can see my PC, but not her's and she's ON W10 Pro.

 

I've tried Net View what her PC is off, just me and the Deco, same error...

  @IrvSp 

Oops, my fault. I should have said that it only works on Pro Editions. It even says in the video does not work for Home Editions.

Razorwindmo60 wrote

  @IrvSp 

Oops, my fault. I should have said that it only works on Pro Editions. It even says in the video does not work for Home Editions.

  @Razorwindmo60 

 

Yes, I know that. No GPEDIT on Home. It really isn't needed, as I mentioned above, I used POWERSHELL to make the same changes that GPEDIT does.

 

What SPECIFIC change did you make that fixed your problem as the 'setting' was wrong on your PC?

 

Also, my error is different from the one on You Tube, so that may be why it fixes your problem.