Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[J-L]

Hi all,

I've got an issue with my DNS-323. I recently lost access to it from my computer.

My set up is:

1. DNS-323 firmware 1.06 (w/ 2 2Tb Seagate drives in RAID-1) connected to a WRT-54G version 5.
2. I've got a PS3 connected through the router and it can access the files on the NAS (although periodically I see a 'the PS3 was disconnected from the server' message, but I can still access the files.
3. I've got a laptop running Windows 7 and ZoneAlarm (although for the purposes of debugging I've turned off ZoneAlarm and enabled Windows Firewall.) and it's connected via wifi.

When I originally purchased my NAS I was using a laptop with Windows XP, and there were no mapping issues. It seems that after I bought my new Windows 7 laptop, that these issues have developed (coincidence? maybe...).

Now, I've lost access to my DNS-323 from my laptop. The Easy Search Utility shows the device, along with the two volumes in the Drive Mapping section. When I try to assign a drive letter to a volume, the utility briefly freezes, and then I receive the 'Failed to Map Drive' error message.

When I try to map the network drive, the drives don't even show up, so I guess I can't manually map them that way.

For my Windows Firewall, I've enabled the Easy Search Utility, so nothing's being blocked.

Please help!!

[jamieburchell]

Are you mapping the drives by the NAS name, or IP address? Can you ping the NAS by either.

Have you tried actually uninstalling ZoneAlarm and disabling the Windows Firewall while testing? I.e. not just turn ZoneAlarm off.

[J-L]

Hi Jamie,

Thanks for your helpful response. I'm able to ping by IP but not by name.

I tried uninstalling ZoneAlarm (and rebooting), and turning off Windows Firewall but am still encountering the same error. As an added twist, I had previously enabled iTunes sharing on my NAS and am still able to access and play music from the NAS via iTunes on the same computer.

Quite odd...any more suggestions please?

[fordem]

What did you set for network location in Windows 7 - home, work or public?

It needs to be either home or work.

[J-L]

Hi Fordem,

I have my network location set to work. Actually, I just found something that may or may not be interesting. As per Easysearch, the DNS-323 IP is 198.168.1.101, but under Windows Network, I can see the NAS under Storage, and when I click on properties, the address is 192.168.0.32.

Does that mean anything?

[jamieburchell]

If you can ping the NAS by IP, can you map your drives / access your shares that way too?
E.g. \\192.168.x.x\Volume_1. If so, it sounds like you have name resolution issues.
192.168.0.32 is the NAS's default IP address I think?
Have you set a static IP address for the NAS, or is it setup to use DHCP?

[J-L]

Wow...

I'm not exactly sure what happened, but I seem to have regained access to my NAS.

What I did (and it probably makes no logical sense), is that within  Easysearch I manually changed the IP to 192.168.0.32, because I got the crazy idea that if I matched the two addresses, then things might work out.

Of course, as a result, I wasn't able to map my drive using \\192.168.1.101\Volume_1. So what I did was manually change the IP back to 192.168.1.101 within Easysearch, and once I did that, I was able to map the drives within it...? 

Not exactly sure what that means, but everything seems to be working now.

Thanks for all your help! 

[jamieburchell]

It will certainly help if your NAS and computer are on the same subnet
Setting a static IP is best IMO.