Print

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

[Alexx]

Router settings doesn't matter. I did a master reset yesterday without changing ANY settings, not even the encryption, and guess what: It doesn't work (surprise, surprise!)

So in other words it's not triggered by settings in the router.

Also, the problem is computer independent. Let's say both my computers are off and I reboot the router. If I now turn on any of the computers after just a few minutes, i will be able to print. However, if I instead wait several hours and then turn them on, it will NOT work because the problem is now back.

So in other words the problem has nothing to do with the computer since it happens without a computer being present. The router rebooting is the ONLY factor here, so it can't be your computer settings either.

This is why (and I've said this for the last 8 pages) it has to be Firmware related. And again i stress the fact that it worked perfectly in 1.2x with the exact same setup.

[EddieZ]

Eddie - please post your router settings, page by page.  Once you do that, people can review their settings against yours and see if there are any differences.  It would also be very helpful if you detailed how your network is configured: what security suites you have on your systems, the anti-virus you are running, public/private settings, etc.  Again, people can compare their configurations to a known working one.

Ik keep repeating myself...The router settings are not the crucial thing here. It seems that you really do not understand my point here It is not a question of: My settings work and yours don't so you need to copy my settings.

The thought is that with either the firmware (which has really not changed a lot compared to 1.2x apart from the new Ubicom core/SDK) OR (perhaps more likely) the SDK/core update that was included in the 1.3x firmware responds badly (= reboots, Shareport malfunction etc) with certain (combinations?) of settings OR network topologies. Dlink cannot reproduce the issues shared on the forum. So sharing this info with them might speed up the process of finding the culprit.

You notice there's a lot "OR" 's present. That's because I:
1. don't have a generic solution
2. Am only trying to get more info out of the people who have issues and only complain since Dlink cannot reproduce the issues in lab environment. And if it is not broken, how do you know what to fix?

But I wil give up my attemps and leave the threads about all the problems to the ones who seem to enjoy complaining instead of solving.

Good luck with your malfunctioning devices. MINE WORKS PROPERLY! 

[kegobeer]

Router settings doesn't matter. I did a master reset yesterday without changing ANY settings, not even the encryption, and guess what: It doesn't work (surprise, surprise!)

So in other words it's not triggered by settings in the router.

Also, the problem is computer independent. Let's say both my computers are off and I reboot the router. If I now turn on any of the computers after just a few minutes, i will be able to print. However, if I instead wait several hours and then turn them on, it will NOT work because the problem is now back.

So in other words the problem has nothing to do with the computer since it happens without a computer being present. The router rebooting is the ONLY factor here, so it can't be your computer settings either.

This is why (and I've said this for the last 8 pages) it has to be Firmware related. And again i stress the fact that it worked perfectly in 1.2x with the exact same setup.

You just made my point - if Eddie shares how his network is configured (computers, wired/wireless, security suites/anti-virus/anti-trojan, operating systems, tweaks done to said systems, etc), people with problems can compare that known working configuration to their own.  If enough people report back with similarities and differences, the D-Link technicians might be able to reproduce the problem in the lab.

I've done a lot of troubleshooting during my career, and one of the best ways to discover the cause of a problem is to compare working systems to non-working systems.  Is it time consuming to detail how something is configured, and then go line-by-line to see what is the same and what is different?  Yes.  Can it help isolate a problem?  Yes.

To Eddie: it's not about copying settings.  It's about sharing information so people can compare configurations.  People can't isolate problems in their systems if they don't have a working system to look at.  If you want to help, share your configuration so people can start looking and seeing what's different.

[EddieZ]

That's Dlinks job. They are the only ones that know how the firmware on the DIR interacts (or is supposed to interact) with settings. The problems cannot be solved by chasing settings. It's the effect they have on the firmware that cause the issues.

AFAIK, there a a few issues that need to be separated. Possibly they will merge together i a later stage, I don't know.

Looking at the forum repsonse, revision A3 and A4 are mostly hit by reboot/disconnects. I do not an A3/4. Issues that are with A2 are seldomly seen and I really doubt if they are related to A3/4 issues (except 1 Shareport issue, see below)
Also, I think reboots and disconnects are something different then 'deauthorization'. The Shareport disconnecting issue has to do with deauthotrization of wireless clients connected. But with the other issues on the A3/4 (reboots, freezing) Shareport is also affected. Different cause, same effect.

So my configuration as an example does not have an impact. At least, that's my vision on the issues.

[kegobeer]

That's Dlinks job.

What is D-Link's job?

They are the only ones that know how the firmware on the DIR interacts (or is supposed to interact) with settings. The problems cannot be solved by chasing settings. It's the effect they have on the firmware that cause the issues.

I'm not talking about solving the problem.  In order to find a possible cause, it's necessary to troubleshoot and compare a non-working system to a working system.  Fixing the problem is up to the software engineers.  However, since the engineers can't duplicate the problem, they can't fix the problem.  So, comparing a working system to a non-working system.....

AFAIK, there a a few issues that need to be separated. Possibly they will merge together i a later stage, I don't know.

What issues are you talking about?

Looking at the forum repsonse, revision A3 and A4 are mostly hit by reboot/disconnects. I do not an A3/4. Issues that are with A2 are seldomly seen and I really doubt if they are related to A3/4 issues (except 1 Shareport issue, see below)

I own an A2, and I won't upgrade the firmware based on these problems.  Just because the A2 community isn't reporting an issue doesn't mean that the A2 is immune.  If I upgrade and suddenly Shareport stops working for me, my cheese will be out in the wind.  But, if someone with a working A2 setup posted details on computer configurations.....

Also, I think reboots and disconnects are something different then 'deauthorization'. The Shareport disconnecting issue has to do with deauthotrization of wireless clients connected. But with the other issues on the A3/4 (reboots, freezing) Shareport is also affected. Different cause, same effect.

So my configuration as an example does not have an impact. At least, that's my vision on the issues.

You aren't going to post your computer network configuration, because you don't think doing so will help anyone.  Since none of us are software engineers employed by D-Link, we really have no idea if this is restricted to a certain hardware revision.  I think sharing what works for you can help others identify what might be causing their problem.  You said in an earlier post that "This a discussion board for customers to get answers from other users and IT nerds."  A good discussion involves sharing working configurations, so that users and "IT nerds" can identify a possible cause of a problem.

I sincerely hope you reconsider your decision and post your configuration(s).

[EddieZ]

kegobear, you got to find the answers to your questions yourself. I'm not gonna explain every sentence, sorry. A hint (or 2): look on the board for the definition of "issues" and read your own remark in the same post to answer your 1st question... And please read my sentences carefully. Words like "mostly" have a specific meaning....

My advice: stick to 1.21 until there is some relieve to this. If it works OK, don't fix it.
My config will do nicely in my particular situation, just comparing configs isn't gonna cut it: One needs to see how they interact with the firmware and router's core.

[StepheninIsrael]

It also doesn't work on the DIR-825 with all the firmware/software upgrades.

Clearly they changed something in one of the 2 upgrades that messed it up.

I still have not received any response or acknowledgment from Dlink tech support.

[EddieZ]

My best bet is that the issue is in the updated Ubicom SDK (which also causes the non-reversibility of firmwares).

[Henk55]

What I encounter in the past;
I have a (a good brand) Music Wifi Controller wich re-booted about once or twice a week.

So I'll post then a message "maybe a watch-dog" problem.

After some month's later it finally states a watch-dog problem,
on some devices causes about the non-zero tolerance of the hardware!

What I'm trying to say is there is Watch-dog timer in the Dlink 655?

At the moment I'll trusted on my A3 1.22b5 FW, and a second one A4 with 1.21 stays in the box as reserve. 

[kegobeer]

kegobear, you got to find the answers to your questions yourself. I'm not gonna explain every sentence, sorry. A hint (or 2): look on the board for the definition of "issues" and read your own remark in the same post to answer your 1st question... And please read my sentences carefully. Words like "mostly" have a specific meaning....

My advice: stick to 1.21 until there is some relieve to this. If it works OK, don't fix it.
My config will do nicely in my particular situation, just comparing configs isn't gonna cut it: One needs to see how they interact with the firmware and router's core.

Wow.  You just don't get it, Eddie.  Sharing information helps people solve problems.  Why you choose to be selfish and keep that data to yourself is beyond me.  Usually someone who takes on the role of helper/expert is eager to share information.  Perhaps your system doesn't work quite as well as you claim.

[ZT3D]

I've been reading through this thread for a couple of weeks now and can also confirm this very problem with my D-Link DIR-655 (A4) router using the 1.31NA (and previously the 1.30NA) firmware along with the SharePort 1.10 PC software. Shortly after the router is reset, my computers are able to connect and print to the Samsung ML-1740 laser printer that's hooked up to the router's USB port. After some hours have passed, however, none of my computers are able to connect to the device unless I reset the router either by cycling the power to it or resetting the device through its tools >> system menu.

I'm also going to make it very clear that although this is my first post here, post counts mean nothing to me and shouldn't be a big deal to anyone. There have been multiple users who honestly believe that this problem appears to be firmware-related and still you have people like EddieZ who come on here and report that they are running problem-free and how their "technical background" makes them more qualified to speak on the matter. On the other hand, you have people like Alexx who intelligently state their points and back them up with evidence that has not been refuted by anyone here. If D-Link wants more information from us in an attempt to solve this problem, that's what this thread is here for. I'm not going to stand idly by in the face of useless elitist criticism, however, and those who prefer to brag rather than help should keep that in mind.

[Alexx]

ZT3D, Thanks Let's hope D-Link will release a fix soon. I really appreciate that so many people have registered just to post that they have the same problem because it really sets the scale of the problem in perspective. Obviously, a LOT of customers are affected by this.

[EddieZ]

Wow.  You just don't get it, Eddie.  Sharing information helps people solve problems.  Why you choose to be selfish and keep that data to yourself is beyond me.  Usually someone who takes on the role of helper/expert is eager to share information.  Perhaps your system doesn't work quite as well as you claim.

Humbug. It works fine. Any reason to suspect me of misrepresenting my own situation?
Once again: it's not about my settings. There is no magic in them: My device works properly. It's the correlation of YOUR settings with YOUR revision and the firmware/SDK changes (which WE ALL can't see) that could reveal the causes of the issues that YOU have.

If you stil don't get it I would suggest you take some reading classes or buy a brain...

[Demonized]

I've been reading through this thread for a couple of weeks now and can also confirm this very problem with my D-Link DIR-655 (A4) router using the 1.31NA (and previously the 1.30NA) firmware along with the SharePort 1.10 PC software. Shortly after the router is reset, my computers are able to connect and print to the Samsung ML-1740 laser printer that's hooked up to the router's USB port. After some hours have passed, however, none of my computers are able to connect to the device unless I reset the router either by cycling the power to it or resetting the device through its tools >> system menu.

I'm also going to make it very clear that although this is my first post here, post counts mean nothing to me and shouldn't be a big deal to anyone. There have been multiple users who honestly believe that this problem appears to be firmware-related and still you have people like EddieZ who come on here and report that they are running problem-free and how their "technical background" makes them more qualified to speak on the matter. On the other hand, you have people like Alexx who intelligently state their points and back them up with evidence that has not been refuted by anyone here. If D-Link wants more information from us in an attempt to solve this problem, that's what this thread is here for. I'm not going to stand idly by in the face of useless elitist criticism, however, and those who prefer to brag rather than help should keep that in mind.

I doubt if even a few posters actaully know/have a clue about the working of firmware and internal structure of hardware. People like Alexx sound intelligent perhaps, but I've been missing the so called "evidence". I do not get the feeling those people know even a tiny bit about the way firmware and stuff works. All I see is "It's the firmware", regardless of which issue.

[ZT3D]

I doubt if even a few posters actaully know/have a clue about the working of firmware and internal structure of hardware. People like Alexx sound intelligent perhaps, but I've been missing the so called "evidence".

Perhaps you need to read more carefully and take a close look at Alexx's post at the top of page 14. He outlined the steps he took after resetting the router back to the factory defaults and explained the time factor after resetting the unit as the primary difference between working and non-working scenarios.

I do not get the feeling those people know even a tiny bit about the way firmware and stuff works. All I see is "It's the firmware", regardless of which issue.

I am not concerned with any issue aside from this one which has been verified and confirmed by numerous users at this forum in multiple threads. The fact is that you don't have to be an "expert" to understand what the key variable is between past instances when things were working and now when things aren't working. That key variable is the firmware and none of the suggestions brought forth so far have managed to provide a solution, giving further credibility to the belief that nothing short of a firmware update can correct this problem. Although there is another variable in that newer SharePort software (PC v1.10) is required with v1.3x firmware, closing and reloading the SharePort software does not solve this problem when it arises.

It has been suggested that older hardware revisions of the DIR-655 may be less likely to experience this but that doesn't help the many users who presently own A3 or A4 hardware revisions and are stuck with 1.3x firmware which cannot be downgraded in an attempt to work around this common problem.