Print

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

[valleyboy221]

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!

[faragondk]

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.

[EddieZ]

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.

[faragondk]

"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

[EddieZ]

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.

[Xinot]

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?

[faragondk]

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.

[EddieZ]

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.

[Alexx]

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.

[mclearn]

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.

[EddieZ]

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.

[valleyboy221]

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

[Alexx]

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.

[EddieZ]

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...

[Xinot]

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?