I'm having trouble accessing an SMB share from a Windows Server 2025 machine in my domain-joined environment. This NAS setup, which is connected through a VIP pool, works fine from my Windows 11 laptop on a different subnet. However, when I try to open the share on the Windows Server, it gives me the error: "The specified network name is no longer available." I've done some troubleshooting: I've pinged the NAS VIPs, checked port 445, reviewed the firewall settings, and confirmed the routing configuration is correct, but I'm still stuck. Can anyone help?
4 Answers
It's puzzling why you have multiple NAS VIPs. Just try the one your laptop accessed successfully. Make sure you can ping it first, both by IP and hostname. If possible, connect your laptop to the same VLAN as your Windows Server and check if you can still access the share. Also, when on the Windows Server, use the 'net view' command to see if the share shows up. If it does, you might want to disconnect and try remapping it with the right credentials. No need to enable SMBv1 at this stage.
First, try accessing the share using the NAS's direct IP, like \192.168.45.10sharename. If that works, you might need to tweak the DNS search order in the network adapter settings on your Windows Server. If that doesn't do it, consider giving the Active Directory computer account of your Windows Server read permissions on the root share folder. Also, changing your settings to prefer IPv4 over IPv6 in the registry could help. Check this guide for more info: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows.
Hey! Have you enabled insecure logins for SMB? Sometimes that can cause issues. You can find details on how to enable it here: https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3. Let me know if it makes a difference!
I see you’ve already pinged and checked access over port 445. That's good! Did you try pinging the share by both its IP and hostname? One more thing to consider is enabling SMB V1. It’s disabled by default because it’s not secure, but it would be worth it to test if that’s the issue here. Just remember to turn it off afterward if it works.
I can ping both IPs and the hostname with no issues, but I haven’t tried SMB V1 yet.
Yes, I enabled that setting, but unfortunately it didn't help.