Windows 10 error message "Can't find server" or "Couldn't locate machine" in FileBrowser

This error message means that no device on the network has responded to the name that you have entered.

If you want to get connected as quickly as possible, use an IP address instead of a network name. You can return to this page later to try the network name once you know that FileBrowser will connect.

Home Environment

  1. In FileBrowser's "Name or URL" field enter just the computer network name and do not prefix with "HomeGroup", "WorkGroup" etc. If you normally use a UNC path such as "\\computername\sharename\foldername", just enter "computername" (without the quotes) into the "Name or URL" field.

  2. Try adding ".local" to the end of the computer name.

Work Environment

  • In a work environment you may need the DNS name of the target file server in FileBrowser's "Name or URL" field. Your system Administrator will be able to tell you this.

    However if you wish to find out for yourself
    Start a Command Prompt, simply press the Windows key and type 'Command" and select the Command Prompt App result that appears

    Windows 10 error cant find server or couldnt locate machine

    Then in the Command Prompt app type the word "ping -4" followed by your computer name and press return, if you dont know the name of your computer you can find out here. The network name of the Windows machine in this example is computer3.

      C:\Users\John Smith>ping -4 computer3
      Pinging computer3.stratospherix.com [192.168.1.3] with 32 bytes of data:

    In this example "computer3.stratospherix.com" should be entered into the "Name or URL" field.

Options

I have a different version of Windows

Back to main
Which version of FileBrowser is for me?
Compare FileBrowser Versions

Unsure which version of FileBrowser is for you? Check out our comparison page.