View original (French)

Blocking NAS Freebox Pro access on certain PCs.

Solved
huks Posted messages 4 Registration date   Status Member Last intervention   -  
steph810 Posted messages 1865 Registration date   Status Member Last intervention   -

Hello everyone,

I'm reaching out to you because I'm completely stuck on a network issue in our association and it's starting to drive me crazy!

Our setup:

  • We have a Freebox Pro.

  • The NAS (local storage) is properly enabled.

  • Since we have two different rooms, the PCs are connected via 2 Netgear switches.

The problem: The NAS works... but not everywhere. I have 3 PCs that can access it perfectly and open the files. However, for all the other PCs in the office, it's impossible.

Yet, when I do a ping from the command prompt on the PCs that are blocked, the NAS responds perfectly (0% loss). So the PCs can "see" the NAS on the network.

But as soon as I try to open it (via Windows + R or in Explorer), I get an immediate error saying: "Windows cannot access . No username or password is requested, it blocks before that.

What I've already tried:

  • I tried enabling the SMBv1 protocol in Windows features.

  • I attempted to modify the registry key AllowInsecureGuestAuth to force guest access.

  • I tried using the Windows Credential Manager to manually enter the admin credentials.

Nothing works, the commands are blocked or unresponsive. Could this be a security block specific to Windows 11 on these machines? Or is it a communication/configuration issue between our two switches isolating certain PCs?

If anyone has a specific idea to help me out, I’m all ears!

Thank you very much in advance for your help.

2 answers

  1.
    steph810 Posted messages 1865 Registration date   Status Member Last intervention   152
     

    Hello, to be done on all machines:

    net view \\IP_OF_THE_NAS

    What errors does it return to you?

    • System error 53 --> network resolution.
    • System error 5 --> rights.
    • System error 67 --> SMB share.
    • Error 1231/1232 --> network
    0
    1. huks Posted messages 4 Registration date   Status Member Last intervention  
       

      Thank you for your response. On all PCs, system error 53 is displayed.

      0
      1. steph810 Posted messages 1865 Registration date   Status Member Last intervention   152 > huks Posted messages 4 Registration date   Status Member Last intervention  
         

        Thank you,

        Have you tested them with the IP? Have you tested them with the NAS name?

        We'll see if it's a name issue or SMB.

        net view \\NASName

        And the results of:

        Test-NetConnection NASIPAddress -Port 445

        If it is properly on the default port.

        The script above can help you diagnose, check the SMB and remote shares tabs.

        0
      2. huks Posted messages 4 Registration date   Status Member Last intervention   > steph810 Posted messages 1865 Registration date   Status Member Last intervention  
         

        The Net view command with the NAS name shows the same error as for the IP (system error 53). The Test-NetConnection command, on the other hand, shows: TcpTestSucceeded: True.

        0
  2. steph810 Posted messages 1865 Registration date   Status Member Last intervention   152
     

    Thank you for testing on a single machine that is not working:

    See the config:

    Get-SmbClientConfiguration | Select-Object EnableInsecureGuestLogons, RequireSecuritySignature, EnableSecuritySignature, EnableMultiChannel

    Allow guest access without a password:

    Set-SmbClientConfiguration -EnableInsecureGuestLogons $true

    To revert, replace $true with $false

    it's just a test.

    If it works, we will see later about securing it a bit more

    0
    1. huks Posted messages 4 Registration date   Status Member Last intervention  
       

      Thank you. I tried the first command on two PCs (one that works and another that doesn't). Here are the results:

      • On the PC that doesn't work: all 4 categories are set to True.

      • On the PC that works: RequireSecuritySignature is set to False, while EnableSecuritySignature and EnableMultiChannel are set to True.

      By setting RequireSecuritySignature to False, it worked! I will try it on another PC. Thank you for your help, you have been a great help. Have a nice day!
      On another PC, it worked too! To get everything to work, I had to enable AllowInsecureGuestLogons and set RequireSecuritySignature to False. Thanks again, have a nice day.

      0
      1. steph810 Posted messages 1865 Registration date   Status Member Last intervention   152 > huks Posted messages 4 Registration date   Status Member Last intervention  
         

        If everything is okay, don't forget to mark it as --> Resolved topic

        0