New ISP router -> unable to open SMB share

Question

Hi Community,

Recently got the fiber, I now have a new router from my ISP, whose LAN address space is identical to the previous one: 192.168.1.*. I have a private server on this LAN, which notably hosts the OMV application. I can access the application from a client station, which proves that the server is functional.

This application exposes an SMB share which allows me to store music, images and videos. From my workstation (Win11), when the old router was in use, I just had to open File Explorer, browse the Network to see the share appear:

A double-click allowed me to navigate through my folders and access the various files.

With the new router, I still see the SMB share (idem above), but a double-click causes an error message to be displayed (sorry, in French):

In English: "the share is not accessible, because you maybe don't have the requested authorization to reach this network resource. [...] Invalid network address" when nothing else has changed.

If anyone has a clue how to solve this problem, I'm all ears!

Thanks in advance for any help!

Answer 1

How are you authenticating to this other pc? Did you map a persistent network drive with an ID+password? Run "net use" from a command prompt.

Do you have an entry for this PC in the "Windows credentials" section of Credential Manager? (See Control Panel\User Accounts\Credential Manager)

Or did you define a local account with the same name and password on both machines?

With a new router, the obvious change would be how DHCP registers the pc name. My router registers names with .Home.

PS C:\> nslookup 192.168.1.5
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
Name:    Blackhole.home
Address:  192.168.1.5
PS C:\>

If you can still "see" the other PC, then network discovery is working. So there must be something else. Do you see any change in the pc names?

On the remote PC have you checked the security eventlog to look for logon failures? Ca

n you logon to the desktop with whatever account you use for network access?

I wrote a Powershell script a while back to try and troubleshoot issues like this. You could give that a try. I haven't updated it in a while, but it might point something out.

See SmbTest.ps1

https://social.technet.microsoft.com/Forums/en-US/f19af453-d2b3-47ba-86ba-0833d87c9d80/unable-to-map-network-drive