Linkstation Live LS-CHL only visible when XP laptop is ON

[Snaques]

I have a problem with my new 500GB LS-CHL (firmware 1.33) where the drive is visible in NASNavi on both XP and Windows 7 computers, BUT only when the XP laptop is connected. When I disconnect the XP computer, the W7 computer loses the LS drive. Any explanations?

 

Also I can map the drive only on my XP. This is very annoying since the XP computer is only rarely in use.

 

[AngelsAbys]

Please try directly connecting the NAS device to the W7 computer, disabling firewalls, defender, anti-virus, etc to see if you can establish a communication via this route since there will be no direct network communication.  Try both static and DHCP addresses to see if there is communication going on while directly connected.  If the unit is visible and controllable via that route show there is a communication problem within the network somewhere

[Snaques]

Actually, the LS is visible in "My Computer -> Network" and also through web browser with the ip address even when XP PC isn't connected. The existence of XP only seems to affect the NASNavi app.

 

This doesn't solve the problem tho.

1. In My computer W7 only allows me to open LS in media player.

2. When I try to log in on web browser, I always get a message saying "The current session has expired. Please sign in again."

 

So what to do? I will still try the direct connection soon, but the amount of problems I have with the device is just ridiculous.

[Dustrega]

 

1. Is the switch on the unit set to AUTO?
2. Is the NAS IP address pingable from the Win7 machine without the XP machine on the network?
3. Is the NAS IP address pingable from the XP machine?
4. When you're given the "The current session has expired" message when attempting access to the GUI via Win7 does it give you the option to sign back in?  Does this occur on other browsers?

 

[Snaques]

Ok, I restored the factory defaults and connected the LS directly with a cable to my W7 PC. The PC is otherwise completly offline.

 

The result is that:

1. I can see the LS in "my computer -> Network" as some windows media player file/folder.

2. I can again access the settings through the web access when using the direct IP.

3. I cannot see the LS at all in the NASNavi2

4. I can ping the LS

 

So basically I can see the LS in all ways but the NASNAvi, but I cannot use it in any way.

 

What should I try next? :smileyindifferent:

 

I have the DHCP Enabled in the settings.

 

My router is D-Link DI-524 (not connected atm) and I don't know what you mean by setting it AUTO?

[Dustrega]

Since DHCP is enabled on the NAS it is trying to obtain an IP from your computer.  Here's the rub, the computer won't serve an IP when requested so the NAS will timeout to an Auto-Configuration IP (169.254.xxx.xxx).  You'll need to set your computer which is directly connected to a static IP with the same except it will have to differ from the last octet of the NAS (169.254.xxx.yyy).  However, one thing that I am curious about is that the NAS Navi can't see the device (which is on DHCP) and yet you're able to ping it.

[Snaques]

I have been doing some tests and it seems like this is somehow connected to the F-Secure. When it is running I am having problems with the NASNavi, but when it's off then all works just fine.

 

It is often said that one should try using the Linkstation with firewalls turned off. Ok I tried this, but naturally I can't continue working with the Firewall down. Is there some port I should open or an application I should add on the allow-list?

 

Interestingly even with Firewall on, I can still ping, use the web access and see the LS in 'Computer -> Network' as a Media Device.

 

PS. The IP of my LS is 192.168.0.1xx. You seem to talk about 169.254.xxx.xxx addresses.

[Dustrega]

Some firewalls will automatically detect traffic on certain ports and then "learn" based on what you want the firewall to remember for traffic.  For media sharing I'm not sure which port is specifically used, but I'll see what I can find.

[Snaques]

Actually, I seem to found the cure. I posted this comment to another thread, which seemed to solve the problem:

"I think I found the "remedy" in my case. I noticed that in F-Secure Internet Shield 2010 the NASNavi2 was set to 'allow' for inbound traffic. However, the outbound option was still set to 'prompt'. Changing this to 'allow' seems to have fixed my problems for the time being."