share mounting stopped

English Networking
1

I have a TS-230 that has been running well for a couple years.

I am running simply as a workgroup. No domain controller stuff. All clients are Win10.

I just made some DNS changes, or I THINK all I touched was DNS for the 230 and its DHCP and now no clients can mount shares.

This is a bit of an emergency. My wife is REALLY upset!

For a PC on the same physical network as the NAS that could always access shares:

net view \\myserver

times out.

net use H: \\myserver\home

times out.

File manager is not showing myserver anymore in the Networks list.

I really did something and have no idea what I stepped on.

I hope someone can set me straight and get this working…

thanks!

Oh, I restarted the NAS by pulling the plug and then reinserting. I could not find a simple “reboot” option in the control panel. Only reset to factory settings? Or upload a saved settings, and of course I do have that…

2

Hi and welcome to the forum. :slight_smile:

I can’t help with the missing shares, but to reboot your NAS, your logged-in user must be a member of the ‘administrators’ group. If they are, click on your username in the QTS desktop (near the top-right), and you’ll see the usual shutdown/restart options:

Screenshot_20250526_070953
Screenshot_20250526_070953510×517 51.5 KB

3

And there is the reboot option right up their with my account pull down!!!

I went digging all over in the network settings and system info and everywhere else but their. Too smart for my own good!

I fixed my shares problem. Turns out it WAS DNS.

net use h://myserver/home

Needs DNS to resolve myserver to an IP and that was returning a wrong IP addr. GRRRRR.

Fixed DNS and then all my login SHARES work.

Crisis averted and wife cooled down. :wink:

Back to properly fixing up my DNS instead of this hack-of-the-day.

1 Like
4

You can also use the IP (if it is fixed) instead of the hostname. You can also edit your hosts file to resolve hostnames. Lots of different options. You can also map a permanent drive instead of running “net use”. :slight_smile:

5

We have a dedicated FAQ article that addresses this issue.

Please refer to it for a solution: