Synology Nas access Issues over Wifi only.

[Sloecooker]

Where I work we have a Synology Nas which is usually easily accessable from any machine, being wired or wireless. Recently it has developed a 'random' connection issue when trying to access it via wifi.  It probably isn't actually random but a combination or ' Local device name is already in use', 'you might not have permission', 'multiple connections to a server by the same user using a different name are not allowed' and general server is not there/ the name is not available any more errors have started happening. Sorry for the long sentence. Some information:

I can access it from any machine using ip address in browser

I can ping it

I can map it using either server name or ip address both wired and wirelessly

When mapped it is accessable untill a machine restart when the above errors start.

Wired Connection works fine

Problem happens only on windows (7 and 10)

seems fine on linux

I have tried all the things I can think of both server and client side

 

This only seems to be happening since a synology update last week and the errors are inconsistant, for example.....

I mapped one of the two shares using \\server name\share and the other using \\ip address\share. Both worked until I restarted the machine then clicking on the first prompted an error and the second prompted for the password which I entered and the second share worked, as now did the first one since entering password. I restarted the machine and neither worked and gave different errors.

I restarted again and they both worked after the error, password request, no error scenario as detailed above but in the opposite order because the second one i clicked gave an error aswell but then the first prompted for a password.

 

I spent hours using different machines, different versions of windows, different synology users, different windows users ect and came to the conclusion that I have no idea.

 

If anyone can decipher the above nonsense and has any ideas I would be grateful! this wasn't my 'monday morning in work' plan.

[Electronics Wizardy]

Do you have a network diagram? This seems like a issue with your wifi access points, not that nas if I had to make a guess.

 

What does the wifi access points say?

[Sloecooker]

I did think it could be a wireless issue maybe, we have some wireless printers that sometimes work but mostly don't. The Nas is hardwired into the switch, the wireless is handled by a zykel router that was issued by our ISP. It is a managed router but everything else is generally handled by me. This is the second Router they have supplied because the first one stopped working almost entirely. I dont have a Network diagram sorry, it would probably be wrong anyway I think.

[Electronics Wizardy]

1 minute ago, Sloecooker said:

I did think it could be a wireless issue maybe, we have some wireless printers that sometimes work but mostly don't. The Nas is hardwired into the switch, the wireless is handled by a zykel router that was issued by our ISP. It is a managed router but everything else is generally handled by me. This is the second Router they have supplied because the first one stopped working almost entirely. I dont have a Network diagram sorry, it would probably be wrong anyway I think.

Yea that makes me think its the wifi setup, but without logs or more info I can't be sure.

 

MIght be a good option to use non isp provided router and access points

[Sloecooker]

I may be able to get hold of the logs, I think I may have the password somewhere. I have considered asking to get a Decent WAP instead but money / time constraints. I may ask the ISP if they can see any issue, they are being paid after all to manage this stuff!

 

Thank you for your input.

[Master Disaster]

Start by checking the Network Password cache to see how many different accounts each machine has stored for the NAS and removing the cached passwords so you can start again.

 

On both machines having the issue do...

1) Unmap all existing shares.

2) Run "rundll32.exe keymgr.dll, KRShowKeyMgr" in command prompt or the Run dialogue box.

3) Select the NAS (you might have it listed multiple times under its hostname or under its IP, if so do all of them) and click Remove.

4) Once all instances are removed from the cache try mapping the shares again.

 

If you have multiple accounts stored for the same share it can cause Windows to not want to connect. Try to keep only one account stored on each machine accessing the NAS.

 

When handling permissions for a large amount of machines groups are very much required to keep things tidy. On the NAS create a group for each team/section that needs access, assign folder access permission to the group then add the users to the group. Doing it this way means you don't have to mess around assigning each user permissions, just assign them a group and for any edge cases individual folder access can be handled on a per user basis.

[Sloecooker]

I will have a look about that in the morning, aswell as contacting ISP for up to date login information for router!

The Two machines where I first noticed the issue were new laptops, if thats any help?

 

I did also try deleting saved passwords but there were none relating to the nas.

[Master Disaster]

8 minutes ago, Sloecooker said:

I will have a look about that in the morning, aswell as contacting ISP for up to date login information for router!

The Two machines where I first noticed the issue were new laptops, if thats any help?

 

I did also try deleting saved passwords but there were none relating to the nas.

Do other machines running Windows and using WiFi connect to the shares OK?

[Electronics Wizardy]

3 hours ago, Sloecooker said:

I may be able to get hold of the logs, I think I may have the password somewhere. I have considered asking to get a Decent WAP instead but money / time constraints. I may ask the ISP if they can see any issue, they are being paid after all to manage this stuff!

 

Thank you for your input.

Id really try to get your own equeent. Normally you isp doesn't relly want to manage your network, and just gives you access to the internet. 

 

Id give something like iperf or a continous ping a shot and see if there are any dropped connections or lots of retrys to see if there are issues with other apps.

[Sloecooker]

I have tried a win7 laptop over wifi as well which has same problem.

The isp is a local company who manage networks, I dont really understand why they manage ours but I didnt have any input in that regard.

I will try a continuous ping to see if anything shows up as an issue over the wifi.

 

thank you

[Sloecooker]

Here are some ping results, sorry for the formatting. The text is from a wifi linux desktop and the image is from a windows 7 laptop over wifi. A different win7 laptop had similar times but with a few time outs

 

 

 

64 bytes from 192.168.1.73: icmp_seq=92 ttl=64 time=200 ms

64 bytes from 192.168.1.73: icmp_seq=93 ttl=64 time=32.0 ms

64 bytes from 192.168.1.73: icmp_seq=94 ttl=64 time=582 ms

64 bytes from 192.168.1.73: icmp_seq=95 ttl=64 time=54.5 ms

64 bytes from 192.168.1.73: icmp_seq=96 ttl=64 time=1375 ms

64 bytes from 192.168.1.73: icmp_seq=97 ttl=64 time=817 ms

64 bytes from 192.168.1.73: icmp_seq=98 ttl=64 time=618 ms

64 bytes from 192.168.1.73: icmp_seq=99 ttl=64 time=15.6 ms

64 bytes from 192.168.1.73: icmp_seq=100 ttl=64 time=627 ms

64 bytes from 192.168.1.73: icmp_seq=101 ttl=64 time=573 ms

64 bytes from 192.168.1.73: icmp_seq=102 ttl=64 time=3.14 ms

64 bytes from 192.168.1.73: icmp_seq=103 ttl=64 time=3.28 ms

64 bytes from 192.168.1.73: icmp_seq=104 ttl=64 time=838 ms

64 bytes from 192.168.1.73: icmp_seq=105 ttl=64 time=168 ms

64 bytes from 192.168.1.73: icmp_seq=106 ttl=64 time=1241 ms

64 bytes from 192.168.1.73: icmp_seq=107 ttl=64 time=1195 ms

64 bytes from 192.168.1.73: icmp_seq=108 ttl=64 time=624 ms

64 bytes from 192.168.1.73: icmp_seq=109 ttl=64 time=592 ms

64 bytes from 192.168.1.73: icmp_seq=110 ttl=64 time=54.4 ms

 

 

 

 

[Electronics Wizardy]

3 hours ago, Sloecooker said:

Here are some ping results, sorry for the formatting. The text is from a wifi linux desktop and the image is from a windows 7 laptop over wifi. A different win7 laptop had similar times but with a few time outs

 

 

 

64 bytes from 192.168.1.73: icmp_seq=92 ttl=64 time=200 ms

64 bytes from 192.168.1.73: icmp_seq=93 ttl=64 time=32.0 ms

64 bytes from 192.168.1.73: icmp_seq=94 ttl=64 time=582 ms

64 bytes from 192.168.1.73: icmp_seq=95 ttl=64 time=54.5 ms

64 bytes from 192.168.1.73: icmp_seq=96 ttl=64 time=1375 ms

64 bytes from 192.168.1.73: icmp_seq=97 ttl=64 time=817 ms

64 bytes from 192.168.1.73: icmp_seq=98 ttl=64 time=618 ms

64 bytes from 192.168.1.73: icmp_seq=99 ttl=64 time=15.6 ms

64 bytes from 192.168.1.73: icmp_seq=100 ttl=64 time=627 ms

64 bytes from 192.168.1.73: icmp_seq=101 ttl=64 time=573 ms

64 bytes from 192.168.1.73: icmp_seq=102 ttl=64 time=3.14 ms

64 bytes from 192.168.1.73: icmp_seq=103 ttl=64 time=3.28 ms

64 bytes from 192.168.1.73: icmp_seq=104 ttl=64 time=838 ms

64 bytes from 192.168.1.73: icmp_seq=105 ttl=64 time=168 ms

64 bytes from 192.168.1.73: icmp_seq=106 ttl=64 time=1241 ms

64 bytes from 192.168.1.73: icmp_seq=107 ttl=64 time=1195 ms

64 bytes from 192.168.1.73: icmp_seq=108 ttl=64 time=624 ms

64 bytes from 192.168.1.73: icmp_seq=109 ttl=64 time=592 ms

64 bytes from 192.168.1.73: icmp_seq=110 ttl=64 time=54.4 ms

 

 

 

 

Im guessing these pings are very low latency(sub 10ms) on wired?

 

THose are some very bad ping times. I think thats your problem. Try changing things like wifi channel if you can. 

[Master Disaster]

There's no need to mask your internal IP addresses.

 

Did you try using tracert and checking the TTL?

[Sloecooker]

Both of those ping times are from wifi machines, the longer times are from a linux desktop further away through a floor and the lower are from a win 7 laptop about 10 feet from router, the linux times are terrible i know but that machine still always connects fine. It seems to just be windows which is the issue.

 

i did tracert on 3 machines, all wifi

LInux desktop  1  6.914  7.211  7.572 

win 7 laptop(same room as linux desktop) 1  2ms  3ms  2ms

win 10 laptop  1 3ms 2ms 3ms

 

wired times are all sub 1ms

 

sorry, how can i check the ttl for the nas?

Also I masked the numbers to avoid having to explain how its not a security issue should anyone ask who doesnt understand, thank you for mentioning it though.

 

I am trying to get hold of router login information to be able to check logs and channels ect.