Can't connect to NAS

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Can't connect to NAS

Lizard1977

1366 posts

Uber Geek
+1 received by user: 190

# 214219 2-May-2017 16:13

I'm having some problems connecting to my NAS, a QNAP TS-112. I can login to the web interface without any problems, but my mapped network drive isn't accessible. If I type in the name of the share (i.e. //QNAP-NAS/) I get the same problem. Everything is connected via ethernet, and was working fine a couple of days ago. I get the same problem on my SP3 when connecting via wifi.

I did update the firmware recently, but I can't remember if the mapped network drive worked afterwards or not. The only thing I can think of to try is to reset it to factory settings, but I'd rather avoid that if I can possibly help it.

Any suggestions?

solutionz

588 posts

Ultimate Geek
+1 received by user: 188
Inactive user

# 1774369 2-May-2017 16:19

Hostname resolution (i.e. \\QNAP-NAS\) relies on NetBIOS or similar mDNS technology (Bonjour etc) which isn't supported by all devices and doesn't traverse some VPN's or Wifi networks.

i.e. AFAIK Android, iOS mobile etc doesn't support NetBIOS.

Can you connect via IP or from a Windows PC?

(BTW your slash's are going the wrong way, see mine above)

Lizard1977

1366 posts

Uber Geek
+1 received by user: 190

# 1774374 2-May-2017 16:28

Both PCs connecting are on Windows, and all was fine a couple of days ago. I checked NetBIOS and its set to default. Typing in the IP gives the same problem. The Windows troubleshooter says "The remote device or resource won't accept the connection."

As for the slashes, I mistyped in my message, but I was using the right ones when trying to access the share.

solutionz

588 posts

Ultimate Geek
+1 received by user: 188
Inactive user

# 1774376 2-May-2017 16:31

What do you get if you ping the hostname?

ping QNAP-NAS

Jarno

269 posts

Ultimate Geek
+1 received by user: 49

# 1774409 2-May-2017 16:48

Check the qnap forums. There are some other people with the same problem after upgrading to the new firmware. It looks like a bug with SAMBA on older models.

Lizard1977

1366 posts

Uber Geek
+1 received by user: 190

# 1774670 2-May-2017 22:18

I can ping the NAS no problems. Same if I ping the IP address.

mclean

398 posts

Ultimate Geek
+1 received by user: 92

Subscriber

# 1774794 3-May-2017 10:06

No doubt you've looked on the web and found countless cases of this very issue and just as many solutions, none of which work. The only thing I have found to be successful is to wait 24 hours and it all comes back! Maybe that begs a diagnosis, but I have no idea what.

McLean

timmmay

14889 posts

Uber Geek
+1 received by user: 2795

Trusted

Subscriber

# 1774796 3-May-2017 10:17

Did you install a Windows update around the time it became inaccessible? Those sometimes reset your network settings.

Quinny

539 posts

Ultimate Geek
+1 received by user: 68

Trusted

# 1774910 3-May-2017 12:51

There is a finder you can download from QNAP. At work so dont have here. Mine has turned to crap this year with same issue. Cant find. All started after firmware update plus when added 2nd net cable to use the dual option. Despite much troubleshooting been unable to find out why suddenly windows cant see it. I use the app to find it ip and go from there. No luck even when made static. My new Synology is so much better and never misses a beat. Pretty much wasted $2000 on the Qnap sigh.

Rickles

1989 posts

Uber Geek
+1 received by user: 171

Trusted

# 1775888 4-May-2017 20:47

Peter - I seem to recall losing my mapped NAS drives after a Firmware update ... on a D-Link ShareCenter.

Went into interface, cancelled all shares and then reset them for each Folder. After that they all came back in Network (Win 10) and I could also map any of them again.

coffeebaron

5475 posts

Uber Geek
+1 received by user: 2546

Trusted

Lifetime subscriber

# 1775974 4-May-2017 23:24

SMB version 1 , or something like that. I'll try remember to look at mine tomorrow.

Chorus has spent $1.4 billion on making their xDSL broadband network faster and even more now as they are upgrading their rural Conklins. If your still stuck on ADSL or VDSL, why not spend $195 on a master filter install to make sure you are getting the most out of your connection?
I install - Naked DSL, DSL Master Splitters, VoIP, data cabling and general computer support for home and small business.
Rural Broadband RBI installer for Ultimate Broadband and Full Flavour

Need help in Auckland, Waikato or BoP? Click my email button, or email me direct: [my user name] at geekzonemail dot com

Lizard1977

1366 posts

Uber Geek
+1 received by user: 190

# 1776024 5-May-2017 07:58

I lodged a ticket with QNAP and last night they used TeamViewer to login and fix things up for me. I can see my NAS folders in Windows now, but have a new problem in terms of Windows Credentials. When I try and open a folder it asks for login details. I can login with the admin account, but my normal user account on the NAS (which has the same privileges as the admin account) is rejected. I had a similar problem about 2 years ago which another user on GZ helped to fix), but I can't work out what to do here. I'm going to email QNAP again and see what they suggest.

solutionz

588 posts

Ultimate Geek
+1 received by user: 188
Inactive user

# 1776052 5-May-2017 09:31

Does the user have a password?

If not ensure "Password Protected Sharing" is disabled on your PC for the network type you are connected as (Public or Private) or both.

BTR

1513 posts

Uber Geek
+1 received by user: 459

# 1776249 5-May-2017 13:45

The NAS doesn;t have a firewall running on it does it, if so turn it off and see if you can connect then , if so you need to add a rule to allow incoming traffic on the SMB port (445 TCP)

nicmair

102 posts

Master Geek
+1 received by user: 5

# 1776308 5-May-2017 14:12

I had a similar issue (not on a QNAS box mind you, was actually a Windows issue) and had to add a set of credentials in credential Manager. Adding some credentials here, (using a known working account on the NAS) worked a treat. Before that I could see the NAS, but just could not connect to it.

Lizard1977

1366 posts

Uber Geek
+1 received by user: 190

# 1777568 8-May-2017 10:40

So everything is resolved (more or less). I've regained access to the NAS via Windows, and it seems to be working okay. The Windows Credential issue seemed to be solved by simply deleting the user account on the NAS and recreating it. So now I'm just going back to tidying up the folder structure on the NAS (what I was doing when the problems started). The only thing I need to fix is the location of sources in Kodi on Amazon Fire TV. I tried to fix things up late last night but it was proving to be a hassle. Might be simpler just to nuke my current Kodi setup and start from scratch.