D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: R3XNebular on May 01, 2009, 11:09:58 PM
-
The shareport utility detects the scanner however when I click connect it goes you are connected then goes back to being available one sec after. What could be the problem, happens to both VISTA 64 and XP 64
-
PLease provide more info on make and model of the scanner. Did you restore the saved router config after updating or did you do a manual config?
-
Sorry for being so Vague, I have DIR655 Rev A4. I reset all settings to default before uploading firmware. Firmware upgrade successful, everything is working fine beside shareport. Shareport detects Canon MP780 (Multi function printer) I click connect however it says receiving status and goes back to available. I then enabled multicast cast streams, it then worked.
However today I am unable to access it again and the same issue of attempting to connect and just becoming "available" again instead of saying "you are connected". The only solution so far is unplugging the power to the router and re plugging it in. It will then allow me to successfully connect however it is annoying doing that, there must be some solution out there. A person in another thread reported the same issue.
http://forums.dlink.com/index.php?topic=5252.0
-
I run Windows 7 64-bit ánd A2 hardware and have no problems with Shareport...
If the winsock2/TCPIP settings on a client are a bit off (or messed up by some other installed network app like a printer driver) these issues can arise. I suggest you remove the current printer driver thouroughly and reinstall the driver and see if it works any better.
-
I'm having the same problems. Shows my Seagate USB drive as available - but when I try to connect it says "receiving status" then goes back to "Available."
I had the same problems with 1.30 and the new Shareport Utility.
I'm running Vista 32-bit, and have firmware 1.31 now on my DIR-655.
The older Shareport worked fine with 1.22 firmware.
Other than my Shareport issue, 1.31 has been rock steady -- and I'm not sure if its the firmware on the router or the new Shareport Utility which is causing this issue.
-
If you have multicast enables on the router it's the Shareport utility together with the network layer in your PC. I have had the issue to once, did a complete network reinstall, reinstalled Shareport and the problem was gone.
-
If you have multicast enables on the router it's the Shareport utility together with the network layer in your PC. I have had the issue to once, did a complete network reinstall, reinstalled Shareport and the problem was gone.
How to reinstall network? Remove lan card & shareport & reinstall both?
-
you dont need to remove the NIC, only the drivers.
-
you dont need to remove the NIC, only the drivers.
Ok ty. What i ment was remove nic from device manager, boot and reinstall. That will do the trick too.
-
Yes I have the exact same problem (on both 1.30 and 1.31). It temporarly fixes itself if you reboot the router, but only for a couple of hours. Basically, everytime i'm going to print something it will report that the printer is offline, and if i just leave the printer window open and reboot the router from the webinterface it will start printing by itself when it's back up and running. I can then print again without rebooting for a awhile (an hour or two?) but then the problem is back. It can't be a driver issue because i have the same problem on multiple computers on both wireless and through cable.
Rebooting the computer or printer itself has no effect at all, but rebooting the router works every single time so this has to be a firmware issue. It worked perfectly in 1.21 and 1.22 with the old shareport.
Glad to hear I'm not the only one. Hope it will be fixed in 1.32
-
OK. I'm good now. Enabling Multicast Streams on the router made it work. Shouldn't that be a default?
-
It doesn't work for me. Sure it works right after you enable it but that's because the router is rebooting. After a while the problem is back.
-
It doesn't work for me. Sure it works right after you enable it but that's because the router is rebooting. After a while the problem is back.
When you reboot the router your PC's network connection is also refreshed (on/off). So it is not so obvious that the router is to blame here...
You can try a number of things:
-try putting clients in DHCP reservation
- multicast should be on
- reflash 1.3x firmware (in case of bad flash). Set up the config manually.
-
I'm already using DHCP reservation on one of two computers. It makes no difference. Multicast is on. The problem is the same in BOTH 1.30 and 1.31, but not in earlier versions.
-
I'm already using DHCP reservation on one of two computers. It makes no difference. Multicast is on. The problem is the same in BOTH 1.30 and 1.31, but not in earlier versions.
If you can find somebody with a laptop/wireless, install Shareport 1.10 and test if the same issue occurs....that would be great.. You can eliminate either the router or your PC after that.
Why am I asking this: I have had the same with a laptop. But my other laptop did not suffer and neither did my wired PC. OS reinstall solved the failing Shareport issue on the issue-laptop.
-
Definitely firmware related, experiencing this on three different computers. Shareport worked fine for 1.22, so I would rather have a firmware fixed then to go through all these driver stuff
-
Perhaps it's a good idea to isolate the issue based on the hardware version (a2/3/4). A poll for example...
-
EddieZ, I will test it when I get the chance, but my laptop has a fairly recent format and OS install (around 2 months ago) so I wouldn't keep my hopes up.
Running A4 hardware.
-
If you have multicast enables on the router it's the Shareport utility together with the network layer in your PC. I have had the issue to once, did a complete network reinstall, reinstalled Shareport and the problem was gone.
I did this all and no go. Available but can not connect.
DIR-655 H/W: A3 F/W: 1.31 + SharePort 1.10 + XP SP3 + RTL8111B lan.
So A3 have this problem for sure.
-
Look here:
http://forums.dlink.com/index.php?topic=5328.0
Charlie C
-
Why? Shareport is broken in both 1.30 and 1.31 it doesn't matter. By the way 1.31 is definitely better than 1.30.
-
Alexx you are wrong. Shareport is working perfectly with 1.30. On 1.31 I could see my
stand alone HD but it would not connect. Same conditions with 1.30 it works perfectly.
Charlie
-
Then how come it doesn't work for me and many others? I was using 1.30 from the day it was released so i think i would notice if it worked or not. Did you try to reboot your router with 1.31 and it still didn't work? If so that's not what we're talking about because rebooting the router fixes the problem for a short while.
While one of the symptoms is that it either doesn't connect, or disconnects after a few seconds, it is not the actual problem because even when it does connect the device connected still doesn't respond.
-
Alexx,
Did you properly uninstall the older client before upgrading the firmware?
There is a newer client that needs to be installed.
-
We have uninstalled, reinstalled the client several times, the new one.
-
Try this.
Uninstall the client. Remove any antivirus you might be running. Then do a registry clean. Re-install updated client, then virus software.
See that does it.
-
Alright I just tried it. It is working right now but I did a reboot not too long ago so I will report back in a couple of hours.
-
You know what? It's still working after several hours now. I'm really surprised. I'll do some more testing before i conclude that the problem is completely gone but so far so good!
Here are the steps i did, if other people have the same problem and would like to give it a go.
1. Uninstalled Shareport 1.10
2. Uninstalled the Antivirus software. In my case AVG 8.0 Free edition.
3. Rebooted the computer (it will probably ask for this after the uninstallation).
3. After rebooting I did a full registry clean and normal clean with CCleaner (http://www.ccleaner.com/).
4. Installed Shareport 1.10
I think the only imporant step here is the regclean (to clean up after earlier shareport version), because my other computer doesn't even have antivirus installed, but you might as well do all the steps while you're at it.
-
Actually it was a combination of removing the virus scanner and the regclean.
-
Hi all,
same issue for me after installing Firmware 1.31, Shareport has stopped working for me :(
I've tried uninstalling Shareport (V1.14) and running Reg clean, reboot & reinstall Shareport but still no joy :(
The only thing I didn't do was also unistall my antivirus software...in my case NAV 2009.
Will try the full suggested process tonight & report back.
Hardware Version---> A3
-
AV is a real Shareport killer. I thought we already covered that ages ago....
-
Unfortunatley... The problem is back now. So the method didn't work after all :-\ I really thought I had it fixed, but now it wont connect anymore.
Time to reboot my router AGAIN.
-
Unfortunatley... The problem is back now. So the method didn't work after all :-\ I really thought I had it fixed, but now it wont connect anymore.
Time to reboot my router AGAIN.
Thanks, so it is the firmware then, we have isolated it!
-
I have this problem too, firmware 1.31 HW:A4.
I tried the regclean and AV procedure, and it kept connection for a little while, but now it wont reconnect again. The only thing that works is a restart of the router.
-
AV is a real Shareport killer. I thought we already covered that ages ago....
No not really, uninstalling AV Software was suggested by Lycan, but it doesn't appear to be the root cause.
-
No not really, uninstalling AV Software was suggested by Lycan, but it doesn't appear to be the root cause.
I many many cases it is (together with firewalls) but this one seems not AV-related. Have you tried renewing your IP stacks / renewing your network driver install?
-
I many many cases it is (together with firewalls) but this one seems not AV-related. Have you tried renewing your IP stacks / renewing your network driver install?
yes, have you tried 1.31? maybe you will be better to trouble shoot it
-
yes, have you tried 1.31? maybe you will be better to trouble shoot it
Yes I'm running 1.31 and Shareport 1.10 on two wireless laptops, one wireless PC and one wired PC without problems.
This symptom was already present in the old version which was resolved every time I resetted the network connection on the PC (so not rebooting the router).
-
I am jumping on this thread. I have DIR-655 Firmware: 1.31NA HW:A3. SharePort on Vista mounts the shared drive but on Windows 7 it says you are connected but doesn't mount the drive at all. Both OS's are 64-bit. Anybody running successfully on 7?
Thanks,
AJ
-
Yep, running the HDD succesfully on W7 x64. It's something on your W7 config. The new UAC limits autorun on external HDD/devices. So you might want to change the UAC settigns.
-
Yep, running the HDD succesfully on W7 x64. It's something on your W7 config. The new UAC limits autorun on external HDD/devices. So you might want to change the UAC settigns.
UAC is on the lower part. As I said SharePort connects to the drive but doesn't mount it. I can browse it as shared from the Vista machine.
I tried configuring WCN with DIR-655, I had no idea where to begin with.
AJ
P.S. Never mind I fixed it.
-
I take it back, it stopped working on Win 7. I uninstalled and cleaned the registry, there was some leftovers from D-Link. Installed again, as Vista, Vista SP1 or even SP2, the software installs but not the driver..
-
fw1.31 + sp1.10 with wired PC.
Fresh install of XP SP3 with no antivirus + no firewall. = Available but not connecting
Frest install of W7 64bit with no antivirus + no firewall + no UAC = Available but not connecting
So i think problem is shareport and/or firmware.
-
aben2amu. That's a completely different problem and it's not what this thread is about at all. It is about either not connecting, or connecting for just a few seconds then disconnecting. Rebooting the router fixes it for a short while, so that's nothing like your problem. I don't think you'll get any support from d-link for a beta OS, seing as it works for you in Vista.
Xinot, thanks for that. Now we know a fresh install wont even make a difference to this problem. It really can't be anything but the firmware now. Especially since only 1.30 and 1.31 are affected.
-
aben2amu. That's a completely different problem and it's not what this thread is about at all. It is about either not connecting, or connecting for just a few seconds then disconnecting. Rebooting the router fixes it for a short while, so that's nothing like your problem. I don't think you'll get any support from d-link for a beta OS, seing as it works for you in Vista.
Xinot, thanks for that. Now we know a fresh install wont even make a difference to this problem. It really can't be anything but the firmware now. Especially since only 1.30 and 1.31 are affected.
People experienced the same issues with 1.2x.
You might want to reflash your firmware. It might help sometimes
-
fw1.31 + sp1.10 with wired PC.
Fresh install of XP SP3 with no antivirus + no firewall. = Available but not connecting
Frest install of W7 64bit with no antivirus + no firewall + no UAC = Available but not connecting
So i think problem is shareport and/or firmware.
What's your hardware revision? My A2 works great on both platforms mentioned, so it can only be firmware releated issue since the hardware revision is the dynamic component here.
-
What's your hardware revision? My A2 works great on both platforms mentioned, so it can only be firmware releated issue since the hardware revision is the dynamic component here.
Revision A3
-
Revision A3
A3 has a different switch...trying to see how that makes a difference with USB on the Ubicom platform...
-
Also with this version for some reason when printing sometimes it prints half a page then stops and just drops the incomplete page and then resumes printing the missing half of the page onto another page.
-
Also with this version for some reason when printing sometimes it prints half a page then stops and just drops the incomplete page and then resumes printing the missing half of the page onto another page.
Please mention the printer make and model...
Have you installed the latest drivers for that printer?
-
I have the exactly same problem that Alexx mentioned.
I'm very glad to find this thread.
I hope that this thread focuses on the issue Alexx mentioned
because it seems that many people have the same problem.
Does D-link agree that it is the firmware 1.30 or 1.31 problem?
If so, when is D-link going to release the fixed firmware?
-
I have the exactly same problem that Alexx mentioned.
I'm very glad to find this thread.
I hope that this thread focuses on the issue Alexx mentioned
because it seems that many people have the same problem.
Does D-link agree that it is the firmware 1.30 or 1.31 problem?
If so, when is D-link going to release the fixed firmware?
Since only a small part of users is experiencing this we really need to have more info. Possibly (some part of) the router is broken. But since it is a problem that derives from a driver/program that is depending on the host Operating System the cause can just as well be in that area. Especially since 3 out of 4 devices in one and the same home situation have no problem with printing!. That kinda excludes a router malfunction, wouldn't you say?
-
Since only a small part of users is experiencing this we really need to have more info. Possibly (some part of) the router is broken. But since it is a problem that derives from a driver/program that is depending on the host Operating System the cause can just as well be in that area. Especially since 3 out of 4 devices in one and the same home situation have no problem with printing!. That kinda excludes a router malfunction, wouldn't you say?
How many of this users that have no problems with shareport, have PC on 24/7 and shareport connected 24/7? It takes hours to me get this available, but not connect problem. No power saving options enabled. And only fix for this is reboot the router.
-
rebooting the router also resets the network connection on the PC NIC... so that's no way of telling which is to blame....
-
rebooting the router also resets the network connection on the PC NIC... so that's no way of telling which is to blame....
True, but why only shareport is effected? Everything else is playing normally, internet, torrent, everything, but only shareport connection is messed up. So it might be shareport/router/routers usb port.
-
Especially since 3 out of 4 devices in one and the same home situation have no problem with printing!
Not true. It happens on all my computers and I'm definitely not the only one.
rebooting the router also resets the network connection on the PC NIC... so that's no way of telling which is to blame....
I know that you know your stuff, but get real. It's not like it goes down after one hour one one computer and after five on the other. It goes down at the same time on all computers. Wireless or wired, with different operating systems and different hardware network adapters. Rebooting the computer (which also resets the network connection) does not fix the issue. Not even reinstalling the entire OS does. Setting up static IP or DHCP reservation does not fix the issue either, but rebooting the router always fixes the issue. You can keep telling yourself it may be the computers fault but this is a fact. And of course everything else is working just fine after the issue has occurred. The router is rock stable on everything else.
Also with this version for some reason when printing sometimes it prints half a page then stops and just drops the incomplete page and then resumes printing the missing half of the page onto another page.
Funny you should mention that, because the exact same thing happend for me the other day too. I thought it was just a one time thing or my printer acting weird but if you experienced the same thing it might be related to shareport. It has never happened to me before I started with shareport.
-
I am only saying that rebooting the router (assuming the router needs a reboot to work OK with Shareport) resets the network connection on either side. Thus saying that you cannot deduce from this rebooting that becuase you did this, it must be the router/firmware.
The 3 out of 4 situation is mentioned in another thread. I do not exclude any router problems (defects do occur sometimes) but it does show that the same error also seems to occur when other installations work fine.
The reason why only Sharepoint is affected and torrents work fine is because of the nature of shareport. Ublike other networking activities it uses a specific driver that interfaces between the TCPIP stack and the USB protocol on the router. And this driver needs the right bindings to the network stacks on the PC. These can be deleted by registry cleaners or an error in the system config that prevents the bindings from being made (lacking the necessary priviliges on Windows machines, malware, network cache etc). And even some printerdrivers that use non-conformistic install methods (Canon) will prevent Shareport from connecting correctly.
Once again, it may very well be that certain issues are caused by the router, indicating a malfunction (RMA it). But it is too easy to blame the router for everything unless you can exclude the OS. And that cannot be done without having a close look. Certainly when other devices in the same network environment work perfectly fine this will the case, or he error occurs out of the blue after a period of working error free
.
-
Since only a small part of users is experiencing this we really need to have more info. Possibly (some part of) the router is broken. But since it is a problem that derives from a driver/program that is depending on the host Operating System the cause can just as well be in that area. Especially since 3 out of 4 devices in one and the same home situation have no problem with printing!. That kinda excludes a router malfunction, wouldn't you say?
My configuration is as follows:
2 computers - WinXP SP3 (32bit)
2 computers - Vista Home Premium (32bit)
One of them (WinXP) is wire-connected,
All the other 3 computers are wireless-connected.
2 USB devices -- HP printer and the external hard disk --
are connected to Shareport thru the USB hub.
After rebooting DIR-655,
the shareport function on each computer works OK.
I can connect the USB device from any computer when the device
is available(i.e. not connected to other computers).
But, after several hours (or minutes, not consistent),
the USB devices become disconnected (i.e. available status) from all computers.
Then, I cannot connect them anymore from any computer.
( One of computers is very fresh (just bought) ).
The only way to connect is rebooting the router.
(The USB hub doesn't matter for this problem
because even, without the USB hub,
only one USB device (either printer or hard disk)
directly connected to shareport also has the same problem.)
-
But, after several hours (or minutes, not consistent),
the USB devices become disconnected (i.e. available status) from all computers.
Then, I cannot connect them anymore from any computer.
( One of computers is very fresh (just bought) ).
The only way to connect is rebooting the router.
Here shareport say connected, but its not working. Have to disconnect, and when i try to connect again it gives no error messages etc. but stay only available not connected. Yesturday and today i had this problem again, and it didnt connect again, but i didnt reboot router yesturday but i tried to connect again about half hour later and it worked ok... Today (now) its only available again and not connecting. So i dont have to reboot the router, but it just dont work allways. Weird.
update:I did clear router log and after this connected ok... Maybe coincidence, but weird..
-
Did you all do a thourough uninstall of the 1.14 version?
I did a registry clean after uninstalling, the newly installed wouldn't connect either. After the regclean, 1.10 reinstall it worked flawlesly.
I think there is no generic solution for the symptoms. Can you post the log during which time the connection is lost (and explain to which IP the client is connected? Maybe I can spot something.
-
Look there is more then just a few having this issue, it has only happened with 1.31. On all computers even ones that had no shareport programs before and this issue STILL ARISES. Therefore it is DEFINITELY firmware related, I had NO issues at all with 1.22b5 and shareport until I upgraded to 1.31 and 1.10 shareport. We have tried many solutions... can a dev just confirm that this is a prob and try to develop a solution around it.
-
Since only a small part of users is experiencing this we really need to have more info. Possibly (some part of) the router is broken. But since it is a problem that derives from a driver/program that is depending on the host Operating System the cause can just as well be in that area. Especially since 3 out of 4 devices in one and the same home situation have no problem with printing!. That kinda excludes a router malfunction, wouldn't you say?
All four OS experience this in my house so I'm pointing to a firmware issue.
-
Please mention the printer make and model...
Have you installed the latest drivers for that printer?
MP780, yes I am using the latest drivers. Someone else is experiencing the same problem too. There is DEFINITELY something wrong with this firmware.
-
H/W: A3 F/W: 1.31NA
Fresh W7 64bit with fresh install of SharePort 1.10
Wired 1Gbps Lan RTL8111B Pci-e nic with DHCP reservation through router (192.168.0.100)
USB device connected to router: Aiptek/Waltop Media Tablet
Shareport info:
USB Device Name: WALTOP International Corp. Media Tablet
Transfer speed: Full Speed
Model Name: DIR-655
Host Name: dlinkrouter
IP Address: 192.168.0.1
-
MP780, yes I am using the latest drivers. Someone else is experiencing the same problem too. There is DEFINITELY something wrong with this firmware.
So if 2 (or even a 100) people out of 100.000's units sold have a problem there is something wrong with the firmware? ::)
-
@xinot: Apart from the fact I really have bad experiences with Realtek NIC's...have a look at your NIC's energy saving settings (not only the Windows Power settings, but the NIC settings in devicemanager=> advanced), to make sure the NIC isn't just going to sleep.
-
So if 2 (or even a 100) people out of 100.000's units sold have a problem there is something wrong with the firmware? ::)
Not everyone uses shareport and the ones that are probably searching for a solution come here, judging by this threads view lots of people are having this error. This error is in direct relation with shareport and the firmware. It also can be the shareport program also I should of mentioned I did not rule that out. The way your going about is you assume its not firmware/shareport related because it works for you.
-
Not everyone uses shareport and the ones that are probably searching for a solution come here, judging by this threads view lots of people are having this error. This error is in direct relation with shareport and the firmware. It also can be the shareport program also I should of mentioned I did not rule that out. The way your going about is you assume its not firmware/shareport related because it works for you.
That's the great thing of the binary world; if there is something wrong with firmware the error can be reproduced and/or occurs for all users, no discriminatation. So the first priority is to have a look at the dynamic component: the PC where it is installed, or the router hardware revision. But the revision question will also comply to the basic binary rules (excluding malfunctioning models): if my A2 works perfectly fine, why shouldn't other A2's do the same?
-
Im Guessing its A3/A4 experiencing this issue only
-
Same issue here with A4. Fresh install of Win7 x32 on a eeePC 1000HE, and Win7 x64 on my main PC with no previous shareport installed. I doubt resetting the network stack is the issue, since rebooting both the netbook and the main pc do not fix the problem. ONLY rebooting the router fixes it. No problems in firmware 1.21/Shareport 1.14.
-
Same problem here. I have a new DIR-655 A4. I upgraded to 1.31 as soon as I got it and loaded Shareport 1.10 so there was no previous version uninstall issue. I have wired and wireless Vista Ultimate 32 systems and all are experiencing the same problem.
-
@xinot: Apart from the fact I really have bad experiences with Realtek NIC's...have a look at your NIC's energy saving settings (not only the Windows Power settings, but the NIC settings in devicemanager=> advanced), to make sure the NIC isn't just going to sleep.
No power saving options enabled in this PC (Windows power saving options disabled + manually disabled all via device manager, USB, NIC, etc.). Only monitor can go to sleep...
SharePort seems to use multiple UDP ports as i see from W7 Resource Monitor.
4 ports all the time open and 2 extra when connecting/disconnecting to device. If i read this correctly...
Have to keep this resource info on eye if there happens something when this error come again.
-
Thanks to everyone who has registered and posted about the problem. It really helps us get an idea of what scale we're dealing with and how many people are affected. I too think that this may be a A3/A4-only issue. I'm using A4 myself.
Is there anyone at all who are having the same problem on a A1/A2 hardware?
-
I have an A2 and I am having the same problem that a lot of people are having.
I have 3 computers connected to the router.
1 Win XP wired
1 Win XP wireless
1 Vista 64 wireless
When I reboot the router shareport seems to work fine and then some time later it stops working on all computers at the same time.
-
I have an A4, Shareport works after a router reboot but usually only for 1 job then it either continually tries to connect or doesn't see a device at all.
With 1.21 it worked flawlessy. I did a full uninstall of the old Shareport and registry clean and installed after reboot and turned off NOD32 (which you shouldn't have to do, but I did anyways)
I have also gone into device manager and ensured that my nic doesn't get turned off for power management.
-
I have had exactly the same problems as described in these posts - shareport device available but can not connect. My firmware is 1.31 and hardware is A3. I thought my experiences may be helpful:
I installed the shareport utility on my main desktop, which is running Vista Home Premium SP2RC, also I am running Windows Live Onecare as antivirus and firewall. When the shareport utility was installed it was added to the firewall exceptions as part of the install. Also when I first opened the utility the Onecare dialogue box opened to add Shareport to the Firewall allowed list (up and down). I am unable to use shareport on this computer as described.
I installed the shareport utility on my laptop which is running Vista Home Premium SP1 and Windows Live Onecare. Shareport was added to the Firewall exception /allowed list as my desktop computer. I was unable to use shareport on this computer as described.
I then decided to install shareport on my Windows 7RC computer, this uses AVG Free A/V (not Onecare). When Shareport installed it was added to the firewall exceptions and when I ran Shareport, it detected The USB device connected to my router as with my other two computers BUT this time it connected, installed neccessary drivers on my computer and was available for use.
This leads me to the following:
The 1.31 firmware is OK, the Shareport Utility is OK with Vista (as other Vista users have used Shareport successfully), but there is a problem using the Sharepore Utility with Windows Live Onecare (and maybe some other Antivirus / Firewall solutions).
To test this, I disabled the Live Onecare Firewall and found that any available USB device would successfully connect; when I re-enabled the Live Onecare Firewall, I could no longer connect to the same USB device - back to the original problem!
-
I have this problem too, and I don't have Antivirus installed on one of my computers, I tried to disable the firewall too, on that computer but that didn't make any difference.
If I reboot the DIR-655(Firmware 1.31 HW: A4) I can connect fine even if the firewall is enabled, and it works for a while, but if I try to connect again later on, the shareport utility shows my printer as available, but when i try to connect it says: connecting, then receiving status, and then shows it as available again. I have also experienced that when I switch the printer on, the utility doesn't show the printer at all. A reboot of the DIR-655 helps on this problem too, but this problem is rare compared to the connect-disconnect problem.
-
Perhaps your NIC is entering powersave mode and fails to re-initiate the Shareport USB device driver. Windows has had problems with this for years.
But it's just a suggestion, since I cannot see into other PC's config. ;)
-
"Perhaps your NIC is entering powersave mode and fails to re-initiate the Shareport USB device driver. Windows has had problems with this for years."
Wouldn't powersave mode affect other network traffic if that is the case? Everyting else I do over the network works. The behaviour is the same on all my computers and they all have different network adapters.
I have also tried to reboot my pc, and the problem is the same until I reboot the DIR-655
-
No, not when it goes to sleep, wakes up and persues normal network traffic but the special USB driver for Shareport has been unloaded and does not bind gain with the TCPIP stack.
Perhaps not the right words, but this scenario also occured with the 1.14 version. I still claim this behaviour is a Windows issue.
-
No, not when it goes to sleep, wakes up and persues normal network traffic but the special USB driver for Shareport has been unloaded and does not bind gain with the TCPIP stack.
Perhaps not the right words, but this scenario also occured with the 1.14 version. I still claim this behaviour is a Windows issue.
If every other network and usb hardware & software works ok after sleep, its Windows issue when Shareport can not? Maybe theres something in Shareport software that should tweak a littlebit?
-
If every other network and usb hardware & software works ok after sleep, its Windows issue when Shareport can not? Maybe theres something in Shareport software that should tweak a littlebit?
I agree, and in any case a PC reboot should fix that problem anyway, but it doesn't, a DIR-655 reboot does, for a while.
-
Do me a favour and get some more info on USB-over-TCPIP requirements and you will find that the drivers required are somewhat more complicated than the USB mouse driver on your PC.
-
Yeah but the USB-over-TCPIP requirements is Shareport 1.10 and DIR-655's responsibility! If it doesn't work on say 10% of all PCs (i recon the % is probably closer to 50 judging from the posts on the forum but thats beside the point) then D-Link and ONLY D-Link alone is to blame. Stop blaming the PC. it even happens to Macs so it should be quite clear who should take action. Whether or not the PC hardware is the cause of the problem is completely irrelevant because D-Link is required to make drivers that works around the limitations of the hardware in the PC.
This is a problem with D-Links product and not my network adapter. Therefore D-Link should provide support for it. I know you're trying to help but right now it just seems like you're trying to put to blame on Windows.
-
Here here! No offense EddyZ, but it doesn't really sound like you are considering even the remote possibility that something might be buggy in either the brand new 655 firmware or the brand new Shareport 1.10 software. Since a windows reboot does nothing to fix the problem, it just does not make any sense that it is a problem on the PC end.
Yeah but the USB-over-TCPIP requirements is Shareport 1.10 and DIR-655's responsibility! If it doesn't work on say 10% of all PCs (i recon the % is probably closer to 50 judging from the posts on the forum but thats beside the point) then D-Link and ONLY D-Link alone is to blame. Stop blaming the PC. it even happens to Macs so it should be quite clear who should take action. Whether or not the PC hardware is the cause of the problem is completely irrelevant because D-Link is required to make drivers that works around the limitations of the hardware in the PC.
This is a problem with D-Links product and not my network adapter. Therefore D-Link should provide support for it. I know you're trying to help but right now it just seems like you're trying to put to blame on Windows.
-
Yeah but the USB-over-TCPIP requirements is Shareport 1.10 and DIR-655's responsibility! If it doesn't work on say 10% of all PCs (i recon the % is probably closer to 50 judging from the posts on the forum but thats beside the point) then D-Link and ONLY D-Link alone is to blame. Stop blaming the PC. it even happens to Macs so it should be quite clear who should take action. Whether or not the PC hardware is the cause of the problem is completely irrelevant because D-Link is required to make drivers that works around the limitations of the hardware in the PC.
Just to be clear: Dlink is not responsible for the buggy features of an Operatigng System (standby/sleep mode).
Sorry to say, but you are generalising all issues (adding together Mac issues with PC issues), excluding the OS and hardware from being one of the possible causes and, that's what is being shown, you really have no clue about IT. That's not a 'bad' thing, but do not pretend that without this IT knowledge you can solve or even pinpoint these issues.
-
Yesterday I reported that I was able to connect my USB devices on my Vista computers by switching off my Live Onecare Firewall. Unfortunately this morning when I tried to connect (Firewalls Off), I found that I was unable to connect to the USB devices. I tried to connect using my Windows 7RC computer and now this computer would not connect either.
The only difference was that yesterday, when I was able to connect, I had just removed the power from my router and left it unpowered for a minute. When I repowered the router, I was able to connect as described in my earlier post. Today, when I was unable to connect, the router had been powered up since yesterday.
It seems hard to imagine that this is an operating system problem, as I am using '3' systems - Vista SP1, Vista SP2 and Windows 7RC - none of which will now connect
-
EddieZ, that's not my point. Im not saying it's impossible that the cause is the PC. I'm saying that the cause of a non-isolated issue is completely irrelevant. It's D-Links responsibility to bring out a funtional product period. It doesn't matter if the cause of the problem is Windows because shareport is a windows product.
If D-Link would come out with a step by step guide "How to get shareport to work in Windows" that would of course be perfectly fine, but they have not, so blaming windows without telling people how to fix is it simply not good enough.
Also I don't know which of us knows less about IT because you clearly think that rebooting your computer won't wake up a sleeping HW component, but rebooting a 3rd party router via the web interface, will.
-
Excluding is what anyone does who shouts: It's the router/firmware. There are a great number of circumstances that can cause Shareport to malfunction, ranging from the PC network config, standby mode, AV/firewalls to USB hubs or devices that are not self powered.
Seemingly no one wants to do some objective elimination. It's easier to shout: "It's the firmware", even though it seems to work on other routers without any issues...
-
Excluding is what anyone does who shouts: It's the router/firmware. There are a great number of circumstances that can cause Shareport to malfunction, ranging from the PC network config, standby mode, AV/firewalls to USB hubs or devices that are not self powered.
Seemingly no one wants to do some objective elimination. It's easier to shout: "It's the firmware", even though it seems to work on other routers without any issues...
Well i have done everything you have asked to do to fix this, but no go... So what next? I should fix every Windows?
-
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?
-
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
-
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?
-
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: 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).
-
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!
-
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.
-
I'm following this thread, hoping for some sort of suggestions that works - or even someone from Dlink asking followup questions.
-
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
-
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.
-
Lycan - would it help to send you our saved config files?
-
No, we have no way of reading them, what I'm looking for is common things among the computers that are having shareport problems.
-
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.
-
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.
-
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?
-
To be honest, we have a hard time locating the older A1/2 models, so yes. We test with the current revisions.
-
To be honest, we have a hard time locating the older A1/2 models, so yes. We test with the current revisions.
You can buy it from me (+post/packaging)... ;)
-
I'll take two, for.......testing......yea.
-
A4 works good for me with 1.31 and SharePort 1.10. I have tried an EPSON MFP with both printing and scanning, a WD USB Hard Drive, and a USB FLash drive and all work fine from both PCs. I have XP SP3 on one and Vista 32 bit on the other.
Windows Firewall seems like no issue as on one of my PCs.
With 3rd party firewalls, seems like it works after you add SharePort as an exception (it popped up automatically and asked me if I wanted to make an exception the first time I used it with Symantec).
No issues with AVG on one PC or Symantec on another as far as anti-virus.
For the people that have to reboot their router after a while to be able to re-connect to their devices, I wonder if there is something common running between all of them. Perhaps post a screenshot of the processes (from Task Manager) being run on the PCs? Perhaps some setting they have all enabled in their router? Perhaps a screen-shot of the SharePort Window to see if they all have a common device or device type connected?
Strange ???
-
I'm with you, jh
It really boggles my mind that this issues are firmware related. Just because I don not understand why I cannot reproduce the issues of suffer from them...
-
I'm with you, jh
It really boggles my mind that this issues are firmware related. Just because I don not understand why I cannot reproduce the issues of suffer from them...
Could it just be something so simple like usb voltages? Some devices may be more sensitive to voltage changes. Could there be some usb voltage dropouts in this router? Can energy saving features in this router (A3/A4 ?) do something like this?
From DIR-655 features:
CONSERVES ENERGY
Automatically powers down ports that have no link
Budgets power output for different Ethernet cable lengths
Includes wireless LAN scheduling, which can shut down your wireless network when not in use for further power savings
...
-
Sounds like your own to something Xinot
-
To be honest, we have a hard time locating the older A1/2 models, so yes. We test with the current revisions.
Not a problem finding them in Canada. I'll trade you an 825 for it.
-
Xinot, that's actually the first explanation regarding this problem that would make perfect sense. It's definitely a possibility.
-
My Dir-655 A3 1.31NA is doing the same thing. Available > Connecting > Determining Status > Available.
With 1.30NA (Shareport Utility 1.14) I started getting issues detecting my printer on the USB port (Brother HL2040).
Firmware 1.22b5 and Shareport Utility 1.14 worked flawlessly on Windows 7 Beta. Fresh installed Windows 7 RC
Reboot Router and it connects.
This morning I rebooted router, connected on this pc and left house. Came home, installed Shareport 1.10 on Wifes computer, requested port, which was received correctly. Released port, her PC went Available > Connecting > Determining Status > Available and neither PC could connect to USB Port until router reboot.
Im also getting the problem where 2 pages turns into all the paper in my tray to print. 1st page fine, second page and others may have a smidge of something along the top, with or without the date at bottom ... second page (2/2) finally printed with errors some 5-7 pages later, then blank paper continued to be printed until I turned off printer.
The printing issue was during testing whether the "Auto-Connect for Printing" made the issue go away. I have not had it running long enough to tell if the connect issue is minimized, but the first thing I tried to print was flawed ... but it did connect and disconnect automatically.
Memphis PC Guy
-
I'll take two, for.......testing......yea.
Trade for a 855?
-
My router is dir-655 A3 and three pc with 32 bit Win XP SP3, Vista and win7. If I reboot router then it works. I tried all modification mention in this thread.
-
Have this available but doesnt connect problem with Aiptek/Waltop media table (powered by usb) and with 2,5" usb hdd with and without extra power.
Weird is, that my 3,5" Lacie usb hdd with external power supply wont work at all. Shareport found, see and connect to it ok, but every time it refresh status, this hdd goes to available status again. New connect attempt and it connect again.
DIR log looks like this when i connect to this hdd again via Shareport:
[INFO] Sun May 17 12:39:23 2009 Silex: usb detected
[INFO] Sun May 17 12:39:23 2009 Silex: get usb descriptor
[INFO] Sun May 17 12:39:23 2009 Silex: vid=59F pid=951
[INFO] Sun May 17 12:39:23 2009 Silex: found new usb device
[INFO] Sun May 17 12:39:23 2009 Silex: remove usb device
So when this lacie hdd goes to available state, and i connect to it again, router will remove this usb device first and find it again.
This hdd doesnt show in windows explorer either.
edit:UPDATE
Lacie problem was too long USB cable even thought this hdd have external power supply.
5m (16 feet?) cable no go with router/shareport, but works ok connected directly to pc.
2m (6,5 feet?) usb cable works ok with router/shareport...
:-\
-
One more...
After upgrading to 1.31 and 1.10 I have the exact same problems.
I am running with:
DIR-655 - HW Version: A2 - FW Version: 1.31NA
From a laptop with Win 7 RC Build 7100 with NOD32
and a desktop with Win Vista Ultimate 32 bit with KAV2009
Shows that my Kingston HyperX 2 GB DataTraveler is available but cannot connect
ONLY a reboot of the router seems to help....for a minut to several hours...
I have tried allmost every hint in this tread (exept a clean OS install), but nothing seems to help.
The 1.31 firmware, in all other instances, is working flawlessly...no complaints there.
My guess is, that it is a SharePort Utility problem.....
-
Hi there,
I am normally a lurker, but I have been reading this thread with interest and had to post.
Turn off auto power on/off in printer settings?
I have been having the same problem as other people with having to reboot the router because SharePort does not connect. SharePort sees my printer (Canon Pixma IP4000) and I can print after my DIR-655 A4 has been rebooted, but after some time, it will no longer connect.
For the past two days though, it has been working perfectly. All I did was disable the auto power on/off power saver on my printer. Basically, I leave my printer on all the time. Could someone else perhaps check if you printer's power saving features are activated/deactivated?
I may be just lucky though, so I will post again if the error returns.
Gary
-
I have no issues (to start with)
But I have my Samsung on powersave. I did set Shareport to connect automatically when a print command is given and prolonged the disconnect time to 120 seconds after giving the print command. The printer needs some time to resume from powersave.
If this is the cause of the issue I would laugh my balls off, by the way :P (no offense intended to Monolith, it's the plain simplicity of this possibility)
-
I turned on my external hard disk and it is always on because it doesn't have
autopower feature. And I turned off my printer's autopower on/off feature.
But still same problem.
-
Hi there,
I am normally a lurker, but I have been reading this thread with interest and had to post.
Turn off auto power on/off in printer settings?
I have been having the same problem as other people with having to reboot the router because SharePort does not connect. SharePort sees my printer (Canon Pixma IP4000) and I can print after my DIR-655 A4 has been rebooted, but after some time, it will no longer connect.
For the past two days though, it has been working perfectly. All I did was disable the auto power on/off power saver on my printer. Basically, I leave my printer on all the time. Could someone else perhaps check if you printer's power saving features are activated/deactivated?
I may be just lucky though, so I will post again if the error returns.
Gary
I think you just got lucky because that wouldn't explain why rebooting to printer doesn't work but rebooting DIR-655 does. If that was the reason it would be the other way around.
Anyway I just checked my powersave settings and it was at just 5 minutes (with no option of turning it completely off). I know for a fact that it works long after 5 minutes when i reboot, and I think all it does is to turn off the display anyway.
Another thing is that it's not only happening with printers, but all kinds of USB-devices, so i very much doubt the problem is in the usb-device.
-
I posted this in the other thread, but since this one is much larger, I put it here also.
Hardware: A1
Firmware: 1.31NA
Shareport: 1.10
USB device: Canon Pixma iP2600 Printer
PC no.1: Desktop with Windows 7 RC 64bit, wired connection
PC no.2: Sony Vaio Z590 with Windows 7 RC 32bit, wireless N connection
PC no.3: Sony Vaio T250 with Windows XP SP3, wireless G connection
Problem: Same problem as others. Printer works after router reboot for a couple of hours. After that it will be unable to connect. If I then reboot the router again everything will start working automatically for a few hours. Rebooting the computers, the printer, or shareport itself does not help. Only rebooting the DIR-655 works.
-
Anyone want to buy a DIR 655 A2 that is actualy working (mine)? ;D
-
I'd hang on to it - it sounds like a collector's item, a router that works.
-
I'd hang on to it - it sounds like a collector's item, a router that works.
Just add a smiley ( :) ;) :D ;D 8) :P ) and you get the idea
-
Anyone want to buy a DIR 655 A2 that is actualy working (mine)? ;D
Maybe your system is just so bad that it just works ok when it really should be broken. Or maybe you are just so in love to your A2 that you just can not see it faults.
;D
-
No faults here with my A2 either.
-
Or maybe you are just so in love to your A2 that you just can not see it faults.
;D
No, I can distinguish the difference between a device and a woman ;D
-
No, I can distiguish the difference between a device and a woman ;D
And winner is? ;)
At least it should be possible to get this device work like it logically should work.
Female logic is... different story ... ...
ps. any news about 1.32? beta? something? ::)
-
No news here. The gates of Perestroijka have closed on me. 8)
-
Last word from Tech support was they couldnt reproduce the problem. So until they can, gonna be hard to fix it. There are definite changes since the beta which makes the Beta kinda useless if you ask me :) The Shareport Utility version number changed (confusing) and things are added back (802.11b etc) and then released "untested"
-
Well, I'm not unhappy with 1.31. No issues and Sharport working great with the new features.
But I guess I'm alone in this.... ;)
-
It seems that there are other unhappy Dlink users out there:
http://www.dslreports.com/forum/r22333492-Shareport-problem-on-DIR655
What has happened to the dlink engineers that were taking an interest in the problem?
-
Waiting until the tech lab guys can replicate the issue. Without that there's no solution....
-
I'm having the same issue of being able to connect to devices and then not after a while. Reboot the router and it works again. I'm using a USB hub (unpowered) and was wondering if the others having this issue are also using a hub, powered or not?
I had a Brother HL-2140 printer and a 2GB Crucial Gizmo USB stick attached to it. I noticed some odd behaviors whenever trying to use the USB stick, so I'm going to take it out and see if just leaving the printer hooked through the hub keeps the connection and allows reconnection after some time. If that doesn't work then I'll try hooking the printer directly to the router and see if that makes a difference.
BTW, I'm an experienced software engineer that worked as a tech support rep in the beginning of my career. I agree with others that the problem is likely NOT at the PC level.
A4/1.31NA
-
I have this problem with devices connected directly to DIR-655:
- Lacie 3,5" USB HDD with external power (with 2m usb cable ok but with disconnect/available problem. with 5m cable shareport can see and connect to hdd but return instantly to available status, and windows wont see this hdd at all)
- USB powered 2,5" HDD with and without extra usb power plug (Y-cable)
- USB powered Aiptek/Waltop media tablet
No device have any problems with direct PC connection...
-
Even though I don't believe it is the client software, another thing I am trying is the latest client from the Silex site. These are the people who manufactured the underlying SDK for the client and their driver (SXUPTP) is 1 minor version newer, so why not;) Their client looks a lot like the d-link branded version, because they are the originators, and it works with the dlink router. Here is the link to their client in case anyone is interested:
http://silexamerica.com/support-and-downloads-supportmenu-160/product-support-information-supportmenu-137/200?task=view (http://silexamerica.com/support-and-downloads-supportmenu-160/product-support-information-supportmenu-137/200?task=view)
-
Even though I don't believe it is the client software, another thing I am trying is the latest client from the Silex site. These are the people who manufactured the underlying SDK for the client and their driver (SXUPTP) is 1 minor version newer, so why not;) Their client looks a lot like the d-link branded version, because they are the originators, and it works with the dlink router. Here is the link to their client in case anyone is interested:
http://silexamerica.com/support-and-downloads-supportmenu-160/product-support-information-supportmenu-137/200?task=view (http://silexamerica.com/support-and-downloads-supportmenu-160/product-support-information-supportmenu-137/200?task=view)
Thx, ill try this one.
edit. Updated only sxuptp driver manually via device manager.
With SXUPTP driver 3.3.5.0 (shareport default is 3.3.4.0) -> 4+ hours and shareport+usb powered hdd working ok.
edit. 6h with no problems
EDIT: No go. My PC was offline some time (so shareport was not connected) and when i boot my system up again, shareport didnt even see this HDD anymore. I unplugged it from router and plugged it back, and after this shareport did see it ok again but with same problem i had wit my Lacie hdd and too long USB cable. So shareport found my hdd ok, and connect to it and say connected but after refresh it goes back to available state... ??? Nice..
Router reboot fix this again. So how can this be? Shareport connection go broken when my PC is off?!? Some usb power saving options in router?
-
Updated sxuptp driver manually also. Tried 3 different USB devices which connected immediately; but I now had other problems:
Lexar USB Jumpdrive - connected immediately, appeared in Windows Explorer (Computer) but I was unable to access Explorer froze and I had to restart my computer. Also I was not able to disconnect this device reliably from Shareport.
USB drive - connected immediately, but did not appear in Windows Explorer (Computer), I also had problems disconnecting this drive but after a long delay it usually disconnected.
USB HDD - connected immediately, but did not appear in Windows Explorer (Computer). Drive disconnected without any problems.
While experimenting with these devices, I had a lot of problems with Windows Explorer freezing and in each case I had to restart my computer.
It seems like we have half a solution
-
...
It seems like we have half a solution
Yep like 50/50. Our PC and usb devices are ok, and router + shareport are bs... ;D
-
I've always been puzzled how rebooting the router, cures all of the problems on all my network computers so that shareport works and then after a few minutes (if I am lucky to last that long) all my computer problems return and shareport stops working. ???
I did read on one of the forums that the beta firmware 1.30 worked without any problems with shareport; as I never tried it and it is no longer available, I wonder if anyone else had success with the beta firmware.
-
Any one tried installing the whole Silex app?
-
Hi folks
Don't know how this applies to anyone else, but was having the same issue with my printer not connecting after a few hours until I reset router. I have since updated my network driver (Realtec RTL8168C(P)/8111C(P) Family PCI-E GBE NIC) and rebooted my router. Since that time I have had no issues connecting. I'm not sure if this is what fixed the issue ( or if the problem is truely cured) but I thought I'd post anyway.
PS this was several days ago.
-
I did read on one of the forums that the beta firmware 1.30 worked without any problems with shareport; as I never tried it and it is no longer available, I wonder if anyone else had success with the beta firmware.
No the problem intruduced with 1.30, so it is the same with that as 1.31. 1.2x worked fine though.
-
Hi folks
Don't know how this applies to anyone else, but was having the same issue with my printer not connecting after a few hours until I reset router. I have since updated my network driver (Realtec RTL8168C(P)/8111C(P) Family PCI-E GBE NIC) and rebooted my router. Since that time I have had no issues connecting. I'm not sure if this is what fixed the issue ( or if the problem is truely cured) but I thought I'd post anyway.
PS this was several days ago.
There is not a generic cause for the issue, as it is not a generic issue (hit me...). The network binding/configuration is one of the causes. Since a lot of people see the same syptom they automatically say it is one and the same root cause. And that is yet to be seen, although this behaviour ("hey, you're leg hurts too? Must be broken, just like mine") is very enjoyable from a sociological point of view ;)
-
There is not a generic cause for the issue, as it is not a generic issue (hit me...). The network binding/configuration is one of the causes. Since a lot of people see the same syptom they automatically say it is one and the same root cause. And that is yet to be seen, although this behaviour ("hey, you're leg hurts too? Must be broken, just like mine") is very enjoyable from a sociological point of view ;)
In that case:
Why will a reboot of the router fix the problem, but NOT a reboot of the computer?
Why will the problem happen at the same time for all computers?
Why will it happen with ANY operating system, and ANY network adapter with both wired and wireless connections?
Why will the problem still occur regardless of whether or not the computers are on or off?
I am much anticipating you reply, hopefully with a logical explanation as to why the network configuration is the cause when the computer isn't even powered on. Really looking forward to it. After all, you IT skills are far greater than the rest of us right? ::)
-
Can't you read? ??? There are multiple causes for the symptoms, not excluding possible flaws in either software, firmware or even flawed revisions. But...you don't have to be an IT guru like me ;) to understand that if it really is a firmware or software error, there can be no exceptions. Or there is another variable present with you guys that triggers this behaviour (revision, network setup etc).
Furthermore, there have been reports on the forum about a 4 PC set-up, with only one PC failing consistently with Shareport and the others doing just great. This kinda supports my first sentence, doesn't it?
In return you can answer one question for me: why does not everybody suffer from these issues?
-
After problems with SXUPTP 3.3.5.0 that i mentioned before its has now run ok over 15 hours. Newer before worked this long ok. :o
Could be something else caused this connection problem before with this driver as it now seems to run just fine... Have to boot my pc and see if it work ok after this too.
edit:shareport freezes when i tried to boot my pc. Now when shareport its connected and working ok, it can not DISCONNECT, and after boot it just can not find my usb hdd anymore.
Router reboot didn't help either, but i had to unplug this hdd from router and plug it in again.. :-X
-
Can't you read? ??? There are multiple causes for the symptoms, not excluding possible flaws in either software, firmware or even flawed revisions. But...you don't have to be an IT guru like me ;) to understand that if it really is a firmware or software error, there can be no exceptions. Or there is another variable present with you guys that triggers this behaviour (revision, network setup etc).
Of course there can be multiple causes. It's just that the network configuration isn't one of them. When you say that the network configuration of a computer that is turned off is the cause, it really goes to show you have no understanding of IT. Do not think for a second you can solve or even pinpoint the issue without this knowledge. :D The reason for trial and error is to exclude possible causes. The problem is that even with this trial and error you just won't exclude the PC.
In return you can answer one question for me: why does not everybody suffer from these issues?
I never claimed to know why it happens and as a consumer i couldn't care less, but my personal guess would be that the router which don't work were manufactered on another factory than the ones that work. For example if the other factory is using a different usb-port brand. What I DO know is that it worked in 1.21 and 1.22 for all of us so it should be easy to fix with a firmware upgrade.
-
I think Alexx's point holds more water then yours Eddiez. Enough of this bickering I just want this fixed... like everyone else... and for god sakes it is definitely caused by either firmware or shareport related. If it works for 1.22 why should it not work for 1.31!
-
Also can anyone source the problem to why the printer when connected prints half pages sometimes or quarter pages then resumes the printing on the next page. MP780 here.
-
Where is d-link people who should try to fix this??? Cmon D-link, answer SOMETHING about this problems people have with this router... What is done, what is not and do you need any more info etc.?
-
I've been playing around for a little while with the new firmware and Shareport. From what I see, it looks like the problem is definitely is the software. I've tried it on 3 systems now, and the system that had the old version 1.14 of shareport Utility is the one that is giving me the problems. However the major difference between that system and the other is that it is an HTPC and it has Nvidia Dual GB Lan. One of them is hooked up to my 2 HDhomeRuns and the other is to the DIR-655. If I disable the both network cards and reenable it with the one with the router first then the utility will see my Hard Drive if not then it will continue not to find it. So could the conflict be with something generating internal IPs that the utility is picking up and mistaking it for the router? (ie ATI CableCard Tuners, Servers on the system (localhost routes), or simply a dual lan configuration.
Sorry if this makes no since to anyone but that is the problem i'm having. The reason why rebooting the router fixes the problem I think is because it causes the utility to rescan for IPs and then finds the dlink the second time. Of course when there is a network interuption, or connection problem the first thing the utility does is scan for IP, and that causes the utility to break again until you either restart the router, or disable and enable the lan lines again.
If you think i'm on to something let me know. Either way they need to get it fixed. I only upgraded for the autoconnect feature, and of course that is probably the cause of the problem...laughs
WD My Book 1TB on Shareport.
Armyb77
-
Of course there can be multiple causes. It's just that the network configuration isn't one of them. When you say that the network configuration of a computer that is turned off is the cause, it really goes to show you have no understanding of IT.
You really shuld take some close reading classes. Because that is absolutely not what I've said or claimed.
And if that shows I have no understanding of IT you should talk to my company's management. They employ 178.000 best of classpeople worldwide so who's wrong here? ;D
-
You really shuld take some close reading classes. Because that is absolutely not what I've said or claimed.
And if that shows I have no understanding of IT you should talk to my company's management. They employ 178.000 best of classpeople worldwide so who's wrong here? ;D
Coming from a software engineer point of view, I would say just because not everyone runs into the problem doesn't mean its not firmware related. If there is something in the network configuration that is causing this, I would say that there is a defect in the firmware that isn't able to overcome the difference in the network. Alot of these network configurations seem pretty standard too.
-
Coming from a software engineer point of view, I would say just because not everyone runs into the problem doesn't mean its not firmware related. If there is something in the network configuration that is causing this, I would say that there is a defect in the firmware that isn't able to overcome the difference in the network. Alot of these network configurations seem pretty standard too.
True, but I am not only aiming at network configs, but perhaps even more at Windows configuration and Windows networking issues. No software will overcome problems cuased by Windows (TCPIP stack) errors. And coming from the Windows 3.0 era you can assume I've seen them all (although MS keeps surprising me :D)
So these issues - causes are also part of the larger picture.
example: running shareport 1.10 I had a problem with the time it took the USB HDD to mount (2 to 3 minutes). And all scanning settings for network and USB HDD were turned off!. After upgrading my NOD32 version this problem just disappeared! No more issues.
-
True, but I am not only aiming at network configs, but perhaps even more at Windows configuration and Windows networking issues. No software will overcome problems cuased by Windows (TCPIP stack) errors. And coming from the Windows 3.0 era you can assume I've seen them all (although MS keeps surprising me :D)
But thats not true though. They have software that run on Windows. If there are problems with the Windows TCPIP stack, then they aren't doing a good enough job coding the windows software and/or testing it. To a certain extent, although it sucks (I know this all too well), they are responsible for bugs in windows because they are providing a service that runs on it. My company uses Java. When we run into JVM bugs, we file a bug with Sun, and then depending on severity work around it. Thats how it works. I would consider USB devices stop working to be pretty severe, probably QA block.
I mean, if I am reading this correctly: Boot Router, use shareport, shareport works, wait...., shareport stops working..., reboot, shareport works. Something def seems wrong with either the driver or the firmware, whether its the TCPIP interface or USB timing issues on the firmware.
-
Ok I can reproduce it over and over again. If you have multiple active connections (Lan & wIRELESS, or Dual Lan) when both of them are active then this problem reproduces where it will show the device but not connect, or it will not show the device at all. If I disable the Lan not connected to the the router every time the problem goes away until I enable the the connection again.
To me that seems to be where the bug is, I would also think it's on the Utility side not the firmware too because it only effects the system with both connections active.
My suggestion is to disable or disconnect the LAN or Wireless device that is not connected to the router. Also the same problem may exist for connections such as Firewire or Bluetooth.
-
Ok I can reproduce it over and over again. If you have multiple active connections (Lan & wIRELESS, or Dual Lan) when both of them are active then this problem reproduces where it will show the device but not connect, or it will not show the device at all. If I disable the Lan not connected to the the router every time the problem goes away until I enable the the connection again.
To me that seems to be where the bug is, I would also think it's on the Utility side not the firmware too because it only effects the system with both connections active.
My suggestion is to disable or disconnect the LAN or Wireless device that is not connected to the router. Also the same problem may exist for connections such as Firewire or Bluetooth.
my wireless is disabled though and problem still there
-
You really shuld take some close reading classes. Because that is absolutely not what I've said or claimed.
You said the network configuration is one of the causes when we have said several times that the problem occurs regardless of computer interference. So you either must have no clue how a computer works or you are simply ignoring our testing. In any case, you are not helping.
They have software that run on Windows. If there are problems with the Windows TCPIP stack, then they aren't doing a good enough job coding the windows software and/or testing it. To a certain extent, although it sucks (I know this all too well), they are responsible for bugs in windows because they are providing a service that runs on it.
I agree completely.
-
It seems SXUPTP 3.3.5.0 will keep my usb powered 2,5" hdd connected with no problems, but now i can not disconnect it... ;D
Everything is fine until i try to disconnect it via shareport or boot my pc.
-
You forget that a Windows machine is more then the software that comprises the OS. It's a OS that's designed to operate on 1000's of different combinations of hardware. This makes driver situations very tricky.
We're not seeing any of the issues that you guys are, but that doesn't mean we're ignoring them. I'm currently forwarding all failures reported in these forums thats shareport related to our PM department.
-
:) ok guys i'm new here ,hi all, i want to report my experience though i know one's solution is not ok for everyone.
i've been having same issues and solved everything just disabling QOS engine both from router settings and windows xp, now it's working like a charm, i hope it lasts, will report if it fails again.
i have a A4 rev with latest FW 1.31 and latest shareport. i hope it helps someone.
another issue i've been having is external HDD connects after 3 minutes when my avira antivirus guard is enabled. not solved yet..i just disabled it when i have to connect, i read of other people having same issue with other antivirus software like AVG.
Marco
-
I stopped using shareport and just plugged my printer into my PC ... it works flawlessly now ... even with the router turned off!
-
This is what we're looking for! A solution! ;)
Seriously, it really stumps me how it is possible that my setup works without a problem and others' don't.
Hopefully we can provide input to Dlink about the specific configs that cause this behaviour. My thoughts right now are aimed at the SDK/core update from Ubicom that was released through 1.3x. But since I have no insight in this kit its up to Dlink to check this out.
I've done some testing with my setup and the Shareport program and found no issues. I did notice that an NOD32 update fixed my initiatlization lag. I'm still testing the disconnect I have after a period of time and I am suspecting Windows power settings for that (even when that is turned off ???). But no explaination yet for the rebooting and freezing thing
-
I wonder if dlink are using the same setup as MemphisPCGuy....
....because there are so many people on a number of different forums having this problem (apart from dlink and eddiez :)), just do a search. I looked at the dlink uk site where they described the hardware revision A3/A4 as 'Green Ethernet'. I know eddiez has described the hardware differences, but is there a difference in functionality?
-
Functionality is different for A3/A4 when you talk about the Green Internet feature. This feature will cut power to ports not being used. So there is a difference. But this might very well be a differentiating factor.
But there could also be multiple causes for the different behaviours (Shareport, rebooting, disconnects etc). I That's why i'm (kinda) trying to have people giev more specific info and settings, since the conclusion "it reboots, so it must be the firmware" is cutting corners and does not help resolving the issues...
-
I really don't know what the specific settings that you refer to are. I did anticipate that when I emailed dlink technical support, when I rang dlink technical support and then spoke to their engineer and then their product specialist that they would direct me to these settings to check where the problem was in my system. All I got from them was 'Reboot the router and then I don't know'. So eddiez, if you can do dlinks job - give me a clue which settings to check. Excuse my ignorance, I am not an it engineer - I didn't think you had to be to use this equipment.
-
:) ok guys i'm new here ,hi all, i want to report my experience though i know one's solution is not ok for everyone.
i've been having same issues and solved everything just disabling QOS engine both from router settings and windows xp, now it's working like a charm, i hope it lasts, will report if it fails again.
i have a A4 rev with latest FW 1.31 and latest shareport. i hope it helps someone.
another issue i've been having is external HDD connects after 3 minutes when my avira antivirus guard is enabled. not solved yet..i just disabled it when i have to connect, i read of other people having same issue with other antivirus software like AVG.
Marco
Has anyone with Shareport issues tried this solution? If so, has it worked?
-
Has anyone with Shareport issues tried this solution? If so, has it worked?
The only reason I bought this router for QOS. Can someone confirm it works? maybe it'll help the tech
-
no guys, it doesn't.. :(
it worked fine till i disconnected the HD.. then when i tried again.. same s**t
at least it worked fine for some hours ::)
-
no guys, it doesn't.. :(
it worked fine till i disconnected the HD.. then when i tried again.. same s**t
at least it worked fine for some hours ::)
Same problem with updated sxuptp driver. All ok until manually disconnect or reboot.
To EddieZ: If multiple computers have same connection problems simultenously, what else it could be but hardware/firmware problem?
-
Same problem with updated sxuptp driver. All ok until manually disconnect or reboot.
To EddieZ: If multiple computers have same connection problems simultenously, what else it could be but hardware/firmware problem?
Hardware failure may be a cause with one of the revisions. But this dragon has more heads (read: more causes). Opposed to your "4 PC's having the same problem" there's my (and others') "I have no issues" or " "three PC's work fine, only one is not able to connect" .
-
I really don't know what the specific settings that you refer to are. I did anticipate that when I emailed dlink technical support, when I rang dlink technical support and then spoke to their engineer and then their product specialist that they would direct me to these settings to check where the problem was in my system. All I got from them was 'Reboot the router and then I don't know'. So eddiez, if you can do dlinks job - give me a clue which settings to check. Excuse my ignorance, I am not an it engineer - I didn't think you had to be to use this equipment.
That's the whole problem: which setting or combination of settings cause the issues that we've seen. That's why I would suggest to send an overview of all settings to see if this helps to take step 1: replicate the issue(s) in the lab. I'm not the lab (that's Dlink) and I'm not a software analyst.
Only trying to get some more info out of people besides "it's the firmware!" :-\
-
Hardware failure may be a cause with one of the revisions. But this dragon has more heads (read: more causes). Opposed to your "4 PC's having the same problem" there's my (and others') "I have no issues" or " "three PC's work fine, only one is not able to connect" .
Where is this "three PC's work fine, only one is not able to connect" people? I have only see people with or without this problem. And i dont think people who have multiple PC's have same config etc. in every machine. I think your way to see this issue is little too complex. ;D
Give ALL settings.. Yeah, thats really wiseguy advice.
-
Where is this "three PC's work fine, only one is not able to connect" people? I have only see people with or without this problem. And i dont think people who have multiple PC's have same config etc. in every machine. I think your way to see this issue is little too complex. ;D
Give ALL settings.. Yeah, thats really wiseguy advice.
Not claiming I can solgve the issue. Walk through the threads and you will find it.
This is called "creating a sound basis for Dlink to solve the issue (since they don't seem capable in managing the user's input themselves)" . Thit does not happen automatically by 'wiseguys' like you who notice there's an issue and only point at the first general assumption without even considering alternatives or differentiate the issues thet are around. So either you take a renewal course in IT issue resolving or just refrain from sarcastic remarks and suggestions. Does not really help in this situation besides getting off yourself on complaining (apparently).
-
Not claiming I can solgve the issue. Walk through the threads and you will find it.
This is called "creating a sound basis for Dlink to solve the issue (since they don't seem capable in managing the user's input themselves)" . Thit does not happen automatically by 'wiseguys' like you who notice there's an issue and only point at the first general assumption without even considering alternatives or differentiate the issues thet are around. So either you take a renewal course in IT issue resolving or just refrain from sarcastic remarks and suggestions. Does not really help in this situation besides getting off yourself on complaining (apparently).
What ever... You really take this at same way.
You give only vague answers to everything. It is pointless to give more and more info to our settings and configuration if we dont know what and where to look at.
What you are saying is we should jump around like headless chickens. Real IT issue resolving. :-X
Ill quit here. This frustrated complaining is pointless too i know. I post again if theres anything to tell.
-
So either you take a renewal course in IT issue resolving or just refrain from sarcastic remarks and suggestions. Does not really help in this situation besides getting off yourself on complaining (apparently).
Do you really expect, or even think it's reasonable, for a customer to take IT issue resolving course every time theres a problem? How about you take a customer support 101 course then, because you obviously have no clue about that. The whole reason for customer support is to help people resolve issues by asking spesific questions that is likely to be the cause, but I guess you missed that part. Since you're asking for ALL settings it sounds like you don't even know where to start so I'm not sure you're even bothering.
I just did a hard reset of the router to see if there is any hope for a router spesific feature that triggers this problem. I'm not expecting much though.
-
This is, to my knowledge, not a customer service board. This a discussion board for customers to get answers from other users and IT nerds. Dlink only moderates and provides some info. So I guess you're having a misconception about the peurpose of this board.
If you're not an IT guy and only looking for solid solutions, don't get mixed up in these discussions and just follow the formal customer service guidelines for reporting malfunctioning hardware (either by phone, email or your reseller). Just a thought, ofcourse.
And these issues are way past 'resetting and all is fine'. And I can kinda 'guarantee' you that Dlink also has no clue where to look since they cannot reproduce the issues mentioned in their lab environment. So getting more info from people who do suffer from these issues is not that a bad idea, wouldn't you say?
-
Disabling QoS did not help.......
Win7 RC 7100 on Lenovo T60 Laptop - wireless via DWA-160
WinVista Ultimate 32 Bit on Desktop computer - wired
-
This is, to my knowledge, not a customer service board. This a discussion board for customers to get answers from other users and IT nerds. Dlink only moderates and provides some info. So I guess you're having a misconception about the peurpose of this board.
If you're not an IT guy and only looking for solid solutions, don't get mixed up in these discussions and just follow the formal customer service guidelines for reporting malfunctioning hardware (either by phone, email or your reseller). Just a thought, ofcourse.
And these issues are way past 'resetting and all is fine'. And I can kinda 'guarantee' you that Dlink also has no clue where to look since they cannot reproduce the issues mentioned in their lab environment. So getting more info from people who do suffer from these issues is not that a bad idea, wouldn't you say?
I agree, and im sry about this whining. Plain "more info" is still pointless to me.
Maybe it is easier to make firmware that allow us to downgrade again. ;D
-
well, to you it is pointless, but for a developper trying to debug any info is helpful when you have none to start with. ;)
Perhaps that is easier, don't know what features were updated by the new Ubicom SDK/core in 1.31.
-
In consideration of other issues, there is a thread "port forwarding issues with 1.31" - using an HP Mediasmart Server with a DIR 655 where the Mediasmart automatically configures port forwarding, but after approximately 10 minutes the port forwarding fails (more details on the thread). This is another feature that used to work with 1.21 firmware. Something working briefly and then failing - sounds familiar, is it a coincidence? Just a thought
I have both these issues - Shareport and Mediasmart Port Forwarding.
-
In consideration of other issues, there is a thread "port forwarding issues with 1.31" - using an HP Mediasmart Server with a DIR 655 where the Mediasmart automatically configures port forwarding, but after approximately 10 minutes the port forwarding fails (more details on the thread). This is another feature that used to work with 1.21 firmware. Something working briefly and then failing - sounds familiar, is it a coincidence? Just a thought
I have both these issues - Shareport and Mediasmart Port Forwarding.
Well my router can not save any port forwarding rules. No HP thing. Make rule, save & reboot = port forwarding page is empty again. Same with upnp on and off.
-
I'm wondering if there is someone who has no shareport issue with dir-655 fw 1.31NA (A4).
Does the problem happen only to very few routers reported in this thread ?
Is there someone who has no issue with dir-655 fw 1.31NA(A4) + shareport 1.10 ?
Unless I'm very unlucky so that I purchased the router with hardware defects,
I can hardly understand that D-link cannot reproduce this problem which
"apparently" many people have...
-
Well, here I am again, let's be clear, I don't want to kick any bucket, but you want peopole tao report all settings.
Do you really want to know all windows settıngs, abd all other( maybe irrelevat ) settings people make?
Because this is what you ask and you repeatedly refuse to respeciffy, even though this is a board that people are referred through to by service representatives from D-Link if they can't present them with a satisfying solution. The inability from D-Link routes people to this very board and frankly the ^&&%'(('- way you and other so called experts treat them is lacking any respect.
I, for one, am working in IT for 40+ years, I have never seen such a lack of QA and QC ın any case as this. I'm not the only ( qualified ) one to react in this way and have been called a troll before because, INHO, that's the only '' response '' D-Link and YOU got left.
quote author=EddieZ link=topic=5287.msg33165#msg33165 date=1242993947]
well, to you it is pointless, but for a developper trying to debug any info is helpful when you have none to start with. ;)
Perhaps that is easier, don't know what features were updated by the new Ubicom SDK/core in 1.31.
[/quote]
-
Hmm...pointing fingers again? Maybe that's why you were marked as a 'troll'?
To be honest, I've rarely seen so much opposition to an effort to actually try and solve issues that seem to be widespread, ánd which cannot be replicated by Dlink.
So put you money where you're 40-year experience mouth is and do something constructive instead of joining the pack and cry wolf.
-
Big E is really smart guy...
-
Thanks. You're not too bad either ;)
-
This is, to my knowledge, not a customer service board. This a discussion board for customers to get answers from other users and IT nerds. Dlink only moderates and provides some info. So I guess you're having a misconception about the peurpose of this board.
Not really. It doesn't matter what kind of board this is. If you're gonna pretend to be the expert, at least give proper advice. If you are not even going to give real advice then why are you even posting? Sure, everyone can post whatever they want but at least stop accusing everyone for not doing constructive testing.
If you're not an IT guy
In fact I am an IT guy, and I work with all different kinds of routers and network setups every day. This is why I was able to exclude the network configuration om my computer as a possible cause. So far it seems you have ignored all trial and error though.
-
Hardware failure may be a cause with one of the revisions. But this dragon has more heads (read: more causes). Opposed to your "4 PC's having the same problem" there's my (and others') "I have no issues" or " "three PC's work fine, only one is not able to connect" .
Who is this person you speak of? Can you post the link? Maybe ask him "HOW" KEY WORD "HOW" AND WHICH SETTINGS DIFFER to make one work and the other three work? Maybe you should post your settings for a start since it's working for you. Which settings am I speaking of? I don't know you keep referring to settings but WHAT SETTINGS. Vague answers are not very helpful.
-
You're asking for the winning lottery numbers. And that's, excuse the language, plain dumb.
You're all very selective in quoting and disregarding the fact I've made it very clear I don't have a solution. But if all you other "experts" prefer to keep ranting instead of actually acting as IT guys, please do.
Happy ranting!
-
You're asking for the winning lottery numbers. And that's, excuse the language, plain dumb.
You're all very selective in quoting and disregarding the fact I've made it very clear I don't have a solution. But if all you other "experts" prefer to keep ranting instead of actually acting as IT guys, please do.
Happy ranting!
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.
-
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.
-
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! :D :D :D
-
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.
-
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.
-
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).
-
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.
-
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.
-
My best bet is that the issue is in the updated Ubicom SDK (which also causes the non-reversibility of firmwares).
-
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.
-
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.
-
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.
-
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.
-
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...
-
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.
-
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.
-
Does that mean Shareport is now no longer a feature of the dir-655 A3? I have identical assus motherboards with marvell 1G nic. hardwired Ethernet cables to the DIR-655 and a Brother HL2040 laser printer.
Running Windows 7 RC fresh install
What do I replace to make shareport work like it did with this equipment and software before firmware 1.30 ?
I am getting the connection available issue and the 2 pages prints 10-15 blank/partial pages issues when using shareport.
Printer to PC via USB prints perfectly using its same driver and usb cable.
-
You could try setting Shareport to "Auto connect for printing" and extend the time before Shareport disconnects after the printjob to the max. setting (30 sec). Possibly the printerdriver 'hesitates' with the data that is sent to the printer and Shareport disconnects because it sees no data. A static PC-Printer connection will not suffer from this. Don't know for sure, but might do the trick.
-
You could try setting Shareport to "Auto connect for printing" and extend the time before Shareport disconnects after the printjob to the max. setting (30 sec). Possibly the printerdriver 'hesitates' with the data that is sent to the printer and Shareport disconnects because it sees no data. A static PC-Printer connection will not suffer from this. Don't know for sure, but might do the trick.
Which version of shareport are you talking about?
Do you have the working DIR-655(A3 or A4) FW 1.3x + Shareport 1.10?
May I know your hardware configuration and status?
-
Spent $100 on a new printer to see if the problem still exists, and it does. Had a MP780 now an Epson TX200 same issues.
-
(DIR 825 (r.A1) F/W: 1.11NA)
Yesterday I spent 75 minutes on the phone with Dlink tech support.
I finally reached a high enough level tech who said he is familiar with the problem and resolved it on his own pc/router.
We hard reset, unplugged, and restored the router. We shut off my PCs firewall (Vista). We reinstalled shareport.
We restarted and hibernated my PC just to make sure.
And you guessed it.
Shareport worked...
...for a few hours.
(On my second PC (Win7) also reinstalled Shareport, but before the hard reset - and that didn't do anything until we shut off the router.)
Because of all the actions we did, the only one that was relevant was unplugging the router which apparently resets something in the router which then allows Shareport to work.
Firmware bug. Definitely.
-Stephen
-
Hello,
I have the same problem on my A2 revision. I have made some tests and I can't see what is wrong. I even tested by requesting the printers on 2 computers exactly in the same time. One had the printer, and the other couldn't. (so it is probably not a dead lock).
When I have the problem, one computer (1) has the message telling that it is trying to do a connection (so the problems seems to be there between the request of the lock, and the losk is accepted) and on the other computer (2), I have a message telling that the printer is used by another computer (the computer 1).
The printer is "Epson Aculaser C900".
I don't use WIFI at all (disabled). If someone want, I can post a backup of my configuration
Also, all was fine with the firmware 1.21.
Thank you
Marc
-
The SDK is less the problem here. More then likely I would blame the updated Shareport that was added in to the firmware before release.
However I am aware of the troubles being faced but so many of you. We are not ignoring you, however I am currently working to isolate and resolve the DNS Relay issue in this firmware, once that is done I can focus on shareport.
We will get this hammered out.
-
That is a fair response. Glad to see you guys acknowledge issues. Love my DIR-655 and DNS-323.
-
It is yes. Thank you for that.
Anyways, today when my shareport lost connection to my media tablet (connected but not working), i turn shareport utility off, unplug media tablet from router, and start shareport utility again. No usb devices connected to the router and yet shareport show my media tablet available. Try to connect, it will and say connected, but after few seconds it return to available status again.
It seems like shareport utility are not talking with router at all.
Maybe this mean something, maybe not..
-
Have had shareport working for 48 hrs:
I turned off Advanced DNS Service in the router config and Auto connect in Shareport config. Doesn't make sense that the former would affect anything, but I am open to fantasy at this point. Can someone verify this? I have been able to manually connect from my W7 RC1 over many attempts where previously it failed.
-
Update - Working now for 72h. Proceeding to test with Auto Connect enabled.
-
Sadly, my 655 has always had advanced dns disabled and i have had no success =(
-
Party's over - once I tried to connect my wireless netbook, it caused the whole system to go back to its old ways.
-
Update - Working now for 72h. Proceeding to test with Auto Connect enabled.
Working for me 24 hours now, I just ENABLE Advance DNS on the router ,Reboot and still working.
1.- Dell XPS 420 Wired Win7 RC2
2.- HP dv5 laptop Wireless Win7 RC2
3.- Acer laptop Wireless XP sp2
all my computer was able to connect thi morning. :-\ wierd . .
-
My Advanced DNS was always off. Thus it is not related with this issue.
-
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.
-
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.
-
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 ;)
-
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.
-
Just remember: As long as there is a next version after 1.10, there's hope ;)
Wait and see...
-
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.
-
I have the powered external hard disk and the powered usb hub.
But same problem.
-
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.
-
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.
-
"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
-
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
-
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.
-
My best guess is that there's an incompatibility between the Silex virtual USB program/driver (we call it D-Link Shareport ;D) 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 ;))
-
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
-
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
-
Hey guys, More bad news, the 1.32 beta version did not fix the connection issue, after a couple of hours since the flash and a reboot of the router, I'm still not able to connect to my printer from either of my 3 machines (2 vista's and 1 XP). Ver 1.32 has not fixed the problem.
-
Any error messages in the log?
Just a reminder: not all Shareport connection issues have to be firmware/driver related...If there's somthing wrong with your TCPIP config on Windows, a new firmware is not going to solve that...
-
Croket is right. 1.32 doesn't fix the problem after all. Exact same thing as before. The log shows nothing.
-
Just a thought,
my Samsung CLP-350 printer has a Power Safe mode which it enters after 20 min by default and I can't wake it up again connected via shareport.
If I set the Power Safe to 120 min, the printer stays connected and is reachable for 2 hours.
This might be a special situation with a special device but perhaps your printers behave similar.
USB flashdrives stay connected and work properly until I disconnect them via tool.
-
Croket is right. 1.32 doesn't fix the problem after all. Exact same thing as before. The log shows nothing.
Same thing here. Not working ok.
-
Strange thing, I have a Samsdung CP 315 and it goes to sleep after 5 minutes. I can wake it up with no problem and connect/disconnect when needed fro wired PC and laptops (when you set Shareport to connect on a print job, don't forget to set the Sahreport timer to last at least 120 secs, otherwise Shareport will disconnect before the printer has restored from sleep :) )
-
Strange thing, I have a Samsdung CP 315 and it goes to sleep after 5 minutes. I can wake it up with no problem and connect/disconnect when needed fro wired PC and laptops (when you set Shareport to connect on a print job, don't forget to set the Sahreport timer to last at least 120 secs, otherwise Shareport will disconnect before the printer has restored from sleep :) )
No, doesn't change anything. But no problem as the CLP-350 is a networked printer and I only used it to test the shareport with my WIN7 x64 machine.
-
I tried the new beta firmware 1.32 and it also did not solve the problem for me. The Photosmart A716 worked fine only on one laptop (out of 3 computers in my house) for one day, now it's back to not being able to connect (or it connects and after a few seconds it disconnects). All of my computers use Win7.
Specs:
All computers OS: Windows 7
Firmware : 1.32 beta
Router: DIR 655 A3
Shareport: 1.10
-
My drive stays connected longer and if it loses connection it will reconnect, sometimes. I've been receiving nonspecific network errors that don't show up in the log. I get the big red X from Shareport and when this happens the only way to reconnect is to ---- drum roll ---- reboot the router. None of this is related to the problems I experienced with copying large files to a USB drive. It's simply a very unstable connection to the drive as the connection severs frequently, then reconnects, and eventually complete failure. But at least it is different than before the upgrade. Also, I found that if I reboot my PC while the drive is connected it will not reconnect after the computer restart.
-
Hello,
The problem is not solved for me too. I made a backup of the configuration, flashed, reseted to factory settings and restored the configuration. Still impossible to reconnect after one day.
Marc
-
Just looked at my error logs, and No there are no error msgs. I tried playing around with some settings after the upgrade flash but sill had no luck. the only way it works is if I reboot the router.
-
1.32 did not fix my shareport issue either
-
I bought DIR655 just because it offer shareport function. So, I am very keen to see a bug-free firmware on shareport. However, to be fair to the DLINK technical teams, without "reproduce" the problem in their envirnoment, there is no way for a software engineer could fix the bug. From a consumer point of view, totally right, it's DLINK's problem. From a technical or practical point of view, they need to reproduce or got a "problem machine" in order to proceed. You can challenge or complaint to the DLINK company how much resources DLINK company put in this issue but fingerpoint to the technical team seems a bit unfair.
Seems whoever do not have problem before, most (I cannot say all) of the upgrade firmware version will continue works fine (touch wood, I am one of the lucky guy). One the other hand, whoever have problems in previous version, upgrade do not fix this problem. So...the simple conclusion draw from this is the problem is a complex combination of Windows (and installed software etc) with the firmware. It will be good if anyone currently has problem, could do a complete reinstall the windows and sharepoint, and then install the software one by one, until the problem occurred will definitely help the team to reproduce the problem. Of course, is there anyone willing to do this for the sake of the other???? What I saw so far is most of the people just scream out the symphtom and to certain degree, this give only a very little help for the team to locate the bug. It just shooting in the dark. For those user has no problem (just like me), there is nothing we could help...it just work.
-
I bought DIR655 just because it offer shareport function. So, I am very keen to see a bug-free firmware on shareport. However, to be fair to the DLINK technical teams, without "reproduce" the problem in their envirnoment, there is no way for a software engineer could fix the bug. From a consumer point of view, totally right, it's DLINK's problem. From a technical or practical point of view, they need to reproduce or got a "problem machine" in order to proceed. You can challenge or complaint to the DLINK company how much resources DLINK company put in this issue but fingerpoint to the technical team seems a bit unfair.
Seems whoever do not have problem before, most (I cannot say all) of the upgrade firmware version will continue works fine (touch wood, I am one of the lucky guy). One the other hand, whoever have problems in previous version, upgrade do not fix this problem. So...the simple conclusion draw from this is the problem is a complex combination of Windows (and installed software etc) with the firmware. It will be good if anyone currently has problem, could do a complete reinstall the windows and sharepoint, and then install the software one by one, until the problem occurred will definitely help the team to reproduce the problem. Of course, is there anyone willing to do this for the sake of the other???? What I saw so far is most of the people just scream out the symphtom and to certain degree, this give only a very little help for the team to locate the bug. It just shooting in the dark. For those user has no problem (just like me), there is nothing we could help...it just work.
Done that (and more), and nothing helps...it just don't work.
-
if shareport problem on clean windows and clean firmware, I think it should narrow down to device specific conflict....eg. A1/A2/A3/A4 router hardware or USB device specific driver (eg. the specific printer driver).
-
if shareport problem on clean windows and clean firmware, I think it should narrow down to device specific conflict....eg. A1/A2/A3/A4 router hardware or USB device specific driver (eg. the specific printer driver).
Purchased a new printer to make sure it wasn't the printer, nope def not the printer. People with A2,A3,A4 are experiencing issues... except for eddiez. Could we have more people post and confirm if they have A2,A3,A4 and shareport is fully functional for them.
-
@R3XNebular
Shareport works fine on my Rev A2 with HP Deskjet 6540 and 6840 printer.
Samsung CLP-300 is very slow with graphic prints but text pages are ok.
Big brother Samsung CLP-350 has problems after going into power safe mode.
I think the difference are the drivers and kind of printer.
Is it a windows (GDI) printer where the computer does the job and sends the complete print data or is it a printer with own memory which just receives a print job in a printing language (i.e. PCL) and has to process the printing on its own.
I could imagine there are more problems with GDI printers as the whole print is transmitted via silex virtual link. If there are interrupts, the printer may think it is the end of page and will print the rest onto a second one or it skips or prints wrong data ...
I think the next firmware and shareport tool will fix again some of the problems. The next version is already waiting on silex homepage for the new d-Link firmware ;D
http://www.silexeurope.com/en/home/support/productgroups/common-downloads/device-server-and-virtual-link.html
-
Installed the whole Silex driver and app and it works just fine ;D
-
Installed the whole Silex driver and app and it works just fine ;D
so your saying shareport now works perfectly with the new update?
-
I never had any problems. So nothing to be solved.
-
I have had no luck with the silex software either.
-
.. which was most likely caused by a driver or something with the firewall. But what the heck. There are many benefits for reinstalling an OS.
-
Installed the whole Silex driver and app and it works just fine ;D
Demonized, would you please amplify your comment? I'm very intersted to hear what you did and why.
-
Hello all, I too installed the Silex driver but to no avail. I'm still running FW 1.32 on HW Ver A4. A Router restart is the only way for me to connect.
Being that so many people are having so many problems with these new firmware releases, why won't Dlink allow us the capabilities to revert back to the previous versions when the shareport did work (ver 1.21). That should resolve some or most of our problems at least until they have solid working Ver. I mean really its only software they can make it happen!
-
Demonized, would you please amplify your comment? I'm very intersted to hear what you did and why.
I installed the newer ánd the previous version next to Shareport to see if there were any other modifications besides the skins. Both versions worked fine and only differ in the skins provided. It means the application is taken 'as-is' from Silex. This also makes a conclusion that possible issues need to be addressed in the firmware.
I installed the newest version to see if there have been any changes to the connection method, but since I don't have any issues I am not able to judge this properly.
-
I installed the newer ánd the previous version next to Shareport to see if there were any other modifications besides the skins. Both versions worked fine and only differ in the skins provided. It means the application is taken 'as-is' from Silex. This also makes a conclusion that possible issues need to be addressed in the firmware.
I installed the newest version to see if there have been any changes to the connection method, but since I don't have any issues I am not able to judge this properly.
You're on the the very few and fortunate ones Demonized
-
It seems so. But don't forget people come to a forum to solve an issue. Those who have no issue will not complain on a forum. part of those will perhaps also have an issue but don't want to spend time on it and just leave it like that. But I think there's a great majority that has no issues (an assumption, I know). Otherwise there would have been very harsh and destructive reports everywhere on (semi-)professional sites...
-
It seems so. But don't forget people come to a forum to solve an issue. Those who have no issue will not complain on a forum. part of those will perhaps also have an issue but don't want to spend time on it and just leave it like that. But I think there's a great majority that has no issues (an assumption, I know). Otherwise there would have been very harsh and destructive reports everywhere on (semi-)professional sites...
Yes you're right there may be others having these issue and some that just don't know where to turn after speaking to a "product specialist" at Dlink. And some may just circumvent the shareport problem by just not using it altogether, however, if Dlink doesn't fix this problem soon I think we will start seeing those harsh destructive reports sooner than later. There are enough angry people here to make a stink.
-
Hmmm, capable maybe but justified that's another matter...There is truly no product that has no issues.
These issues are not generic in their nature. If they were there might be some justification, but my view is that the issues are not generic.
-
Hmmm, capable maybe but justified that's another matter...There is truly no product that has no issues.
These issues are not generic in their nature. If they were there might be some justification, but my view is that the issues are not generic.
I agree. I suppose at this point we just hope for the best!
-
Google is full of web sites with people reporting delayed write failures on networked USB drives. Not only networked but also connected directly to the computer. After seeing all of this I became much less suspicious of Shareport as the root of my problem. Although, the silex component might not play nice with my drive. I finally found ONE web site run by a guy that knows what he's doing. He solved his problem by writing his own lower limit driver for his drive enclosure. Bottom line for me is I really don't know where the problem lies. I'm going to try everything I can to find a Windows fix or a drive enclosure fix since there is nothing I can do about Shareport but wait and read the forums for news. Sometimes one of you guys will say something to give me another idea. I'm not giving up on Shareport unless D-Link yanks it. I can live without it but trying to get all of this to work has become my Matterhorn.
-
As I posted in the Firmware update threads, I had the shareport detection, then connection , then printing one page on multiple page problems. I also had the router do a soft reset after or in the middle of multi-page print jobs. Flashed the 1.32 Beta and started using the silex driver and the smaller print jobs now print correctly, but I was still experiencing problems with the router soft resets.
I had a QoS entry for my Vonage device and after I removed it, the large print jobs no longer cause the router reset though they still don't print correctly.
-
This morning I uninstalled Shareport and installed the Silex Virtual...thingy (I forgot the full name). It's probably already been mentioned but the driver that was extracted is a newer version. Upon executing it, I saw the double drive entries again except this time it connected. That was a first. So I rebooted the router and doing so took care of the double entries. Then I rebooted my PC and after it came up, the Silex Virtual...thingy connected to the drive without a hitch. That might be a first. So, I'm thinking I'm batting .666, I'll go for 1.000. I run my drive imagae program. It's blasting along writing 2MBps. It copied around 2G before it choked. I'm leaning more and more towards my drive housing which uses a Prolific chip. According to what I've read, Windows will see the drive and somehow think "OK, you can handle this much data at a time". The Prolific chip, on the other hand says "No I can't". Windows says "Yes you can and I'll prove it". Prolific days "Fine go ahead. Watch what happens when you do". This was a simplified explanation I read and the bottom line is that there is no gate keeper to tell Windows to only send so much at a time or else you are going to cause an overflow and then the whole process breaks down. Adding a lower limit driver to my hard drive will throttle that flow down to something the Prolific chip can handle. Unfortunately, I don't know where to find such a driver. There is one for a USB/Firewire Prolific chip. I'm thinking about playing with fire and install it just to see what happens. Now, could this also be what is happening to the other devices that are having problems? Can you install a lower limit driver on a printer? Just my 2 cents.
-
Anyone tried the new firmware? don't want to take the dive and have more things go wrong.
-
Anyone tried the new firmware? don't want to take the dive and have more things go wrong.
I will at some time today. I'll report back, unless of course it causes my router to burst into flames. ::)
-
This exact same issue occurs on the DIR-628 (A3) running the latest firmware beta (v1.20NAb07Beta01), running shareport v1.1 on a Vista SP2 x86 & Windows 7 RC x86 machines.
Using an Epson RX-620 MFP device - says "checking status" and goes back to "available" - once the router is rebooted, works fine for a while, then starts having the hiccups again - rinse & repeat.
I'm actually surprised that no one has posted anything here about it... maybe because it's the DIR-655 subforum, i guess?
-
This exact same issue occurs on the DIR-628 (A3) running the latest firmware beta (v1.20NAb07Beta01), running shareport v1.1 on a Vista SP2 x86 & Windows 7 RC x86 machines.
Using an Epson RX-620 MFP device - says "checking status" and goes back to "available" - once the router is rebooted, works fine for a while, then starts having the hiccups again - rinse & repeat.
I'm actually surprised that no one has posted anything here about it... maybe because it's the DIR-655 subforum, i guess?
Thanks just confirms it's firmware or shareport related.
-
I flashed the latest Beta and I'm sorry to report that the on again, off again Shareport connection is as quirky as ever. I am able to reconnect much more often after replacing D-Links Connect with Silex's Connect but, WOW, it will connect and 5 seconds later - disconnect. Then it will repeat this dance over and over.
-
I flashed the latest Beta and I'm sorry to report that the on again, off again Shareport connection is as quirky as ever. I am able to reconnect much more often after replacing D-Links Connect with Silex's Connect but, WOW, it will connect and 5 seconds later - disconnect. Then it will repeat this dance over and over.
I can confirm that, took the leap onto the new Firmware 1.32.b2. Can the tech's tell us if they've got any idea how to fix it or if they are able to reproduce the issue? Me and many hundreds of anonymous viewers (judging by the views) are becoming impatient.
-
Hundreds of views are probably generated by ten people who frequently have a look at the same post with an updated contribution. Wishful thinking...
-
Hundreds of views are probably generated by ten people who frequently have a look at the same post with an updated contribution. Wishful thinking...
Who would do that? :P
-
There's a 20 people hardcore group ..... ;)
-
I've forwarded this thread to the PM for the product. I'm trying to get him to see if they are able to reproduce the failure, as we are not able to here.
I await his response.
-
I tried the new Silex utility and it worked only once with my HP Photosmart A716. I installed Silex on one desktop PC, and I printed out a picture just fine. Then I installed it on a laptop and the issues came back, to both computers. Looking at this I think there must be some kind of a sharing issue in the software, or firmware. Most likely the router does something that messes with the software (both Shareport and Silex) when it sees more than one computer...
My specs:
OS: Windows 7 RC (with all updates)
Router: DIR 655 1.32 (beta) A3
Software: tried both shareport 1.10 and Silex 3.2.3
-
The problem happens whether there are multiple computers printing or not. I have a single PC with a wired connection attached to the router and it is the only one with the Shareport/Silex client. My other devices are a Wii and an occasional notebook, no printing from either.
-
We might have something here guys. I'm going to uninstall on all 3 of my machines, then reinstall it on only one of them. I'll write back with my findings!
-
Along these same lines of thought, all of my experiences with Shareport have been wirelessly. I have a Ethenet over Powerline switch next to my Laptop so I'm going to hook up to it and see if get a bit, or a lot more stability with "Connect". If not, I guess I'll have to hook up directly to the router and see what happens. If you D-Link guys are reading this, in your test evaluations are you performing them with a wireless or wired (or both) connection?
-
Well guys my test did not work, I uninstalled shareport on all 3 machines and reinstalled on only one to see if by any chance having multiple sessions of the shareport running was causing a conflict but that that didn't do it.
Clancy, one of my machines is wired into the router and unfortunately that also doesn't work.
-
Clancy, one of my machines is wired into the router and unfortunately that also doesn't work.
You sunk my battleship. :'(
-
You sunk my battleship. :'(
sorry ;D
-
I could have saved you the trouble croket. See my post just prior to your brainstorm
-
I've forwarded this thread to the PM for the product. I'm trying to get him to see if they are able to reproduce the failure, as we are not able to here.
I await his response.
What is the status? who is the PM?
-
What is the status? who is the PM?
If you want to control the process you'd better apply for a job. Don't go pushing after less than 4 days after the mod's message. In normal life this kind of remark/question is considered quite rude.
But that's just my personal opinion.
-
If you want to control the process you'd better apply for a job. Don't go pushing after less than 4 days after the mod's message. In normal life this kind of remark/question is considered quite rude.
But that's just my personal opinion.
Did at any point I suggest I wanted to control the process? NO. Pushing? Its been over a month where I have pointed out this issue and he suddenly forwards it to a PM (whatever that is). He should of done that alot earlier when he couldnt reproduce the issue. If you are trying to suck up to the techs you're doing a good job, maybe they'll find a good place for you to lick their arses?
What is rude is that this issue is still present and that all they can say is we can't reproduce this issue.
-
Is there a SLA with 'the user' somewhere that I've missed? Reality is sometimes hard to accept.
And yes, you actually do suggest by asking these questions that you want to control the situation. What's the use of getting the PM's name? Do you want to send him a birthday card or ask him out? This is a form of "I want to speak to the manager" if things don't go your way. Well you can. It should not be too hard to find out who D-link's CEO is. You'd better go straight to the top instead ;)
-
Is there a SLA with 'the user' somewhere that I've missed? Reality is sometimes hard to accept.
And yes, you actually do suggest by asking these questions that you want to control the situation. What's the use of getting the PM's name? Do you want to send him a birthday card or ask him out? This is a form of "I want to speak to the manager" if things don't go your way. Well you can. It should not be too hard to find out who D-link's CEO is. You'd better go straight to the top instead ;)
Asking if theirs a response implies I want to control the situation? what are you twelve? lol cause that is not my intention. How do I know? oh cause I'm me :)
I am curious to see if the PM is on this board because yes I am a unhappy customer and I have every right to be ::) Looks like you're abit of a troll doesn't it. Go be a hero in another thread ;D
-
Asking if theirs a response implies I want to control the situation? what are you twelve? lol cause that is not my intention. How do I know? oh cause I'm me :)
I am curious to see if the PM is on this board because yes I am a unhappy customer and I have every right to be ::) Looks like you're abit of a troll doesn't it. Go be a hero in another thread ;D
Did you hear me complain about your 'status' part?
Work on you manners and you might even become somebody in this world. And good luck with that!
-
Did you hear me complain about your 'status' part?
Work on you manners and you might even become somebody in this world. And good luck with that!
Yes you said "This is a form of "I want to speak to the manager" if things don't go your way"
Manners? You deserve none, firstly I asked two straight forward questions and secondly you are rude
"Don't go pushing after less than 4 days after the mod's message, In normal life this kind of remark/question is considered quite rude."
Hate to tell you this but this is the INTERNET, did you want me to write a type of letter or something such as
Dear Lycan
It has come to my concern that you have failed to address the issue with shareport, you have stated you have forwarded this issue to a PM. May I kindly ask if you have received a response.
Get real...
-
Good to see you do know how to be polite and forthcoming. I bet you'll get a response on that one. On the original post....haven't seen one yet. I wonder why....
-
Good to see you do know how to be polite and forthcoming. I bet you'll get a response on that one. On the original post....haven't seen one yet. I wonder why....
Lycan last.... active June 19, 2009
My post... June 19, 2009
enough said.
-
enough said.
Couldn't agree more.
-
Lets see if I can set everyone straight.
1) There are A LOT of threads here, and 2 Mods for home class devices.
2) If I didn't respond, it's because I was busy doing something else.
3) PM = Product Management. I didn't forward it sooner because we CAN'T reproduce your failure, so what am I supposed to show him? A working router?
4) This is a D-Link hosted forum, NO MOD/ADMIN will EVER give out personal contact information here. I mean we use handles in our posts.....comon.
Now, we are forwarding the threads in this forum that appear to have legitmate claims to see if we can narrow down and isolate the given issue. I'm told there should be some firmware forth coming and it should address some if not all of these issues.
-
Lets see if I can set everyone straight.
1) There are A LOT of threads here, and 2 Mods for home class devices.
2) If I didn't respond, it's because I was busy doing something else.
3) PM = Product Management. I didn't forward it sooner because we CAN'T reproduce your failure, so what am I supposed to show him? A working router?
4) This is a D-Link hosted forum, NO MOD/ADMIN will EVER give out personal contact information here. I mean we use handles in our posts.....comon.
Now, we are forwarding the threads in this forum that appear to have legitmate claims to see if we can narrow down and isolate the given issue. I'm told there should be some firmware forth coming and it should address some if not all of these issues.
1) Can understand that.
2) Can also understand that.
3) So you are saying you've been able to reproduce the issue now?
4) Don't think anyone asked for his personal contact info eventhough my statement may of implied it, but I can understand the privacy issue.
Your last statement is very vague, you are told some issues will be addressed that I'm hoping to be the major ones such as the freezing router (6000 views, 258 replies) and this shareport issue (6400 views, 300 replies)
-
Lets see if I can set everyone straight.
1) There are A LOT of threads here, and 2 Mods for home class devices.
2) If I didn't respond, it's because I was busy doing something else.
3) PM = Product Management. I didn't forward it sooner because we CAN'T reproduce your failure, so what am I supposed to show him? A working router?
4) This is a D-Link hosted forum, NO MOD/ADMIN will EVER give out personal contact information here. I mean we use handles in our posts.....comon.
Now, we are forwarding the threads in this forum that appear to have legitmate claims to see if we can narrow down and isolate the given issue. I'm told there should be some firmware forth coming and it should address some if not all of these issues.
Cool...fresh firmware coming for the testing. :o
-
4) Don't think anyone asked for his personal contact info eventhough my statement may of implied it, but I can understand the privacy issue.
"Implying" is really an understatement when looking at "who is the PM?-"
Your last statement is very vague, you are told some issues will be addressed that I'm hoping to be the major ones such as the freezing router (6000 views, 258 replies) and this shareport issue (6400 views, 300 replies)
No of views/replies does not vouch for the qualification 'major' of the issue. 'Most interesting' would be the most applicable qualification. ;)
Looking forward to the new firmware (although nothing's really broken here)
-
Looking forward to the new firmware (although nothing's really broken here)
Yep, running stable - boring !
But perhaps the next firmware will change this ;D
-
Yep, running stable - boring !
But perhaps the next firmware will change this ;D
LOL ;D
-
Lets see if I can set everyone straight.
1) There are A LOT of threads here, and 2 Mods for home class devices.
2) If I didn't respond, it's because I was busy doing something else.
3) PM = Product Management. I didn't forward it sooner because we CAN'T reproduce your failure, so what am I supposed to show him? A working router?
4) This is a D-Link hosted forum, NO MOD/ADMIN will EVER give out personal contact information here. I mean we use handles in our posts.....comon.
Now, we are forwarding the threads in this forum that appear to have legitmate claims to see if we can narrow down and isolate the given issue. I'm told there should be some firmware forth coming and it should address some if not all of these issues.
Thank you. We will wait.
-
No, we're still unable to reproduce the failures that you guys are seeing. However based on the sheer volume of people complaining and the popularity of this thread I decided that the PM should take a look again.
To be honest there should be some firmware releases for the 655 and the 4500 around the same time. Hopefully sometime this week, but please don't quote me. I have 0 control of owhen I get my hands on it.
-
No, we're still unable to reproduce the failures that you guys are seeing. However based on the sheer volume of people complaining and the popularity of this thread I decided that the PM should take a look again.
To be honest there should be some firmware releases for the 655 and the 4500 around the same time. Hopefully sometime this week, but please don't quote me. I have 0 control of owhen I get my hands on it.
Lycan
The recent posts in the "freezing Router" thread by Fatman & myself could help explain the unexplained failures.
I can see how it would be hard to reproduce random failures.
You thoughts?
-
DIR-655, Hardware Version A4, Firmware Version 1.31NA, Shareport v1.10.
PC1, D-Link DWA-552 Extreme "N" Wireless PCI Adapter, Windows XP Pro sp3
PC2, D-Link DWA-542 RangeBooster "N" Wireless PCI Adapter, Windows XP Pro sp3
PC3, Onboard Realtek Wired NIC, Windows XP sp3
Printer Brother HL-1230 series laser printer connected by printer to USB port adapter cable.
All three PC do the same thing after a couple of hours.
Auto connect doesn't work and if I try it manually it goes you are connected then goes back to being available one sec after. If I reboot the PC it doesn't even connect at all I immediately get a pop up error connecting window. If I reboot the router it works fine for a while but eventually I can't connect again.
I have since un-installed the Shareport utility but now I have another problem. Previously I was using a DI-704P as the print server for the laser printer. It's DHCP server is disabled and its connection LAN to LAN to the DIR-655. It worked fine on all PCs but now it doesn't. I installed the print server software, set the port up and printed a test page OK from all PCs. Now after a couple of hours I can't print to the printer. Nothing happens, it doesn't power up. If I double click the printer icon it shows the print job but the status column in blank. Rebooting the PC and both routers won't fix it. I have to delete the printer and re-install it only to have it not work again latter on. >:( Shareport has done something to windows that is not un-done when you un-install it. I thinkI amgoing to try a system restore on one of the PC's if I can remember when I installed Shareport.
-
DIR-655, Hardware Version A3, Firmware Version 1.32B02NA (tried 1.31 first), Shareport v1.10.
I gave up with this combination, printer would never connect automatically on Windows startup. It worked perfectly before with FW 1.21 and Shareport 1.14.
Bought another DIR-655 with 1.10 FW, updated it to 1.21. Now Shareport works correctly with original Shareport 1.14. I have instructed my wife to shoot me if I ever try to update the FW of this router again.
-
Believe it or not, but the DIR655 USB printer feature is not a print server. So comparing those is not applicable here.
A lot of printer issue are either printer driver related or TCPIP on the OS related. Installing printer driver after Shareport has been installed solved a lot of printer related issues...
-
Believe it or not, but the DIR655 USB printer feature is not a print server. So comparing those is not applicable here.
A lot of printer issue are either printer driver related or TCPIP on the OS related. Installing printer driver after Shareport has been installed solved a lot of printer related issues...
Hello Demonized
I've been watching this post closely and have tried many of the suggestions users have offered but to no avail.
I have the A4 ver 655 with the latest beta firmware. I have 3 wireless xp machines and 1 wired, and none of them connect to the router unless the router is rebooted, same issue most here are having. I've also reinstalled the print driver as you suggest but still no luck.
just thought I'll drop in and let you know that reinstalling the print drives does not work. I'll keeping checking back for any new possible solutions.
take care
-
Is there anyone who has any progress on this shareport issue?
-
Nope even 1.32 final still has issues. It stays connected for a few seconds then goes back to appearing as "available".
-
Same here. Final 1.32 has not solved the problem. Still requiring a router restart in order to prints from any of my 4 machines.
-
Because we are no longer discussing 1.31 and are now dealing with 1.32 I'm going to lock this thread. Please refer to the new thread here.
http://forums.dlink.com/index.php?topic=6788.0