Print

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

[EddieZ]

My Advanced DNS was always off. Thus it is not related with this issue.

Glad someone also notices that DNS isn't related to the issues...I have it enabled and works perfectly.

[R3XNebular]

F*** sake, can you give a date when you guys will actually try working on this, Or I am going to buy a new router, cause this router has run me up the wall.

[EddieZ]

They never give out dates. Nor Dlink nor any other software/hardware manufacturer will do that. So either buy a new router or grow some patience. There's more important things in life then a router that are supposed to drive you crazy 

[Clancy]

This is cross posted from the Shareport forum but this thread is where I first read up on this situation.

Emerald, I have a USB drive attached to my DIR-655 and it will mount right after I reboot my router. After that it is a matter of time before it unattaches and will not reattach until I reboot the router again. The fact that Sharepoint sees it means that you've done everything right. Something else is going bump in the night and no one seems to be able to pinpoint the problem. I've been feverishly working on the PC side of the issue to see what I can come up with but I'm running out of ideas. Initially, I had firmware version 1.21 and Shareport version 1.14 running. My hardware version is A3. The test I use is to run my drive imaging software, which can take up to 5 hours to complete, and under the aforementioned setup it ran for just over 4 hours before it lost connection. I then decided to upgrade the firmware to the latest version and use the accompanying Shareport software. I have yet to see the drive stay connected for longer than 1 hour before it disconnects. Rebooting the router has been the only way I have found to get it to reattach the drive. I have disabled the NIC and then re enabled it to refresh the network without rebooting the router and this has not worked. If I reboot my PC, when I start Shareport I now am presented with 2 identical hard drives neither of which will connect. Of course, there really is only one but I cannot figure out why it shows 2 and the only way to correct this is to reboot the router. D-link engineers cannot duplicate the problem but my guess is that they are running the test on a pristine setup without all of the myriad software that is added and removed by the common user, not to mention the **** that usually comes preinstalled. If the D-link engineers could concoct a monitoring program that would create a log that we could then ship to D-link (to somehow pinpoint what is happening) would be something I would volunteer for. But, I don't think they know what to look for so how can you write a monitoring program if you don't know what to monitor? I went so far as to install the Netmon software by Microsoft to see if I could get some idea what is happening when the drive detaches. What I found, and this could be speculation, is that I received a flurry of UDP requests from the router just before or during or after the drive detaches. Most of them were identification requests from the DNS. What I noticed is that although I correctly registered my primary and secondary names, it would say that something about it was incorrect. This may all be pie in the sky wishful thinking as I have no idea if  the router should query who is on the other end and it doesn't like the answer; would it disconnect my drive? Inquiring minds want to know.

[EddieZ]

Just remember: As long as there is a next version after 1.10, there's hope 
Wait and see...

[Leslie]

I had been fighting this for a while as well, and tried almost everything in this thread, and I have a few theories. From what I have seen, power management is the likely cause. I never tried older versions, so I am working on what I have seen so far and from what I have found with USB.

I tested on several hard drives and thumbsticks, as well as various cables. Some would register but not connect, some would not even register. Some would show, but not connect and shortly disappear. Finally, I tried the sd card reader. It worked every time.

I have seen this before, a device is not getting enough power, it will sometimes register in Windows and not allow it to run. Windows sometimes will even turn off that USB port since the device is not working or not being used. I then added an external power to the external drive and what do you know, it worked fine.


How many of you are using non-powered USB hubs, how many powered ones require power from the source even if powered? Try something very low powered first (not a thumbstick, they can use more than you think). I would be interested if D-Link changed the power management between the firmware versions and is now giving you all grief. Maybe they lowered the max output on the A4 to help compensate for the lack of heatsink.


I have an a4 by the way, and seems to be running fine for the moment after gigs of transfer, and switching between XP and Win7, wire and wireless. Maybe it's too early to tell, but this is much further than I could get before, and seems to be running fine. Maybe some of you could verify the results.

[stonehead]

I have the powered external hard disk and the powered usb hub.
But same problem.

[Leslie]

well it worked for a while, a reset of the router restarted it. I still think this is power related/power management. As soon as I left it alone, it loses connection. I transferred 20gigs no problem, once it sat for a bit, it stopped working.

[PeterJvM]

Interesting,

I live in Turkey and occasionally run into the same Shareport problem.
The electricity is not as stable as we have a lot of voltage-fluctuations and I noticed that when the light dimms for a brief period, thıs happens also, sometimes I even get de-authentication messages and retarts at that time. No wonder in my case the ac power supplied is the cause. I did run my comptersystem on a no-break powersupply for 2 weeks to test and everything ran without shareport problems and without any other trouble.
Since not everybody has the problem I think there might be a small chance that failing power supplies are the root of the problem.

[R3XNebular]

"Since not everybody has the problem I think there might be a small chance that failing power supplies are the root of the problem."

I highly doubt everyone here is having failing PSU's

[PeterJvM]

Agreed, but even though it's a small chance, it is a situation that I just tried to reproduce and guess what, it's easy to do. So it's relatively, easy to take in account or to test for D-Link.
Since the early (a1 - a2) series seem to be a lot less affected and there are small hardware-changes to the newer (a3 - a4) series, there may be a possibility that an unstable psu causes problems earlier at these units. Not using (usb)bus-powered devices would, as some people seem to have noticed, more or less relieve the problem.
In that case an properly over-dimensioned psu would be a solution.

"Since not everybody has the problem I think there might be a small chance that failing power supplies are the root of the problem."

I highly doubt everyone here is having failing PSU's

[Alexx]

That still doesn't explain why it worked in 1.2x.

And if it really is the PSU, why will a router reboot from the web interface magically fix a issue with the PSU? As far as I know the PSU is still sending power to the device when you reboot it.

If the cause really is power management, it is probably a firmware thing and not the hardware.

[EddieZ]

My best guess is that there's an incompatibility between the Silex virtual USB program/driver (we call it D-Link Shareport  ) and the Ubicom SDK/kernel (hardware).

If so, there is nothing you can do to fix it. It still leaves the issue open that there's a considerable difference in the way you individually are affected. But anyway, if this is the case we just need to wait for an update by Dlink. Don't know what's faster: getting the driver fixed by Silex or getting a new kernel update (also third party and I guess they may have changed them since the 1.3x issues  )

[Tad_M]

appereantly there is a beta firmware 1.32 that fixes the problem.

FILE:
http://forums.dlink.com/index.php?topic=5841.0

RELEASE NOTES:
http://www.dslreports.com/forum/r22496647-DIR655-Firmware-132NA-Beta-1-available

Let us know if this works for you

[Guyton]

Printer and hard drive work for me off usb hub with this beta fw!!!!!!    THANKS D LINK

appereantly there is a beta firmware 1.32 that fixes the problem.

FILE:
http://forums.dlink.com/index.php?topic=5841.0

RELEASE NOTES:
http://www.dslreports.com/forum/r22496647-DIR655-Firmware-132NA-Beta-1-available

Let us know if this works for you