Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
This is driving me crazy...
Every now and again (it's probably happened 3 or 4 times in the 6 months I've owned it), my DNS-323 seems to stop advertising its name on the network, so accessing shares like \\dlink-xxxx\sharename doesn't work. Accessing by IP address, e.g. \\192.168.0.32\sharename, works fine. If I access the web admin pages and hit the "Save Settings" button under "Setup", "Device" (note the device name appears in the 'Name' field, so the device hasn't "forgotten" it) - hey presto! the device is visible on the network once more. I'm running with firmware 1.04, but the problem also occurred with 1.03.
Has anyone else seen this?
Offline
Add the dns name and ip address to your hosts file. I assume you are using windows, and it generally has issues with names. The hosts file is in c:\windows\system32\drivers\ect.
Last edited by bq041 (2008-06-24 02:50:36)
Offline
Oh sure, I realise I could use that workaround on every machine on the network (a mix of Windows & Linux), and if I can't find any other solution I'll do that. I was just hoping this was a known problem with the device, with the possibility of a fix in the not-too-distant future.
Just to clarify, even a reboot of the DNS-323 doesn't fix the problem. I actually have to go into the web admin pages and save the network settings. Then a couple of months later I have to repeat the exercise :-)
Offline
I do not believe it is an issue with the DNS. Windows has had known issues with the Windows network and NetBIOS for over 10 years. Half the time it does not see my other windows machines on the network. I think it is more an issue with that than the DNS. The reason it works when you hit the save button on the DNS is because its scripts are written to broadcast the new name onto the network as soon as it is changed so machines will know that the name has changed.
Offline
To manage this issue, I gave a fixed IP to my DNS, and i access it from every machine by its IP. This is probably the easier to do, and as you said, I never had any problem since.
Offline