Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
I've searched for a clear solution to this issue (I'm sure there is one) but no success. Here is my problem and setup.
I've installed DNS-323 fine - 2 volumes - Volume_1 and Volume_2
I have the 323 plugged into my wireless router [iinet standard 4 port Belkin]. I access the 2 drives over my wireless home network. That works fine.
I've setup a STATIC IP for the 323 which is 10.1.1.25 via the DLINK setup tool.
I have two laptops that I used to share/access (and backup to) the 323. Both running Vista.
I've successfully MAPPED each volume (R and S) drives and they appear as "Volume_1 (\\dlink-ABCDEF)" and "Volume_2 (\\dlink-ABCDEG" under file system and I can click on each R and S drive and save/read files OK. Both laptops have mapped the drives successfully (although one took more effort than the other, indeed I couldn't use the DLINK setup tool for one laptop).
********
My problem is that when I reboot the laptop I get an error on reboot. Both R and S drives appear in the file list but they don't have connectivity. It appears that the "name" associated with each drive [eg DLINK-ABCDEF] isn't mapped correctly.
Now I've found a work around but I'm not sure why it works and I don't like having to do it EVERY reboot. If I issue from DOS prompt the command "PING -a 10.1.1.25" then on the second or third attempt at this I find the PING actually returns the "DLINK-ABCDEF" name in the results (the first couple of times there is NO "DLINK-ABCDEF" associated with the 10.1.1.25 PING result.
After the name association works; I then wait about 30 secs and if I click on the R or S drive in the Windows Explorer list, I'll get the network connection back again. Then everything works fine.
Of course the problem is that my backup software (memoe free included) requires me to "kick-start" the connection using this method each time before it'll realise the drives are available to backup to.
********
My questions:
- How come these connection (DNS mapping?) dies everytime I reboot.
- Why does the "PING -a 10.1.1.25" eventually [after a few tries] reset the named drive mapping?
- Is this the best way to setup the DNS so that I can access it readily from each laptop, wirelessly?
Any advice would be much appreciated,
Thanks. Roy.
Offline
Your problem is most likely one of name resolution - map the drives to the ip address rather than the host name and see if that resolves it.
If you do not have a DNS server on your network with the appropriate host entries for the DNS-323, then name resolution is dependent on Microsoft's old "master browser" which is the most reliable, especially in a mixed OS environment.
Offline
Thanks fordham,
That fixed my problem. And not unexpectedly it *seems* that my wireless comms to the drive under IP addy is quicker than the name resolution.
Cheers, Roy.
ps: still wondering why the PING would come back with name resolution after a while. Is there something on the 323 that get's woken up by the ping (link the DNS?).
Last edited by roy57a (2009-02-10 11:56:09)
Offline
Pages: 1