@HelpFixDecoApp 

HelpFixDecoApp wrote

  @IrvSp @Ryan @Carl 

 

There have been a lot of user in the past who had issues accesing their USB drive using deco. Could this be the root cause? 

Not all Deco's if they do? I've had a few here, X55 and BE65 that I recall worked fine.

I assume holding onto the MSBrowser is a function of the F/W.

I've had some issues and had exchanged email with ones you referenced, but not on this specific issue and also ahd Support connnect to this Deco. Was looking for a different problem and confirmed I had it. Nothing major though. Small issue.

This has been a 'nagging' issue tor me. Well before Win11 25H2 even. I just decided I'm going to 'dig around' and see if I can find some reason, and the above I think it not usual for one to see?

MS has depricated NET VIEW actually, but while NET VIEW doesn't work, NET VIEW \\SHARE_NAME does.

  @Ryan
 
 

Ryan wrote

When you used "nbtstat -a tp-share", does this mean that you targeted the share itself, and the Deco is the Master Browser?

Since I know the name of the share on the Deco itself from the USB settings in the Deco app, I used that name to look at it. 

Using the Share name of the 2 PC's got me the results for those PC's.

Ryan wrote

 

Also, what did you mean by "The Master Browser which is has is no longer in use by MS"?

Here is what Google AI says about it:

=========

Computer Browser service (which relies on the Master Browser protocol) due to its age, insecurity (using legacy SMBv1), and high network traffic, disabling it by default in modern Windows versions like Windows 10 and 11, recommending its removal to enhance security and reduce noise on the network. 

=========

There is a good chance the Deco F/W is not using SMB2 even?

By the way, SAMBA works fine using VLC for instance.

NET VIEW is basically gone as well as it requires the Master Browser list,

Google AI has this to say about it:

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

net view, favoring modern, more secure alternatives like Kerberos and PowerShell cmdlets (e.g., Get-NetComputer) for network discovery and management, with the goal of enhancing security and standardizing on newer technologies across Windows. While net view might still function on older systems, it's considered legacy and its behavior isn't guaranteed in newer Windows versions as it relies on older protocols being phased out. 

• Security Concerns: Older protocols like NTLM (often used by net view) have weak security implementations compared to modern standards like Kerberos, leading Microsoft to deprecate them.
• Modernization: Microsoft is pushing developers and administrators towards modern .NET, PowerShell, and newer Windows features for better performance, security, and management.
• Feature Removal: Commands like net view are often replaced by more powerful and scriptable PowerShell cmdlets (like Get-NetComputer) and are removed in favor of these newer tools in current Windows versions. 

• PowerShell: Use Get-NetComputer for discovering computers on the network, or Get-NetNeighbor for local network info.
• Modern Protocols: Rely on Kerberos for authentication instead of NTLM.
• WebView2: For web browser controls in applications, use the modern WebView2

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

Of course, the above PowerShell cmdlet is not in Powershell and is for Active Directory:

========

========

  @IrvSp I gave up on USB drives on WiFi enabled routers.  At least on the BE95 there's an option to throttle 3.0 speed to decrease noise on 2.4 GHz band.  I was trying to prove to someone over on the ASUS forum that there is a known concern and had to plug in the USB to get the option to show.  I left it there...  A day or so later my Sensi Lite thermostat went offline, which usually requires me to pull it from the wall and reconnect it to WiFi.  After I ejected and pulled the USB, walked back to the thermostat (which has a clear line of site around 10 ft away, it had already reconnected).

It's been like that for me when I used it, need to enter the share "directory" into File Explorer to access.  Are you no longer able to open the drive?  (That's what happened to ASUS router SMB/SAMBA)...

  @jzchen 

BE68 has that same USB 3.0 setting:

I've tried it both ways, can't see any change or difference?

I did have some other problems, device dropping off.Support got involved and it was determined in the iWatch doing that it was an iOS problem and Apple was notified by support for Apple to fix.

Along the way they did know of another problem they were working on, IoT devices not responding to the Deco/Router's TCP/IP request to see if they were still connected. Specifically in my case, our Keurig Coffee Maker that uses WiFi to set the brewing specifications for each capsule (QR code read, goes back to Keurig server to get the proper time, temperature, and pressure for each capsule being used.

Once the Coffee Maker loses LAN connection I do have a problem getting it reconnected... involves powering it off and on a few times, and rebooting the Deco's.

Suspect your Thermostat has a similar problem... and I recall it was explained to me the Deco doesn't know when it disconnected or that it is connected so I just leaves it connected... and that creates a reconnect problem.

USB has not always been a problem. However, as a Beta Tester I've had different Routers and Deco's in use. As well as MS Windows versions and releases over the years.

Can't recall when it last worked, but the problem is not new.

Yes, using the Share Name in Explorer works, and does NET USE which I've used when I had some major file coping to do. We use that USB drive to save an occasional Acronis Back-up on each PC to it, and copy over new pictures from our iPhones to the Picture folder on the USB drive.

You can Google "microsoft smb1 support" and read all about it.

You csn see what SMB version you are running in PS:

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

PS C:\> Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

FeatureName      : SMB1Protocol
DisplayName      : SMB 1.0/CIFS File Sharing Support
Description      : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.
RestartRequired  : Possible
State            : Enabled
CustomProperties :
                   ServerComponent\Description : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer
                   Browser protocol.
                   ServerComponent\DisplayName : SMB 1.0/CIFS File Sharing Support
                   ServerComponent\Id : 487
                   ServerComponent\Type : Feature
                   ServerComponent\UniqueName : FS-SMB1
                   ServerComponent\Deploys\Update\Name : SMB1Protocol

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

The main problem I feel is SMB1 which MS has decided shouldn't be used. Use SMB2 instead, but I don't think the F/W has moved up to that?

By the way, the Internet is full of reports of NEW VIEW not working. Just Google this, "Net view not working windows 11"

Most of it it appears relates to SMB1 and the Master Browser function.

Google this too, "windows 11 master browser" and it is a common problem.

Bottom line, MS has removed some services and features, and in some cases, like SMB1 you can manually override MS's default. However, nothing is guaranteed to work right it seems.

  @HelpFixDecoApp 

HelpFixDecoApp wrote

  @IrvSp @Ryan @Carl 

 

Can we test @IrvSp theory and have the engineers make a beta firmware for only their deco model and HW version that switches SMB1 to SMB2 and see if it fixes the issues? 

You might be jumping too fast here?

It IS possible that the Deco IS using SMB2? I have not figured out how to check that out?

Now I can connect the USB share to my PC using NET USE X: \\tp-share\g and then run in PowerShell  Get-SmbConnection:

PS C:\Users\ispal> Get-SmbConnection

ServerName ShareName UserName         Credential                           Dialect NumOpens
---------- --------- --------         ----------                           ------- --------
tp-share   g         IRVXPS8940\ispal MicrosoftAccount\is 3.1.1   1
tp-share   IPC$      IRVXPS8940\ispal MicrosoftAccount\is 3.1.1   0

Supposedly that dialect shows the SMB connection?

From a Google search:

Method 2: Use Windows PowerShell (For connected shares)

1. Open PowerShell as Admin: Search for "PowerShell," right-click, and select "Run as administrator".
2. Check Connections: Type Get-SmbConnection and press Enter.
3. Identify Dialect: Look at the "Dialect" column. It will show the SMB version (e.g., 2.02, 3.02) for any active connections to shares, including your router's

So it says SMB 3.1.1, but I am not sure either? It might also be USB version?

Further complicating this is that I added a connection to my wife's D drive:

PS C:\Users\ispal> Get-SmbConnection

ServerName    ShareName UserName         Credential                           Dialect NumOpens
----------    --------- --------         ----------                           ------- --------
laraine-tower d         IRVXPS8940\ispal MicrosoftAccount\is 3.1.1   1
laraine-tower IPC$      IRVXPS8940\ispal MicrosoftAccount\is 3.1.1   0
tp-share      g         IRVXPS8940\ispal MicrosoftAccount\is 3.1.1   1

It also reads as the same and I KNOW her PC is using SMB1????

Confused here, but I'm sure @Ryan  can find out what is being run on the Deco. 

Also, running SMB2 may not be enough? Suspect of Windows changes may be needed. Google to find NEW VIEW complaints on Win11 as well as LAN sharing. There are many, and many point back to an MS problem.

  @Ryan, @HelpFixDecoApp,

I'm not sure what to do and even if this is necessary?

I'm sure Support can answer if the BE68 F/W runs SMB1 or SMB2/3?

I don't think the Deco isn't working, I can use Samba, see the settings in the Deco App, and use NET VIEW \\Share_Name to see it. I can use Windows Explorer using for the address \\tp-share as well.

It is just a question of why the Deco thinks/knows it is the Master Browser and doesn't relinquish that to another PC?

As for all out PC's enabling SMB1, they are and looks like this in the settings:

I've read the the Server didn't need to be run on the PC, but with it enabled or not it makes no difference. 

SMB2 is enabled on my PC:

PS C:\> Get-SmbServerConfiguration | Select EnableSMB2Protocol

EnableSMB2Protocol
------------------
              True

Actually both SMB1 and SMB2 are enabled:

EnableSMB1Protocol                     : True
EnableSMB2Protocol                     : True