Print

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

[Alexx]

We're all willing, but you're not telling us what to do. We have tried everything you have said so far but nothing has worked. If your IT skills are as good as you say, why don't make a list of things for us to try?

But quite frankly, I do not see how the network config, standby mode or AV/firewall on my computer could be the root of the problem when a reboot of my computer doesn't fix the issue, but a reboot of DIR-655 does. Can you explain that one please?

[valleyboy221]

I saw some advice that said to try using shareport on different computers. As I have stated I have not been able to use Shareport on 3 different computers, different hardware and different operating systems. I did make Shareport work on all 3 computers for a short period of time only by powering down the router, not rebooting from the console. To get Shareport to work, I am not trying to do anything complicated - just use a simple USB drive (no complicated drivers here). I know there is an issue with Antivirus/Firewall software, I have seen it on my computers; so disabling the AV software eliminates that issue.
In my previous posts I have deliberately not blamed the router for the shareport issues, but I do find it difficult to imagine that all my computers are wrongly configured or in standby, etc. But I do think, what is the common factor in my system??
Also I did reread the seven pages of posts and it appears from the people who specified Hardware Version; A1/A2 works, systems with A3/A4 do not. I have A3

[EddieZ]

It's inportant to see the difference in all issues reported. By revision, for example. Generalizing the issue will make the chances slimmer to resolve certain causes.
So Valleyboy221, what I'm trying to do is to have people broaden their mindset about the cause of their 'malfunction' in order to filter out the external problems. Just trying to get some actual methodology
into solving this problem.

@Alexx: Come and bring in your PC  and I''l fix it for you. Or do you think my middle name is Uri Geller?

[stonehead]

It's inportant to see the difference in all issues reported. By revision, for example. Generalizing the issue will make the chances slimmer to resolve certain causes.
So Valleyboy221, what I'm trying to do is to have people broaden their mindset about the cause of their 'malfunction' in order to filter out the external problems. Just trying to get some actual methodology
into solving this problem.

@Alexx: Come and bring in your PC  and I''l fix it for you. Or do you think my middle name is Uri Geller?

Who are you?  Are you a D-link employee? Did you develop the firmware?
What else info do you need to actually help people to fix this problem?

I'm sorry but I don't get any helpful advice from you so far.
Can you please give us the step-by-step guideline to fix this problem
if you're such expert?

I'm just wondering if some D-link engineers watch this forum so that they plan to seriously
take a look at this problem. Otherwise, seems like just waste of time...

[Alexx]

@Alexx: Come and bring in your PC  and I''l fix it for you. Or do you think my middle name is Uri Geller?

Yeah that pretty much sums up my point that you're just blindfoldingly blaming the PC whithout even having a clue what is wrong. If you really can fix this issue then simply tell me what to do.

I think it is also obvious that you have absolutely no idea how customer support works with network equipment.
If something is wrong with the product: Release a fix
If an external factor is preventing the product from working: Release a step-by-step guide.
What not to do: Blame an external factor without telling people how to fix it <- This is where you're at right now.

As a consumer I should not have to trial and error and having to look through all kinds of settings on my own. That is NOT customer support. This is affecting many many customers so it is clearly not an isolated issue, nor do we all have defect products. Hopefully we can get a real response from somebody who knows their stuff (like D-Link).

[R3XNebular]

Can someone with an actual clue help us? A dev? actually respond?
A dev may know the source of this problem cause they developed it!

[valleyboy221]

I did speak to dlink tech support by phone. The first agent suggested that I reinstall shareport and power down my router. When this seemed to make no difference I was transferred to a product specialist, who when I explained the problem was honest enough to suggest that he did not know the answer to the problem. I should add that I had contacted dlink by email first - they were unable to provide a solution either. It doesn't help to solve our problem, but it does make you wonder whether the solution is in our hands.

[jeffmik]

I'm following this thread, hoping for some sort of suggestions that works - or even someone from Dlink asking followup questions.

[R3XNebular]

shows that it isn't an 100 in 100,000 error, seems alot of people are experiencing judging by how many new people are signing up just to post here

[Lycan]

We are attempting to collect as much information about the failure as possible. I understand how frustrating it must be to not have this work properly, but we are unable to replicate the issue internally.

Please be pateint and we will get it sorted out for you.

[mclearn]

Lycan - would it help to send you our saved config files?

[Lycan]

No, we have no way of reading them, what I'm looking for is common things among the computers that are having shareport problems.

[artus]

Same issue here -- XP and Vista machines exhibit the same "detect but no connection" behavior.  Rebooting  router sometime allows shreport to work for a while.

Jack.

[jmcging]

Just adding to the thread.

Sharepoint worked with 1.21 firmware and I upgraded to 1.31 firmware and uninstalled sharepoint, then reinstalled latest version and I'm in the same boat - my drive which used to be shared is now unavailable.

My router is dir-655 A4 and this is 32 bit Win XP SP3.

Have tried the uninstall and reg clean but no go.

[valleyboy221]

Lycan
I'm sure you've noticed that the systems affected seem to be using routers with A3/A4 hardware. Is this what you are using in your tests?