Print

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

[rector]

Hi, I have a 323 on my network, and whenever its turned on theres no access until easy find is used. It shows on the network but no access is possible unless the configuration is opened, and then go to any section of the config, change NOTHING, and then save. Immediately the nas is accessable from anywhere on my mixture of xp/7/8/pcs and media player.

Before easy find is used it can be pinged ok, and scanning the network shows the 323 by its manually set ip address. Its outside the pool set by the router, and the same subnet is used, as is the network name. There is no homegroup setup.

Raid is not used, the 2 drives are just separate volumes.

I also have a buffalo nas which works perfectly on the same network, any suggestions

[dosborne]

Sounds like maybe it is just a matter of timing. Once the DNS (Domain Name Server, not the DNS323)server updates the rest of your network can "find" the DNS323 by name.

[rector]

Sounds like maybe it is just a matter of timing. Once the DNS (Domain Name Server, not the DNS323)server updates the rest of your network can "find" the DNS323 by name.

Hi, and thanks
So your suggesting it may just take more time for the dns323 to be accessible on the network? If so several hours dont work. I did explain incorrectly before that windows CANT see the dns323 unless i use easy find. it definately pings ok ()even before using easyfind), and using a lan scanner shows the dns323. Any suggestions for a fix would be great.

[ivan]

A couple of things.

You appear to be saying that you have computers running BEFORE you switch on the NAS.  If this is the case then the computers will not 'see' the NAS because it does not announce itself to the network.

Is it possible to 'see' the NAS using 'Entire Network' under 'My Network Places' in windows explorer on win XP or even using the 'view as ftp' when using netscan?

I would recommend that you try having the NAS powered up and ready before switching on any of your computers and letting us know the results of that test.

As an aside, all of our NAS are powered up 24/7 and are always accessible to all computers - even the laptops clients bring in that are running windows.

[fordem]

It makes no difference if the NAS is switched on before the computers or after, the computers neither know nor care if it's there BEFORE they attempt to access it - assuming a properly configured network, they will do a search on the first access attempt and either succeed or fail.

The city I am in suffers frequent power outages and my network is supported by a UPS wihich is configured to automatically shutdown my servers (DNS-323 included) and restart them after power is restored, however, because my DNS-323 does not support "auto turn-on" it is the only device that remains off, and I will often be unaware of this until I attempt to access it  - it appears in "My Network Places" but when I click on it I will get a message saying "\\DNSNAS\Volume_1 is not accessible" at which point all I need to do is power the unit on, wait for it to come ready and then retry.

My network may be a little unusual in that I run an inhouse DNS server that allows the NAS to be located based on the name, but, the same results can be achieved by assigning the NAS a static ip address and then using that address - for example \\192.168.0.32\Volume_1.


Locating the unit is not the issue here - because it can be pinged (first post, second paragraph) - this would appear to be some sort of access rights type problem,.