@yoa78 

If you want to reference the device, you need to use the IP address. Typically two Windows machines can reference each other names using their own protocols, but the router can not do that for them. So if you are using mobile device you might need to use an IP instead.

If you have a Windows computer not able to access the router USB drive, first try the IP address, then try enabling SMBv1.

Tony wrote

@yoa78 

 

If you want to reference the device, you need to use the IP address. Typically two Windows machines can reference each other names using their own protocols, but the router can not do that for them. So if you are using mobile device you might need to use an IP instead.

 

If you have a Windows computer not able to access the router USB drive, first try the IP address, then try enabling SMBv1.

@Tony Hi Tony - thank you for the reply.  I was able to resolve the issues I originally posted about.

As I stated, prior to implementing the Archer AX11000, my file explorer of choice (in this instance Solid Explorer on Android and  Documents on iOS) was able to connect to my Windows-based computers by way of their machine names.

Once I implemented the Archer AX11000 - I was no longer able to do so.  I performed a factory reset thinking that would resolve the issue, but alas that did not work.  I eventually did a web search for the error that I was facing and it turns out that I was not the only one facing this issue (in a general sense).

The fix was to preface the hostname with SMB://name of computer to connect to and that did the trick.

With respect to the machine names not appearing properly under the Connected Devices status page - even after the factory reset, some devices were not displaying their names proper (i.e. my main computer was listed as the name of the Workgroup that I have my computers assigned to and not the name of the machine itself).  After setting the names properly in the Connected Devices page (I also have an Ecobee thermostat that did not have its name displayed properly either (but instead had an * as the device name), and restarting both the router and my main computer - the name of my main machine display properly when searching for SMB clients to connect to.

I'll keep an eye out for how things proceed from here - but I'm not exactly sure I am feeling the warm and fuzzies about this router ATM.  The last firmware update was published back in February and that alarms me a bit as there are ALWAYS bug fixes and new features to implement and the scarcity of firmware updates does not seem to promote long term support of this router (I tend to keep my routers for YEARS (7+))