TerraMaster Forum

Posted: **03 Jul 2021, 08:24**

For some reason I cannot access my NAS via SMB (in windows explorer) when using the machine name like ... \\ServerName\

I can only see the list of shares when I navigate by IP Address like ... \\192.168.1.64\

When I navigate via Sever Name, I am prompted to enter credentials, and after I provide them, it fails to connect. However when I navigate by IP address, I am not prompted at all, and I can see the list of shares as I would expect.

I don't understand why, because the DNS locally resolves the machine name to the IP address correctly when I ping the server name so I have to assume that this has something to do with the samba configuration internally.

FWIW, I am using the latest version of Windows 10 with all the current updates. Please let me know if there is some kind of configuration file I can modify to change this behavior.

I haven't' yet set a static IP address in my Router for the NAS so it's entirely possible the IP address could change later. Also, the NAS appears in the list of network devices in Windows Explorer like the other PC's on my network, but clicking on it fails in the way described above. Using a Name is preferable to typing in an IP address when navigating machines.

Posted: **04 Jul 2021, 12:29**

This may be related to your computer system analysis, you can try to add "192.168.1.64 ServerName" in the "C:\Windows\System32\drivers\etc\hosts" file.

Posted: **07 Jul 2021, 23:54**

{L_BUTTON_AT}TMRyan

Thanks for the reply however I solved the problem myself. I found that when I tried to use

Code: Select all

NET USE \\ServerName\Share

from the console, I got an error 1219 which reads ...

Code: Select all

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. 
Disconnect all previous connections to the server or shared resource and try again.

I then used

Code: Select all

NET USE

by itself and found results like the following ...

Code: Select all

C:\>net use
New connections will not be remembered.

Status       Local     Remote                    Network

-------------------------------------------------------------------------------
                       \\IP-Address\Share        Microsoft Windows Network
The command completed successfully.

I was then able to use

Code: Select all

net use /DELETE \\IP-Address\Share

to get rid of the second connection. I believe that connection to the IP address was added when I used the TNAS-PC app, since it maps drives and opens folders using the machine IP address. You can add this solution and debugging steps to your knowledge base for when the next persons asks. For what it's worth, using the HOSTS file should be the last option since it only works on one machine in the network. Also, since I mentioned that DNS resolution was working, changing the HOSTS file would have done nothing. Thanks Again!

TerraMaster Forum

Cannot Access TNAS SMB Service by Name .. Only by IP Address

Cannot Access TNAS SMB Service by Name .. Only by IP Address

Re: Cannot Access TNAS SMB Service by Name .. Only by IP Address

Re: Cannot Access TNAS SMB Service by Name .. Only by IP Address