Windows 10: accessing NAS drives on a bridged connection on my PC

I have bridged my wifi internet connection to my lan port on the PCI have run this link to a Netgear witchMy NAS drives are connected tothe switchPC with wifi bridged 2.5G LAN port----------------------Netgear switch 2.5G port------------------NAS drives - 2.5G port--------------I can map the NAS drives, I can open them and see the files on themI cant play and video over t he bridged connectionI can sort of moved a file from the local PC over the connection to a NAS drives Takes foreverWhy so slow to copy to or from?Is the bridge setup in Win11 off?

:)

 

accessing NAS drives on a bridged connection on my PC

I have bridged my wifi internet connection to my lan port on the PC

I have run this link to a Netgear witch

My NAS drives are connected tothe switch

PC with wifi (bridged) 2.5G LAN port

----------------------

Netgear switch 2.5G port

------------------

NAS drives - 2.5G port

--------------

I can map the NAS drives, I can open them and see the files on them

I cant play and video over t he bridged connection

I can sort of moved a file from the local PC over the connection to a NAS drives (Takes forever)

Why so slow to copy to or from?

Is the bridge setup in Win11 off?

 

Problem accessing a NAS drive


I have 2 NAS drives and 3 computers in my home network. The NAS drives and one PC are Ethernet-connected to a router/wireless access point; the other 2 PCs use wireless connections. All 3 PCs can access one NAS drive with no problem. The drives show up in the Network section of File Explorer, and if I click on the NAS's icon all it's shares are displayed (whether or not the PC has credentials to access the shares). The shares on the other NAS drive can be seen by only 2 of the PCs.

On the failing PC the inaccessible NAS drive shows in File Explorer, but if I click on it I get




However, on that same PC, Firefox can access the FTP server on the NAS drive



so Windows obviously has no trouble communicating with the NAS. And Windows must be configured to allow communication with a NAS in general or it could not successfully connect to the other NAS. (Those two screen snips were stored on that working NAS.)

The problematic PC doesn't really have to reach the NAS, but I would like it to, and I'm frustrated that I can't figure this out. Anyone have any suggestions?

BTW, the error popup says I should ask the administrator of the server about this. I would, but I'm not speaking with myself at the moment.

 

Bridged Networks and SMB on a NAS

I have a wireless connection to my router, and a wired ethernet connection to a Synology NAS. I want to bridge the two adapters, so that the NAS is visible for SMB shares on the local network and also has a route to the internet.

I have been going round in circles and though it sometimes works intermittently, nothing I do seems to survive a reboot. I presume this means there's an IP conflict somewhere!

Settings:

Router: 192.168.1.1

Host PC: 192.168.1.214

Bridged Network: Static 192.168.1.215 / 255.255.255.0 / Gateway 192.168.1.1 / DNS 192.168.1.1. TCP/IP over NetBios enabled.

NAS: 192.168.1.212 / 255.255.255.0 / Gateway 192.168.1.1 / DNS 192.168.1.1

Portforwarding on the router Ports 445 and 7001.

Windows FileSharing is turned on everywhere.

This results in a situation where:

- the NAS is visible to SMB for Windows File Explorer on another machine connected wirelessly to the routher, other than the host.

- The NAS is accessible through a browser on the host machine, but trying to open in File Explorer has a "Not Found" error.

- The NAS has a route to the internet.

- The NAS is not visible as a device in my router's client list.

In all my trial and error and such so far, this feels like an issue with authentication on the host machine, but I have reset the credentials several times to no avail; or an IP conflict somewhere, which explains the intermittency -- as I said, on very rare moments, the whole thing seems to be working as planned, only to disconnect or not persist past a reboot.

My other thought as to why the SMB share works on a second machine and not on the host is that I've somehow got SMB trafficgoing round in circles on the host, but I'm not competent to know if that's the case or how to fix it if it was.

HELP!