@JimRe 

If on Windows, open a CMD prompt and enter NET VIEW... do you see the share? If so, then enter NET VIEW \\Reece-Share and if you can see the drive, you should see a drive letter.

If not, you might not have SMB1 turned on in Windows. Control Panel, Programs and Features, Turn Windows Functions on or off, select SMB1 (don't need the Server) and install that. Possible the hard wired PC has that installed as it is needed to access the share.

Hope this helps.

By the way, if your laptop does see the share, it wasn't too clear when you said it can see it under network but can't access it? What happens, get an error or does it just do 'nothing'? What happens with Windows Explorer and the NETWORK selection? Same thing? Under the NETWORK LOCATIONS, do you see the hardwired PC?

  @IrvSp You were correct, I did not have SMB1 turned on in Windows.  I turned it on and rebooted.  However, when I tried to map the path \\Reece-Share to a drive letter, I received "Error Code: 0x800700035 -  The network path was not found."  Strangely as I originally said, I could see the Reece-Share in the Networks section of This PC.  See attached screen capture.  I almost gave up, but I tried again and this time clicked on "Browse".  My Reece-Share showed up in browse, so I selected it and it connected just like I wanted.  So this solved the problem.  I have no idea why mapping the drive would not work the normal way, but using the browse feature solved the problem.  Thank you for the assistance.  

  @JimRe 

Not sure what you used for the NET USE command...

For instance, only my LAN I see this:

C:\>net view
Server Name            Remark

-------------------------------------------------------------------------------
\\IRVXPS8940           Irv's XPS8940
\\TP-SHARE             samba server
The command completed successfully.

Then see what is on \\TP-SHARE:

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

samba server

Share name  Type  Used as  Comment

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

So the actual share is G, the command to share it is:

C:\>net use x: \\tp-share\g
The command completed successfully.

Now I can access the LAN share as X:

C:\>x:

X:\>dir
 Volume in drive X is G
 Volume Serial Number is 77A2-373A

 Directory of X:\

03/16/2018  01:25 PM    <DIR>          $RECYCLE.BIN
09/13/2021  06:24 PM    <DIR>          .
.

.

.
               3 File(s)      2,255,233 bytes
              10 Dir(s)  908,271,632,384 bytes free

  @IrvSp SMB1.0 is seriously insecure. The firmware needs to upgrde to a secure version of SMB

  @cr42 SMBv1 CVEs:
     cve. mitre. org /cgi-bin/cvekey.cgi?keyword=smbv1   (remove spaces)

  @cr42 

Yes, well known. Very olf too.

However, I think the root problem is on the Server, not the client.

On my AX55, V2 is running, but I use V1 Client to access it.

What I did above to get the into, did a NET USE to the router share and then changed to that drive, and used PS Get-SMBConnetion. Give it a try, your router is probably running 2.0 or better.