LinkStation Mini (LS-WSX2.0TL/R1) erratic connection problems

[distill]

In my home network I can always ping 192.168.0.11 successfully. That is my LinkStation Mini (LS-WSX2.0TL/R1) on the AUTO mode. I can also go to the browser interface http://192.168.0.11 always and it gives a welcome screen with a rotating circle. If I'm lucky, I can get past the rotating circle onto the interface. But at the same time I have a problem connecting to the NAS.

If I do run \\192.168.0.11, it will say Windows cannot access \\192.168.0.11. If I use the NAS Navigator2 (2.78), the drive's icon will just not appear even pressing Update several times.

But then, at times, the connection does work. For example if the drive has gone sleeping, I can send wake-on-lan messages and it may wake up (with the huge waiting time of 1min 55sec). Then it goes to sleep again. Perhaps NAS Navigator2 is not able to pass the wake-on-lan messages through (don't know why that would be blocked). While at the same time manual wake-on-lan (WakeMeOnLan.exe or WakeOnLan.exe) work without problems.

There is another problem too: I have another computer on the home network and with that there are no problems. When that computer is on, the drive stays on without problems and I can always connect. But, on my main computer often I can't connect to LinkStation even at the same time the other computer can connect. So it is erratic.

What can cause this behavior and why is my manual wake-on-lan more "powerful" than NAS Navigator2 running? Isn't that application supposed to send the magic packet every 3 minutes?

[joma90]

I would not know if it send a magic packet every 3 minutes  as i have never used the auto feature ever. If one pc works fine but another doesnt. I would suggest its a firewall issue.

[distill]

Does someone know whether it is indeed NAS Navigator2 that is sending the periodical (3min?) wakeup packets to LinkStation or if it is some service or something else? I checked already Windows Firewall, at least I certainly haven't blocked outbound traffic for NAS Navigator2 or anything like that. Still, it can be said that NAS Navigator2 is NOT waking up LinkStation, however if I simply do the wakeup call from WakeOnLan.exe, the LinkStation wakes up.

There is no firewall setting that would allow WakeOnLan.exe and disallow NAS Navigator2 that I'm aware of.

[joma90]

It has to be a firewall issue on your main or a network setting or a setting or application in that pc because you stated this "I have another computer on the home network and with that there are no problems. When that computer is on, the drive stays on without problems and I can always connect. But, on my main computer often I can't connect to LinkStation even at the same time the other computer can connect."

That tells me its that pc. It would not make sense to blame the linkstation or software if one of the pcs work fine with no issues. Get wireshark and see your traffic that way. Also try disabling the firewall. Its not going to hurt. Also any antivirus/spyware. That can cause an issue sometimes like norton or avg,

[distill]

I'm afraid I don't know how to use Wireshark. It would help me tremendously if I knew how Buffalo's wakeup is supposed to work. Is it NAS Navigator2 or something else that periodically wakes up (keeps from going to standby) LinkStation?

Also I tried disabling Windows Firewall, ESET antivirus and router Firewall options, but no difference. As soon as I fire WakeOnLan.exe, the drive starts to wake up. According to http://sg.faq.buffalo-global.com/app/answers/detail/a_id/14657/p/31,33,3670 it would seem that perhaps NasNavi.exe is supposed to send the wakeup packets. I do not know what else to disable other than those firewalls / antivirus I already disabled.