D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Lycan on July 27, 2009, 08:41:48 AM
-
Continued from here.
http://forums.dlink.com/index.php?topic=5287.0
-
Final 1.32 has not solved the printer connection problem. Still requiring a router restart in order to prints from any of my 4 machines.
Any one having any luck?
Dir-655
HW Ver A4
FW Ver 1.32
-
Hey. I posted about this before, the latest firmware 1.32, it still has the shareport problem. Hopefully they can fix it soon.
In order for the shareport to work, you have to reset the router but changing the sharport settings to the WCN configuration settings. Once it restarts, then switch is back to shareport mode. After that, then that is when the shareport works (ONLY FOR A SHORT PERIOD OF TIME). It requires constant reboots in order to use shareport which i belive is not right. If anyone has the firmware 1.21 and is thinking of upgrading the firmware, DO NOT unless you dont need your shareport.
Just wait until the tech of dlink fixes the issues, let other people test out the firmware and keep reading the forums to see if the latest firmware update is a lot more stable.
The 1.32 firmware, shareport doesnt work and my DNS is disabled. If I enable it, my router will last about 2 to 3 days until it locks up, which requires me to unplug my router and then plug it in. It would be nice to keep the DNS enabled WITHOUT locking up. But if you disable the DNS, the router lasts for about 6 to 7 days until it slows down so much that it requires a reboot.
The 1.32 is a LOT more stable than the 1.31 so if anyone has the firmware 1.31, i suggest a firmware update.
hopefully this information helps all. ^_^
-
Not fixed in 1.32 Build 3 for me either.
-
Hi,
I had a similar problem with all of the latest beta f/w releases up to build 3 of 1.32NA. The problem would be that I could see a USB device, but when I tried to connect it would immediately pop up a dialogue box indicating that the connection failed. I recall that somebody had mentioned installing the Silex app, so I downloaded and installed the Silex Virtual Link v3.2.3 with SXUPTP Driver 3.3.8.0). As soon as I had installed this, the Silex client was able to immediately detect and connect to my external USB HD, and after disconnecting, I was able to use the Shareport client app also without any problem. I haven't had any problems since over the last 3 days since installing.
The download form the Silex website was sx-virtual_link_win_323.zip from here:
http://www.silexamerica.com/support/downloads/software/svl/win/sx-virtual_link_win_323.zip
By the way, my Dlink router is the A4 h/w type.
Hope this helps.
W.
-
Thanks your link i'm able to connect my silvershield powermanager from the router
-
Hey worm,
So i downloaded the link you put out, is that meant for PC? and is it like a 3rd party?
I installed it and its pretty much the exact same thing as the shareport program that dlink offers, and I am able to connect to my USB port (though i restarted my router). Im going to be waiting a few more days and see if I can still connect by using that program you gave out, the SX virtural link.
awesome :) Thanks for the info
-
Wow! Great! :)
Thank you, Worm.
I'll try it too.
Thanks again.
-
Hey worm,
So i downloaded the link you put out, is that meant for PC? and is it like a 3rd party?
It's the original program/technology which is used by Dlink (license/rebranded)
-
Deamonized,
Sweet, thank you for the information. So far i still can connect, day 2? keep you guys posted.
thanks again :)
-
downloaded and installed SX Virtual Link with SXUPTP version 3.3.8.0 but problem still exists. I have DIR 655 v A3G and using Windows 7.
-
Hey guys,
So to report about that software, i agree with teribol... Shareport still has problems. even with the SX virtual link.
-
Yep,
Looks like today it finally gave up the ghost again. I was actually excited to have Shareport working without messing up. At least now after the Silex install, I don't get the immediate "connection failed" message. I would love to know what is going on here though. I bought the router so I wouldn't have to get a separate print server.
Sigh.
W.
-
Yep,
Looks like today it finally gave up the ghost again. I was actually excited to have Shareport working without messing up. At least now after the Silex install, I don't get the immediate "connection failed" message. I would love to know what is going on here though. I bought the router so I wouldn't have to get a separate print server.
Sigh.
W.
Shareport is a nice feature, but cannot beat dedicated equipment (like a printserver). The problem seems to be caused by Windows. Some drivers(also others beside Shareport) just don't seem to work OK in certain setups or state (resume, hibernate etc). Or was it Windows that has flakey support for this? ;)
-
hey..i got a new development...my first post about sx virtual link not working...that was for Windows 7...i used Windows XP and its working. I connected and tried copying large files..5 350 MB downloaded video files..no problem.
-
It runs fine with 7 x64... Are you on x86? remember 7 is RC (beta)
-
I upgraded silex to 3.2.3 and so far 3 days in with working shareport. Keeping my fingers crossed!
This is with A3 and windows 7 x64
-
there must be a difference between the 64bit and the 32bit installers that came with the SX Virtual Link v 3.2.3 download. I used the 32bit installer because my W7 is 32bit. I hope that Silex get wind of this and post an updated 32bit installer.
I think that the problem is quite clear now. There is no problem with the firmware update (1.32NA). It is the virtual link that has a problem (specially the DLink version 1.10 of the silex program). The only difference i noticed between the 1.21 firmware-1.14 client pair and the new 1.32Na-SX 3.2.3 pair is how fast the connection is. The former is faster but the latter has nicer interface.
-
Well, scratch that. No sooner had I posted than it stopped working. Figures doesnt it... lol
Same deal as before.
-
I don't understand why these developers don't take a look at firmware-1.21 / 1.14 client pair and the new 1.32NA / Client 1.10 then make a comparison to see what the major changes were made, then revert it. the former worked just fine as far as the connection issue. I"m by no means a programmer or developer but I would imagine that would be a good place to start.
The selling point for me on this router was the shareport feature, it would be a shame and a disappointment if Dlink can't resolve this issue.
Dir-655
HW Ver A4
FW Ver 1.32
-
This sucks, same issue with Shareport on my 655 with 1.32NA. >:( Maybe they should add a timed auto reboot option to the next firmware. ::)
-
I don't want my router to have to reboot daily just to get the shareport to work. I seem to get about two days out of either the dlink software or the other SX software. It's silly.
DIR-655
Hardware Version: A2
Firmware Version: 1.32NA
Windows Vista SP 2
Core2 Quad Chipset
there has got to be a fix out there.
-
I have the same issue, also. My 655 has the 1.32NA firmware. Restoring the factory defaults did nothing to help, nor did using the SX software instead of the shareport utility. I hope D-Link comes through with a fix for this quickly.
update: doing a hard reset (using the pinhole on the back of the router) seems to have fixed the problem, at least for the moment. i can now connect to my printer and the shareport utility doesn't lose the connection after a few seconds.
-
I tried installing the SX Virtual Link on Windows Vista and it works. I even used a USB hub and i can connect to all the devices connected to the hub at the same time. I had an HP multifunction printer and a Seagate 1Terabyte External disk attached to a USB hub. I was able to use the scanner function without having to attached the multifunction printer locally.
So now only thing im waiting for...an updated SX Virtual Link client for Windows 7 hu hu hu. :'(
-
I tried installing the SX Virtual Link on Windows Vista and it works. I even used a USB hub and i can connect to all the devices connected to the hub at the same time. I had an HP multifunction printer and a Seagate 1Terabyte External disk attached to a USB hub. I was able to use the scanner function without having to attached the multifunction printer locally.
So now only thing im waiting for...an updated SX Virtual Link client for Windows 7 hu hu hu. :'(
It works fine with Windows 7. ::)
-
Rebooting the router gets it to work for like two days and then it quits for some odd reason. I've tried Shareport and the SX software.
-
i spoke too soon. while the shareport utility works for my desktop that's connected to a LAN port, every time my wife tries to connect wirelessly causes the router to reboot.
-
2 hours ago I installed SX virtual link, and have been using it instead of shareport utility from D-link,
and doing the extensive tests with one printer and one external HD from 2 XP machines,
so far so good. No more hang at 'available' status. And more than 2GB data transfer from HD
thru wireless without any problem. Everything works perfectly. I'm very happy with it.
I'll keep testing because someone here experienced it stopped working after a couple of days.
By the way, the firmware is 1.31.
(I haven't upgraded to 1.32 because many people reported secureport problem in 1.32).
-
2 hours ago I installed SX virtual link, and have been using it instead of shareport utility from D-link,
and doing the extensive tests with one printer and one external HD from 2 XP machines,
so far so good. No more hang at 'available' status. And more than 2GB data transfer from HD
thru wireless without any problem. Everything works perfectly. I'm very happy with it.
I'll keep testing because someone here experienced it stopped working after a couple of days.
By the way, the firmware is 1.31.
(I haven't upgraded to 1.32 because many people reported secureport problem in 1.32).
wait until the 3rd day... the shareport wont work unless you reboot the router.
if it is still working on the 3rd day, let me know :)
-
wait until the 3rd day... the shareport wont work unless you reboot the router.
if it is still working on the 3rd day, let me know :)
I wished your guess was wrong, but...
Like other reports here,
after 1.5 days, it doesn't work anymore.
It disconnects after few seconds.
-
I wished your guess was wrong, but...
Like other reports here,
after 1.5 days, it doesn't work anymore.
It disconnects after few seconds.
i wish i was wrong too.. but yeah thats what happens to me as well... and i dont think you should expect a fix anytime soon... i mean... its dlink. lol
-
A question: What does everybody mean with "after x day"? Is this continuous on or was the PC/client turned off in between? When Windows OS's are kept in standby or hibernate a lot of devices seem to have issues (not only Shareport). So it would be a good thing to mention what the PC status was during that time...
-
A question: What does everybody mean with "after x day"? Is this continuous on or was the PC/client turned off in between? When Windows OS's are kept in standby or hibernate a lot of devices seem to have issues (not only Shareport). So it would be a good thing to mention what the PC status was during that time...
well i think i get what you mean but...
when people say number of "x" days... its like ooh my shareport works from day one (in which you reboot your router) until like day 3.... after day 3, i cannot log into the shareport anymore... i have to restart the router again in order for me to access shareport. And from the standby or hibernate, it still lets me log into the shareport within the number of days. but after liek the 3rd day, i cannot access the shareport unless i reboot the router again.
let me know if that helps? if not i can try to explain it again. ^_^
-
A question: What does everybody mean with "after x day"? Is this continuous on or was the PC/client turned off in between? When Windows OS's are kept in standby or hibernate a lot of devices seem to have issues (not only Shareport). So it would be a good thing to mention what the PC status was during that time...
When it worked, no problem regardless of standby or hibernate.
It always worked perfectly.
Once it started to stop working, it repeatedly connects(about 25 secs) -->
disconnects --> available(trying to connect) --> connects(about 25 secs) --> ...
Rebooting computer doesn't fix the problem. Only rebooting a router fixes it for a while.
Since rebooting OS doesn't fix it, I guess it is not a Windows OS issue.
-
I have 2 machines Ive been using it with. Both run W7. One stays on while the other one goes in and out of standby when I need to take it with me. I check connectability approx every 2-4 hours and usually sometime on the second day I lose the ability to connect. Happens to both machines at the same time.
-
Non of my PCs ever go into hibernate or sleep mode. My main PC is turned off at night, and my other PC may or may not be on depending on whether it's downloading a torrent or not. In my case it doesn't seem to matter if a PC is on or not, shareport will just quit working after what seems like a random period. When it works all PCs can access the printer. When it decides to quit, non of the PC can access the printer. For me it's an all or nothing situation and only a router reboot will get it working again. >:(
-
Just wanted to contribute my experiences with this issue...
The issue: SharePort behaves correctly in all ways except when trying to connect (manually or automatically) to a device. It tries to connect, and after some time, the dialog box disappears and the device still says it's "available" (as opposed to being successfully "connected"). Otherwise, the status displayed of all USB devices work fine.
Routers experiencing this problem:
Mine:
DIR-655, HW A2, FW 1.31NA
USB device connected:
-Lexmark E321 monochrome laser printer
Computers connected:
-Desktop (wired connection) running Vista Enterprise 32bit SP2
-Laptop (wireless connection) running Vista Home Premium 32bit SP2
Friend's:
DIR-655, HW A4, FW 1.31NA (and also 1.32NA after updating)
USB devices connected:
-Samsung ML-2010 monochrome laser printer
-Memorex USB keyboard
-WD "Dual Option" external hard drive
Computers connected:
-Laptop (mine, same as above) connected with wireless
-Friend's laptop (wireless connection) running Vista Home Premium 32bit SP2
(SharePort version 1.1.0 R1 on all computers described)
In all these cases, I have found that the most reliable solution is power-cycling the router. It also seems that the reboot is not effective unless left off for long enough (15-30s). When having the issue, power cycling the USB device does not work reliably. Generally, the issue returns within a few hours, although sometimes it continues working for a longer period of time.
So, from my point of view, the issue has occurred on every router and ever computer I've tried. I've also been having this issue for months and this is the first time I've posted about it--so I wouldn't be surprised if there are a lot more people out there that are having similar experiences. It's unfortunate that D-Link hasn't been able to reproduce this problem--so keep testing different routers! It's a really frustrating issue and I'm looking forward to the day it's resolved.
-
How long has it been since my original thread? no fix? no comments on this issue... says allot about dlink
-
Your thread and a whole lot more seem to only get comments from people with the same problem but no fix! HELLO D-LINK IS THERE ANYBODY THERE? There are a lot of unhappy people here that wouldn't mind a little feed back from your end. :(
-
The Dir 655 is a Router not a NAS device. When have 3rd party software (shareport client) to run your externals what do you expect.
-
I expect it to work as bloody well advertised >:( D-Link is advertising Shareport as a selling feature for some of it's products. It was one of the reasons I upgraded from my 615 to a 655.
-
Agree with alphanumeric. I woudl hardly consider Shareport "3rd party software" when it's got D-Link's name plastered all over it. D-Link needs to get this problem fixed.
-
The Dir 655 is a Router not a NAS device. When have 3rd party software (shareport client) to run your externals what do you expect.
I believe that the shareport feaure of DIR-655 is a big selling point from the marketing viewpoint
in comparison with other routers. That's the exact reason why I bought it over the others.
Many people including me are really disappointed, but looking forward to the fix
because I, and maybe others too still "want to" believe that the D-link is working to fix it.
Your comment simply implies to me,
"D-link deceived you with the faulty feature, so you need to get over it!"
If it is really so,
I'll never spend my money for D-link's product in future, and furthermore
I will do my best to keep anyone from buying any product from D-link.
-
I don't want this thread forgotten!
-
Agree with alphanumeric. I woudl hardly consider Shareport "3rd party software" when it's got D-Link's name plastered all over it. D-Link needs to get this problem fixed.
Hmm... Did Dlink make the chipset...uh...NO..I would dare to say Shareport software was sub-contracted to another firm.
Lets face it Dlink and Linksys, Netgear are all name brands and if you notice offer alot of the same features. Why is that? Could it be because the have the same internal chipset? (Ubicom)
My Dir 655 A1/A2 was never advertised with shareport although the hardware was there and then you have Linksys coming out with a USB port advertised for HDD and printers..etc.. SO Dlink keeping up with Marketing does it also.
-
Hmm... Did Dlink make the chipset...uh...NO..I would dare to say Shareport software was sub-contracted to another firm.
Lets face it Dlink and Linksys, Netgear are all name brands and if you notice offer alot of the same features. Why is that? Could it be because the have the same internal chipset? (Ubicom)
My Dir 655 A1/A2 was never advertised with shareport although the hardware was there and then you have Linksys coming out with a USB port advertised for HDD and printers..etc.. SO Dlink keeping up with Marketing does it also.
Are you sure? I maybe just missing it completely, but I haven't seen another router based on the ubicom chipset running any type of shareport clone. I honestly wouldn't be suprised if dlink did in fact write shareport using the ubicom SDK.
Granted the trendnet 655 clone doesn't even have USB, so I am not sure there is anyway to tell.
-
Hmm... Did Dlink make the chipset...uh...NO..I would dare to say Shareport software was sub-contracted to another firm.
Lets face it Dlink and Linksys, Netgear are all name brands and if you notice offer alot of the same features. Why is that? Could it be because the have the same internal chipset? (Ubicom)
My Dir 655 A1/A2 was never advertised with shareport although the hardware was there and then you have Linksys coming out with a USB port advertised for HDD and printers..etc.. SO Dlink keeping up with Marketing does it also.
It doesn't matter who made the chip-set or who wrote the software, it has D-Links name and Logo on it. D-Link is ultimately responsible for any hardware or software it markets to the public. I don't care how many excuses you want to dream up for them, they are the ones that screwed it up and they are responsible for fixing it!
-
It doesn't matter who made the chip-set or who wrote the software, it has D-Links name and Logo on it. D-Link is ultimately responsible for any hardware or software it markets to the public. I don't care how many excuses you want to dream up for them, they are the ones that screwed it up and they are responsible for fixing it!
Dream up excuses? Just like this conversation Shareport is a waste as I bought a Router not a NAS device. Kick it to the curb!
-
Are you sure? I maybe just missing it completely, but I haven't seen another router based on the ubicom chipset running any type of shareport clone. I honestly wouldn't be suprised if dlink did in fact write shareport using the ubicom SDK.
Granted the trendnet 655 clone doesn't even have USB, so I am not sure there is anyway to tell.
Your right Linksys dose not have a ubicom chipset ..opps. :) http://www.ubicom.com/newsevents/pressarchive/press.php <--interesting reads
The point I was trying to make was it's all about marketing.
-
If there is someone in D-link, please reply.
I want to know the status of this issue.
Still D-link can't reproduce this problem which many people have ?
-
maybe they shouldn't outsource features. like the new router that has a picture frame, they outsources that software. so how much do you want to bet that won't work right.
bottom line is that this experience with d-link is affecting my consumer choices. I am looking to buy a NAS, and I want the d-link one, but this experience is making me not want to buy d-link. I need to buy network gigabit cards for all my computers - well guess what, after this experience, my dollars are going elsewhere.
If this is how much Dlink values their customers, then they don't deserve my money.
-
maybe they shouldn't outsource features. like the new router that has a picture frame, they outsources that software. so how much do you want to bet that won't work right.
Welcome to Consumer IT. 99% of all firmware and software development is outsourced. And 90% of all products are mass produced by 3 or 4 major manufacturers for all interested companies and just labelled (or boxed) with a brand and a slightly customized firmware.
-
I agree with the frustration expressed here. You buy something that is supposed to work a certain way and your expectation should not be any less than it working the way it was advertised. I am really surprised at D-Link's inability/ unwillingness to fis an issue on such a popular router. They obviously do not bother reding these forums. Haven't looked, but is there a way to contact them directly?
-
d-link is just showing my how little they care for my money. that's fine. i can go spend my money with linksys or netgear. and im the type a person who likes to get all the same brand for my networking equipment. if they don't want my money.
-
d-link is just showing my how little they care for my money. that's fine. i can go spend my money with linksys or netgear. and im the type a person who likes to get all the same brand for my networking equipment. if they don't want my money.
I also use Asus and Linksys products. The respons there isn't any different....
-
I also use Asus and Linksys products. The respons there isn't any different....
I know, I know...
EddieZ,
Demonized,
KevTech
Mysterious guys...
-
I also use Asus and Linksys products. The respons there isn't any different....
LOL, try getting some help from Creative.
-
I know, I know...
EddieZ,
Demonized,
KevTech
Mysterious guys...
The one thing those three share is that they know IT and understand that the world was not created in one day with the twist of a finger.
-
I hit up the DLink twitter account and they said they are "working on it". Enough people are having the same problem in similar environments, that I find it hard to believe they can't recreate the issue. Shareport is a great idea but a huge failure.
Maybe if they would develop their own features instead of out-sourcing them, they might work better or be easy to troubleshoot.
-
I hit up the DLink twitter account and they said they are "working on it". Enough people are having the same problem in similar environments, that I find it hard to believe they can't recreate the issue. Shareport is a great idea but a huge failure.
Maybe if they would develop their own features instead of out-sourcing them, they might work better or be easy to troubleshoot.
That's simply not how consumer IT works.
And believe it or not, all features on my DIR work flawlessly. Even Shareport and in various network and client configurations.
-
The one thing those three share is that they know IT and understand that the world was not created in one day with the twist of a finger.
So,
you want to say to me that those who report the problem here do not know IT, don't you?
Maybe you're a smart IT guy, as you declared... But....
unfortunately I don't get any good hint to solve the problem
from whole bunch of your, per se, "the IT smart guy"'s replies about this issue.
... frankly speaking...
although I thank you for your tries to help us,
mostly what I see is a narcissistic (or royal to D-link) person keep saying that
"my router has no problem, I'm smarter than you,
so don't complain to D-link, you stupid people"
(1) This problem was first posted on 5/1, and 4 months passed since then.
(2) Many people have the same problem (you want to deny it, I know, so don't start again)
(3) The D-link guy(Lycan) keeps telling "D-link cannot reproduce the problem"
, which I hardly believe.
(4) Some small number of people try to make the issue obscure or to divert the problem from D-link.
Those are the facts which I see here, this forum.
-
You see a version of 'facts' on the forum.
It's a fact that the majority of users is unable to configure a network when the environment requires a bit more than "working out of the box". I might be putting it bluntly, but there's no qualification attached to this simply because you don't have to be an engineer to drive a car.
Asking for a solution because I'm an IT pro... even when a lot of info is given, (network) environment factors cannot be taken into account of seen. It's like consulting a doctor by phone; it's quite limited.
Do not refrain from posting your questions and issues. But it's too one sided to blame the manufacturer solely because of someone's own limited capabilities . My statement that I have a good working router is not to show off. It only shows that there is no major or basic issue with the device/firmware, not denying that there's about 50 people where there seems to be either a glitch in the router or their network/client setup.
-
There's one thing that everyone seems to be misunderstanding. D-Link is in NO WAY trying to deny the validity of your issues. We are simply struggling to replicate the failure within our own labs.
Lab environments are a funny thing. For instance we recently did an RMA/Replacement for 15 DGL-4500 users that claim that their routers would lock up in 3-4 days and could reproduce the error at will given enough time.
When the units came to our labs they DID NOT fail. They had to be sent to our HQ office for further analsys.
We simply saying that we're struggling to locate the source of the issue as we don't see the failures, not that we're not going to do anyting about it.
-
OK fine finally some news. The reason people get pissed is it's like pulling teeth just to get any little bit of info out of D-Link. From what I can see a lot of people here really feel like their concerns are being ignored "by D-Link". I see a lot of the same questions asked over and over with no real answer other than "mine does that too". On top of that you get the lammer "Mine Works", so stop you "whining" posts that just fan the flames. (not directed at EddieZ =) ). Lycan, you couldn't maybe enlighten us as why D-Link started this forum?
-
I would imagine this forum was started like many other forums out there. For Users to help out other Users. Thats why its not labeled as a support forum.
-
spot on
-
Hi,
Off topic a little, but its nice to see that Dlink hasn't wiped our threads off the planet as netgear did a few eyars back when the WGT624 routers were having issues.... All they said was, we updated our forum site software, and had to start over....I am paraphrasing here....
Kudos to DLink for letting us air these problems in the first place....
SD1
-
Just to keep this thing going...
I have exactly the same problem as other people have been reporting. The shareport 1.10 client can connect to the printer and successfully complete print jobs right after the router has been rebooted. After some amount of time, no computer in my network can successfully print. It says the printer is available, and keeps trying to connect, but never completes the print job, and no printing occurs. If I leave the print job in the queue, and reboot the router, the printing resumes automatically. I have also installed the SX Virtual Link software with no change in behavior at all.
I am a software developer, and I know fixes take time. But it just seems amazing to me that they can't recreate this problem. It's not like I have some exotic network setup. The two computers where I have seen the problem are both on a wired gigabit connection. One is Vista, the other Win 7. Pretty much everything is default everywhere, the only thing I have done to the router is put in my ISP info. I am absolutely convinced it has nothing to do with the computers. I haven't bothered to update my wireless computers to the newest shareport client because I know it's futile.
This failure occurred immediately after upgrading to 1.32 firmware from 1.21. Under 1.21, it worked fine, except sometimes the client would lose connectivity after a computer resumed from sleep. This was easily fixed by stopping and restarting the shareport client. Now, there's no easy fix, and rebooting the router on a daily basis is clearly unacceptable.
Count me among the disappointed...
-
It's a fact that the majority of users is unable to configure a network when the environment requires a bit more than "working out of the box". I might be putting it bluntly, but there's no qualification attached to this simply because you don't have to be an engineer to drive a car.
Asking for a solution because I'm an IT pro... even when a lot of info is given, (network) environment factors cannot be taken into account of seen. It's like consulting a doctor by phone; it's quite limited.
Why don't you show your configuration (or environment) in which your router works flawlessly?
(1) Windows OS
-. Which setting do I need to adjust in OS (XP or Vista)?
-. Network card? Since I have several computers - thus, different network cards -
which have all the same problem, I don't expect any special tune for the cards.
But if you have any, please elaborate it.
-. Firewall doesn't matter, I think. (the problem still happens even though it was turned off)
but, if you still want to recommend something, please elaborate it.
(2) DIR-655
-. please share your setting.
Any special setting you did?
Setting USB network is relatively simple.
But if you have any, please share your setting info.
Please don't just say, "Oh, it's hard to explain, blah, blah, blah",
if you really think that the issue is not on the DIR-655 router/software
but on the lack of users' IT knowledge.
If you're not able to share or to give the info which can fix the problem,
please please never ever post like that.
I have already read too many posts
-- no help, but just irritate those who want a router working as it is advertised.
-
My Setup (which has had no issues):
Desktop Computer- Windows Vista 32, wired with 2 onboard NICs on a EVGA 780iFTW (Nvidia NICs) Gigabit NICs.
Network Printer wired 10/100
Desktop Computer - Wireless DWA-552 - Windows XP SP3 - NOT using the DLINK connection mamager
Laptop - Wireless DWA-652 - Windows XP SP3- also NOT using the DLINK Connection Manager.
Also, used to have 3rd desktop that was wireless, and sometimes have a 2nd wireless laptop that connects wirelessly.
Router DIR-655 (A2) : nothing special. No Virtual Servers, No Port Forwarding, No Schedules. I use the USB port to run a Laptop Cooler that sits under the router, so I don't use SharePort.
I have run every version of beta firmware that there has been and never had a problem. I am running the 1.32NA.
-
Router DIR-655 (A2) : nothing special. No Virtual Servers, No Port Forwarding, No Schedules. I use the USB port to run a Laptop Cooler that sits under the router, so I don't use SharePort.
You're in the wrong place.
This is the thread for the "shareport" problem.
And I have A4, which may be related with the problem.
--> No. I read old posts again.
Regardless of the hardware version, the problem happens.
-
You're in the wrong place.
This is the thread for the "shareport" problem.
And I have A4, which may be related with the problem.
You asked for configurations of routers that had no issues. I gave mine. As for being in the wrong place, threads don't usually stick to a set path, they tend to migrate off the initial topic and then find their way back.
-
You asked for configurations of routers that had no issues. I gave mine. As for being in the wrong place, threads don't usually stick to a set path, they tend to migrate off the initial topic and then find their way back.
You make me laugh...
anyway, thanks for your reply even though it doesn't help at all.
-
Heck, I could get on here and say my router is perfect if it wasn't for shareport. Yes, for me, everything is working but shareport. I generally love the router except for the broken 1.32NA firmware that destroyed shareport functionality.
-
Removed due to being useless drivel.
Nice of you to drop by with a -presumably- freshly made alias. You can keep shouting but if the firmware is a bust, please explain why my setup has no issues. I'm really curious if you can get passed "it's a coincidence".
Concerning my setup, I can show you the environment. But if you know a little bit of Windows you know that config issues are burried way down in the registry. Especially when the network config is concerned.
But here you go:
NIC: Marvell Yukon 88E8056 PCI-E onboard, driver version 11.10.10.3 on W7 (64bit and 32bit) and Vista (32bit) (10 series driver)
Firewall: Windows own firewall (all Windows)
AV: NOD32 4.0.437 (on all 64-bit and 32-bit Windows)
Shareport
7-port powered USB hub with:
- Printers: 1 Samsung Laser and 1 HP Deskjet
- USB HDD Freecom 400 GB
- Various 4, 8 and 16 GB thumbdrives
Wireless:
2 PC's with Linksys NIC, 1 Acer laptop with Realtek NIC, 1 KiSS wireless mediaplayer, 1 PocketPC 2003, 1 Samsung Smartphone, 1 wirless photoframe
Router config: no guestzone, static IP's, all standard options.
*** Modified by Fatman because he didn't see a point to leaving a quote written by a banned member.
-
Interesting isn't it? In my case Shareport worked with the previous firmware. I flash to the newer firmware, use all the same settings I used before (manually entered after the flash) and Shareport doesn't work any more. I even reset to defaults, only entering passwords for wireless etc and it still doesn't work. No settings were changed on any of my PCs. You don't have to be an engineer to know when your car has a flat tire and you don't have to be an IT pro to know the new firmware is f***ed up. >:(
-
Interesting isn't it? In my case Shareport worked with the previous firmware. I flash to the newer firmware, use all the same settings I used before (manually entered after the flash) and Shareport doesn't work any more. I even reset to defaults, only entering passwords for wireless etc and it still doesn't work. No settings were changed on any of my PCs. You don't have to be an engineer to know when your car has a flat tire and you don't have to be an IT pro to know the new firmware is ****ed up. >:(
No your firmware is ****ed up. Mine works fine. Is it so hard to imagine that your problem is not automatically a generic problem? ???
The reason I am reacting (and almost sounding like a fanboy here unfortunately) is that an individual problem or a problem that seems to strike a small group of users is being enlarged as being a generic issue. That's not "problem solving" (what the board is about) but accomodating a platform for useless ranting. Perhaps out of desperation, who knows. But the added value of screaming and ranting to this forum community is really sub-zero. :(
For your reference: i***roup of white caucasians of let's say 100 are villains and criminals, does that make the rest of the caucasians villains and criminals?
-
I'm new here, but this bickering is silly.
The truth is somewhere between EddieZ's "The firmware works for me" fanboyisms, and the ranters cussing about how evil d-link is.
I have no idea how widespread the problem is. Forums like this are always overrepresentive of problems, because people come here to report problems! But, I do believe something is wrong here. At the very least it is fragile, and simply flashing to the newest firmware causes a functionality that had been working for years to stop working.
I see that EddieZ uses static IP addresses. I have DHCP enabled. Maybe that's something.
-
i just find it hard to believe that with SO MANY people having the SAME problem that NO ONE at D-Link can recreate it. With some many people having the same problem with different hardware versions, different OS, different processors, etc for it to not be a general issue.
-
NIC: Marvell Yukon 88E8056 PCI-E onboard, driver version 11.10.10.3 on W7 (64bit and 32bit) and Vista (32bit) (10 series driver)
Firewall: Windows own firewall (all Windows)
AV: NOD32 4.0.437 (on all 64-bit and 32-bit Windows)
Shareport
7-port powered USB hub with:
- Printers: 1 Samsung Laser and 1 HP Deskjet
- USB HDD Freecom 400 GB
- Various 4, 8 and 16 GB thumbdrives
Wireless:
2 PC's with Linksys NIC, 1 Acer laptop with Realtek NIC, 1 KiSS wireless mediaplayer, 1 PocketPC 2003, 1 Samsung Smartphone, 1 wirless photoframe
Router config: no guestzone, static IP's, all standard options.
Thanks for the info.
Apparently, nothing special in your setting (except using static IP).
Although I don't have much hope that changing to static from DHCP fixes the shareport problem,
I'll try it.
-
Thanks for the info.
Apparently, nothing special in your setting (except using static IP).
Although I don't have much hope that changing to static from DHCP fixes the shareport problem,
I'll try it.
It might. If your NIC is flakey or your OS DHCp is 'off' this might cause disconnects.
-
Just want to report the same issue (useless shareport not working/connecting after a day or two from rebooting the router), and hopefully my info helps D-Link to reproduce this problem.
Printer: HP PSC 1510.
Computer: Thinkpad T43p (laptop) - WinXP SP3. I typically "hibernate" it instead of shutting it down.
Shareport utility worked great under this configuration till I upgraded to 1.3X firmware + new shareport utility. Since then, as everyone else in this forum describes, it's been a nightmare.
I can't blame the OS or other USB-related stuff going on in my laptop (even hibernation) since this issue just didn't exist before firmware 1.3X.
-
Final 1.32 has not solved the printer connection problem. Still requiring a router restart in order to prints from any of my 4 machines.
Any one having any luck?
Dir-655
HW Ver A4
FW Ver 1.32
Have you put in your printers IP-adress and locked to that mac adress??
Like this: 192.168.3.102 printer name 00:00:00:00:0a:00 <= MAC-adress on USB port
It's the same if you use LAN-printer......... and other MAC-adress
Then you have always reserved this to your printer.
Working like a charm here ;D
regards
kthaddock
-
Adding my own identical experience to others here. I had to upgrade to 1.32 to make streaming Netflix work from my LG Blu-ray box ( it does work great ), but now I have same problem of shareport nonfunctional after a few days. Same symptoms as above: Using the 1.10 utility to try to connect, and it tries, then seems to time out and does not connect, but shows HP printer as available. I too had prior 1.21 firmware working fine.
One difference in my case: I have two DIR655's connected by a bridge. The "master" ( DHCP server , address 192.168.1.1) unit also has 1.32NA ( HW A2 ), but the one set up with SharePort ( 192.168.1.2 ) is the one that does not have DHCP turned on since its just a router / AP. It is HW A4. Regardless, I get the same symptoms as all here. The computers using Shareport are wired to the Shareport DIR655.
I don't understand the last post - you are implying that the USB shareport printer gets assigned a unique IP address? When I display the IP in the Shareport utility of my printer, it is simply the IP address of my DIR655 to which it is attached ( 192.168.1.2 ).
I will also add that I really love the DIR655 except for this problem - that's why I have two of them! :)
-
I don't really understand why there is so much discussion about assigning blame to the firmware. To use an analogy to Windows...
I have a desktop that is ~6yrs old (self built and upgraded in that time) and a laptop that is ~2yrs old. At this point, I have Vista on both of them and they work fine. However, sometimes (at most once/week) my desktop resumes from sleep and blue screens. This never happened with XP and it never happens on my laptop (with Vista). Now, if separate people owned my two computers, the desktop owner would say, "Vista is crap and broken b/c it blue screens", and the laptop owner would say in reply, "mine never blue screens, so it's clearly not Vista".
In the end, I do believe that it's Vista's fault (although I don't think it's crap like many people like to say nowadays). I think it is impressive in general that Windows supports so much hardware, but it's obvious to me that my desktop's older hardware just doesn't work as well with Vista. However, Vista should still be designed to support older hardware and work around any quirks, even if it's the hardware's problem.
My point is that just because some people have working Shareport with the latest firmware doesn't mean that the firmware is just fine. Obviously us users who have this Shareport issue have something in common that the new firmware is not agreeing with. Regardless of whether it's actually caused by a particular network configuration, usb device, hardware revision, etc, the fault must lie with the firmware. If, without changing anything else besides upgrading the firmware, functionality is lost, then the new firmware is to blame, plain and simple.
-
It might. If your NIC is flakey or your OS DHCp is 'off' this might cause disconnects.
Nope. Same problem.
I don't believe that the NICs of every computers (2 desktop and 3 laptops) are flakey,
and that every window OSs ( 2 Vista and 3 XPs ) have DHCP problem...
-
I had totally given up on the shareport feature after updating my DIR-655 to v1.31 then later to 1.32 because of the disconnect issue, but after reading on an other thread that the shareport feature was working better after disabling "Enable DNS Relay" under network settings-->router settings I thought I would give shareport another chance.
I have not been running on this setting long enough to say that it is working perfectly, but it is working much better than before on my setup, I usually couldn't run shareport without rebooting the router for more than 4 hours, but now I am on my second day without any reboot of the DIR-655, and shareport is still functioning. I can disconnect my printer, connect it on another computer, disconnect again, switch the printer of, then on again connecting it with shareport and it still works.
Update: Well, it worked better, but the problem showed up again, it just took longer for it to happen. A router reboot helps to get it working again....for a while.
-
I had totally given up on the shareport feature after updating my DIR-655 to v1.31 then later to 1.32 because of the disconnect issue, but after reading on an other thread that the shareport feature was working better after disabling "Enable DNS Relay" under network settings-->router settings I thought I would give shareport another chance.
I have not been running on this setting long enough to say that it is working perfectly, but it is working much better than before on my setup, I usually couldn't run shareport without rebooting the router for more than 4 hours, but now I am on my second day without any reboot of the DIR-655, and shareport is still functioning. I can disconnect my printer, connect it on another computer, disconnect again, switch the printer of, then on again connecting it with shareport and it still works.
Update: Well, it worked better, but the problem showed up again, it just took longer for it to happen. A router reboot helps to get it working again....for a while.
That's exactly what I have experienced.
DNS replay off improved Shareport working time a little bit, but the problem still there.
-
I'm new here, but this bickering is silly.
The truth is somewhere between EddieZ's "The firmware works for me" fanboyisms, and the ranters cussing about how evil d-link is.
offtopic;
Funny how somebody with working device and software is being classified as a 'fanboy'.
-
"Funny how somebody with working device and software is being classified as a 'fanboy'."
Umm... It's not your device which makes you a fanboy, it's your "dlink-does-no-wrong, 1.32NA-works-great-because-it-works-great-for-me, it's-just-all-you-n00bs-messing-things-up" style posts which make you a fanboy.
-
"Funny how somebody with working device and software is being classified as a 'fanboy'."
Umm... It's not your device which makes you a fanboy, it's your "dlink-does-no-wrong, 1.32NA-works-great-because-it-works-great-for-me, it's-just-all-you-n00bs-messing-things-up" style posts which make you a fanboy.
I understand that somebody with a working device and software frustrates the "D-link sux" and "the firmware is generically defective". And nobody likes to be called a n00b. But not liking that name doesn't make you an expert. Real experts don't take the easiest option ('it's the firmware (eventhough I really have no idea how it works)") for granted but have a broader scope in order to resolve issues.
-
I have never claimed to be an expert, and I haven't really noticed anyone else reporting problems with 1.32NA firmware claiming it either. And I don't think d-Link sux. I have been very happy with my router.
It's easy to identify the self-important experts. They're the ones who throw around terms like n00b and write condesending drivel for posts.
Anyway, I'm done with you. I look forward to a fix from d-Link.
-
I can't help it I'm an IT professional. I'll try to mask it in the future and avoid any hint towards being an SME. So much for a user-help-user forum. ;D
-
Using the IT professional as an excuse is not a good idea. Being an IT manager means to help others at your site to work out their frustrating problems in case they have any, not to escalate their frustration. You won't last long with the attitude "it works for me so it should work for you, too" from your way of speaking. Thinking that is fine but I bet you know that otherwise is true, too, in a lot of cases.
On a forum, where users try to help other users, it's best to post what you think is the solution. If it works for others, that's good, if not, a simple "sorry, I'm out of ideas." and stop the conversation there will work out much better. That's the best one can do trying to helpful without being on site, IMO.
-
On a forum, where users try to help other users, it's best to post what you think is the solution. If it works for others, that's good, if not, a simple "sorry, I'm out of ideas." and stop the conversation there will work out much better. That's the best one can do trying to helpful without being on site, IMO.
This is the best post I have read here in the past days. Thumbs up !
All other discussions will miss the topic of the thread.
-
It seems that this discussion (and the real problem at hand) as begun to stagnate. Us users who experience the problem don't have any real solutions and are left rebooting our routers every time we want to print; those who don't experience the problem have added diddly squat; and D-Link says it can't reproduce the problem. Meanwhile the discussion here has been reduced to petty arguing.
MESSAGE TO D-LINK:
If you can't recreate the problem, why not ask for it? I'm sure someone here would be happy to exchange their router. Then, you get a broken one to inspect and the user might get a working one (or, in the worst case scenario, they still have the same issue). If you get routers back and still can't recreate the problem in the lab, well that's helpful too as you would hopefully be able to start isolating the problem. Let's start moving forward on this?
-
IIRC, there's someone on this forum said he was able to make his router works with Shareport for 7 days without issue after a reflash. Before he used to have Shareport issue like you guys too. The procedure was simple, reset the router to default settings, and flash the latest 1.32NA on it again, then set everything up manually later. It's worth a shot as some of you guys might had a bad flash, importing old settings from an older firmware version or even upgrading the firmware through wireless.
-
IIRC, there's someone on this forum said ...
Here it is:
I decided to start over again and redid everything from scratch in an attempt to get Shareport working. I downloaded a fresh version of 1.32NA and the 1.10 Shareport utility directly from the FTP site. I then connected to my DIR-655 A4 over a wired connection and reset it to defaults. Next I flashed it from the file on my PC to 1.32.na "again", and setup all my settings manually. I did not touch any of the hidden settings. Next I installed Shareport 1.10 and setup my printer. Only time will tell, but so far it's been 7 days and its still working. I have only installed Shareport on my main XP Pro sp3 rig that is using a wired connected. The Printer is a Brother HL-1230 with a Centronics to USB adapter on it. If it keeps working for say another week or so I am going to install Shareport on one of my other PCs and see how things go. I definitely think its worth while doing another flash "AFTER" reseting your router to defaults if you are having problems. And as D-Link advises do not flash over a wireless connection. After the flash I went back to static IPs on my LAN and have Secure Spot, DNS Relay, Advanced DNS and DHCP turned off. I'll add to this thread as time goes by with status updates on whether Shareport keeps working or not.
-
Using the IT professional as an excuse is not a good idea. Being an IT manager means to help others at your site to work out their frustrating problems in case they have any, not to escalate their frustration. You won't last long with the attitude "it works for me so it should work for you, too" from your way of speaking. Thinking that is fine but I bet you know that otherwise is true, too, in a lot of cases.
On a forum, where users try to help other users, it's best to post what you think is the solution. If it works for others, that's good, if not, a simple "sorry, I'm out of ideas." and stop the conversation there will work out much better. That's the best one can do trying to helpful without being on site, IMO.
Good post!
Thanks!
-
BTW, the re-flash solution mentioned by alphanumeric didn't work for me. At first, I was thinking that it was fixed because I was able to print 9 hours after a reboot, which was a long time for me.
But, it turns out that yesterday, about 16 hours after resetting, reflashing, and manually setting-up my router, I had to reboot it to get it to print.
So, I am giving up on printing with shareport with 1.32NA. If a new firmware comes out, I'll give it a try. Or maybe I need to spend money on a more robust solution - a printerserver or a network-aware printer.
Grumble.
-
Has anyone with this problem tried a "beefier" A/C power adapter to see if marginal power isn't the "environmental" issue thats causing this problem?
Seems that better power has solved many problems with this and other wireless routers. And to me this makes sense, since I believe extra features/processing added in firmware updates would use more power, plus a device being plugged into the USB port would likely draw additional power as well.
The A/C adapter that came with my DIR-655 is 12 volts @ 2 amps. Something with 2.5A up to 7 amps would probably do the trick (the router only uses amperage it needs, so the extra isn't an issue).
12v adapters with higher available amperage seem readily available for laptops, netbooks, and LCD monitors for $10-20.
I'm not using Shareport or having problems with my 655 (fingers nervously crossed since I've already RMA'd one unit), but would like to see a firmware upgrade path past 1.21.
Anyone having problems tried this? Of course, don't blame me if you get the polarity wrong or the wrong adapter and burn up/out your router.... ;)
-
I've had two power packs die on me, one for my old DI-704P and one for an even older 3-Com router. Both were 5V. I rewired a power pack from an old cable modem that was 5V and use it to power the DI-704P. The current rating was higher than the original power pack. I was using the DI-704P as a print server for my laser printer, and will again if Shareport stops working again.
I don't know about the USB port on the router but on a PC by spec its limited to 500ma max current. If you exceed that the USB port shuts down. If you use an unpowered Hub it can be a problem, especially if one or more of the USB devices recharge though the USB port.
-
Hello all,
I've noticed this topic has gone cold for some time. The new FW release ver 1.33NA has been out for a few months now, I"m wondering if anyone has tried it and if so has it resolved the connection issue?
-
I understand this link ran cold for a while and coincidently I've been browsing around for the last 2 days to find a solution to this same problem and am here to tell that on my dir-628 with the newest firmware of 1.23na has the same reported problems ( I see for at least a year) on my windows vista laptop and my mac! I bought this router for this specific reason, to be able to share a hard drive with these laptops. Wired it is fine but wirelessly shareport DOESN"T WORK! Should have done my hw before purchasing I guess or maybe dlink can finally come up with something because in theory it's nice. ??? :-[ :-\
-
Hi,
If you wanna run a hard drive off this router, pony up for a proper ethernet NAS unit....you will be much happier and productive in the short and long terms...