Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi all,
just come up with this problem which I hope someone can help with. My network configuration is as follows.
Linksys modem/router connected to ISP (ADSL) DCHP enabled - network printer connected to router - laptops wirelessly connected to router - switch connected to router - DNS323 connected to switch - main PC connected to switch - vista media center connected to switch via homeplug.
I did have a cheap netgear gigabit switch and everything worked fine. However, the switch needed to be reset too often for my liking so I replaced it with a HP ProCurve 1400-8G. Previously, when I tried to connect to the DNS 323 when spun down I would have to wait for a bit for it to wake up and then all content would be available and mapped network drives would behave normally. Now I get an error saying that the DNS is unavailable. Trying to access the drive starts to wake it up but an error is reported. If I try accessing it again a little while later all is fine. Although I can access the drives by repeatedly trying and ignoring thhe error this is a pain, especially on the media centre where WAF is important (wife acceptance factor!). Do you have any ideas how I can prevent the error from being reported and to let the pc just sit around and wait for the DNS to wake up?
Thanks very much for your help
Mark
Offline
This is an interesting one ...
Is the new Procurve a "green switch" that disables inactive ports?
Could you post the exact wording of the error message?
Could you check to see what the link status is when the DNS-323 hibernates - in my experience the DNS-323 front panel "power" LED (behind the logo) goes dark and the network and disk LEDs remain on - is the network LED also going out with this new switch?
I'm guessing here - but - here's my thought process ...
After x minutes of inactivity, the DNS-323 hibernates, and the various network hosts eventually flush it's ip/MAC pairing from their arp caches, the switch shuts down the link (or perhaps clears it's MAC table) - the next access attempt is most likely going to take the form of an arp request (which ever computer is accessing the device sends out a request along the lines of "who has ip address xyz"?) and the switch now has to re-enable the link, renegotiate the link speeds, etc. before it can send the arp request so by the time the DNS-323 responds, the host system has timed out and returned an error message.
If you're mapping the drives by hostname try mapping them by ip address and see if that makes a difference.
Try pinging the ip address and see if it gives an immediate response or times out intially and then responds.
Try manually adding an arp entry to see if that removes the delay - if it does one way to deal with it is to add a static arp entry, which is not something I'm in favour of - if you change the ip addresses at a later date and don't remember that you need to change the arp entry, you can have major grief and head scratching.
If the switch is a "green switch" try disabling the feature. If it's not try adding a static MAC to the table and/or try manually configuring the speed/duplex settings to reduce any autonegotiation delays.
Oh - like I said I was just guessing - so feel free to toss any or all of my suggestions out.
Offline
Dear Fordem,
thank you for your time helping me out. Pinging gave good responses and other checks revealed that I had been a real dope. I forgot that in the distant past I had given my printer a fixed ip address which overlapped the DHCP range. This clashed with the DNS323 giving the observed problem! All fixed now and all is well.
Thanks again
Mark
Offline
Glad to hear that you got it working.
Offline