Windows 10: my newest hardware requires SMB 2 min but my NAS is SMB 1, so I cannot access Network Drives

Also posted here:https://h30434.www3.hp.com/t5/Business-PCs-Workstations-and-Point-of-Sale-Systems/newest-hardware-requires-SMB-2-min-but-NAS-is-SMB-1-so-I/m-p/9101915#M46376my newest hardware requires SMB 2 min, but my NAS is SMB 1, so I cannot access Network DrivesProduct: HP Z2 Tower G9 Workstation Desktop PC Operating System: Microsoft Windows 11 HP Z2 Tower G9 Workstation Desktop PC requires the newest hardware requires SMB 2 min, but NAS is SMB 1, so I cannot access Network Drives, what do I have to do? I have many old PCs too, Windows 10 in the network connected... no access problems fo

:)

 

Bridged Networks and SMB on a NAS

Several factors could cause the intermittence of the issue. It's possible that the network configuration is not being saved properly or that there is a conflict between the IP addresses assigned to the different devices on the network. Another possibility is that there could be an issue with the network hardware, such as the router or the network card on the host machine.

To troubleshoot the issue, you could try the following steps:

1. Check the network settings on all devices to ensure they are configured correctly, and there are no conflicts in IP addresses.

2. Verify that the network hardware, such as the router and network card, is functioning correctly and are up to date with the latest firmware updates.

3. Try temporarily disabling any firewalls or antivirus software to see if they are blocking access to the NAS.

4. Check the event viewer on the host machine for any errors or warnings related to the network or SMB service.

5. Try accessing the NAS using a different protocol, such as FTP or SSH, to see if the issue is specific to SMB.

If none of these steps resolves the issue, it may be necessary to seek additional assistance from a network specialist or the manufacturer of the NAS.

 

Bridged Networks and SMB on a NAS

You are welcome, Matt; It's good to hear that turning off the firewall resolved the issue for you temporarily. Regarding the "Operations in Progress" notification during shutdown, it is possible that Windows was applying some updates or performing some other background tasks during the reboot. This could potentially cause issues with network settings or firewall rules.

Regarding the ff-ff-ff-ff-ff-ff MAC address, it is the broadcast MAC address, which is used to send a message to all devices on the network. This is a normal address to see in the ARP table. Since you are still unable to access the SMB share from another machine on the network, there could be a few things to check:

1. Ensure the SMB service is running on the NAS and the share is configured correctly.

2. Check that the network settings on the second machine are correct and that it is on the same subnet as the NAS.

3. Make sure that no firewalls or security settings on the second machine block access to the NAS.

4. Try accessing the NAS via its IP address instead of its hostname to see if that makes a difference.

5. You can also try resetting the network settings on the second machine and see if that helps.

If none of these steps works, it may be helpful to consult the documentation for your specific NAS and also check the logs on both the NAS and the second machine to see if there are any error messages or clues as to what might be causing the issue.

 

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!