Print

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

[ttmcmurry]

I can reproduce a "Connection failed please try again" on two laptops:  IBM ThinkPad R50/Intel 2200BG/XP SP3 & Lenovo ThinkPad T61/Intel 4965AGN/Vista SP1. 

The full story is I have a USB hard drive attached to the 655's usb port but I only use it when I'm doing a ThinkVantage Rescue & Recovery backup.  The drive is powered off 95% of the time.  In fact, I can reboot the router and never turn on the drive (it has a physical power kill switch, not a soft-off) and still get the "connection failed" message.

Once that starts-- especially overnight-- I usually have to reboot the laptops.  I had set the launch of SharePort to manual a few (2?) weeks ago since it was so annoying.

Travis

Side note:  SharePort doesn't work if VMWare Workstation (or Server) is installed.  SharePort probably messes with the VMWare USB 2.0 driver (workstation v6+/Server v2+) and/or VMWare Bridge Protocol.

[larryc57]

I made the changes to the Windows  Vista Firewall as mentioned, though I only had one instance of Shareport in the exception list. Also unchecked the box to check for updated version. No difference, pop ups still occur, even after I exit out of the Shareport Utility. I have a Calvary USB drive connected to the 655. This problem has only cropped up in the last 2 weeks or so. It worked well prior to that. I would also mention that my Shareport Utility can not find the USB drive unless the Network settings are set to Private (Public does not work) in the Vista Network and sharing Center. I'm assuming this has to do with network "discovery" though I'm not exactly sure why. And sometimes when I reboot, or log off, and come back on Vista has changed the network settings back to "Public" (another of those Vista quirks, like the folder view issue), and then the Shareport can't find the external drive again. Once I change back to "Private" it usually works. I do have to toggle back and forth between 'enable' and 'disable' on the Shareport to make this work. Sometimes I have to exit the utility and re-start it to make it work. What I have seen too is that after these gyrations I start seeing the pop - ups, though not always. The biggest mystery is why this started seemingly out of the blue. I haven't made any major changes to my Vista 32 bit Home Premium  other than keeping current thru Windows Update.

[rsmin]

Again, as stated earlier, If i just install the shareware software without anything in the port it still is giving me the "bongs", no popups. I have to uninstall it to get the "bongs" to quit.  That bong noise is the same noise you get when you plug in or take out a USB devise. If I plug in my Deskjet 882C I get the popups.

Rusty

[EddieZ]

Again, as stated earlier, If i just install the shareware software without anything in the port it still is giving me the "bongs", no popups. I have to uninstall it to get the "bongs" to quit.  That bong noise is the same noise you get when you plug in or take out a USB devise. If I plug in my Deskjet 882C I get the popups.

Rusty

The 'bongs' are quite normal. It's just Shareport saying it cannot connect, i assume the icon also turns red. 

[Lycan]

is the computer wireless, it could be dropping the connection.

[EddieZ]

Not in my case. No log entries and other signs of disconnects.

[rsmin]

The 'bongs' are quite normal. It's just Shareport saying it cannot connect, i assume the icon also turns red. 

Yes the icon is red, but the "bongs" happen about every 10 seconds and nothing plugged in the port. This didn't happen when I first installed this program several weeks ago. No way am I going to sit there and hear this constant noise going off ever 10 secords or so. Only way to stop it is uninstall the program, which I did.

And Lycan, my desktop which is what this is happening on is not wireless.

Rusty

[kegobeer]

This recently started happening on my computers.  I have three computers with the Shareport utility - two Vista Ultimate Dell laptops (wireless) and a Vista Ultimate desktop (wired).  I have a Canon iP4000 connected to the router.  This worked perfectly until a few days ago.  My laptop didn't exhibit the behavior, but the other two computers did.

This is how I've solved the problem (so far, at least):

1. Unchecked the notify of new version box.
2. Removed the printer.
3. Installed the printer, overwriting the existing driver.
4. Rebooted.

So far the computers haven't compained about a connection error.

I don't know what caused this, but all of my computers have the new IE hotfix that was released on 19 December.  I don't recall the exact day this problem started, but it was around the 19th.  Related perhaps?

[EddieZ]

Don't think so, although getting certain Windows updates might have a side effect on the utility. Cannot rule it out but strangely enough the error has not occurred for over a week now...

[Kittyburgers]

I was wondering about this.  It started happening on my desktop (wired) and my notebook (wireless) about a month ago, I guess.  I was getting a constant Windows connect/disconnect sound.  I just exited the utility, and made sure that it doesn't automatically start when I logon.  I haven't dealt with it since, as I only used it a few times with a USB thumbdrive.

It would be nice if D-Link would re-write this utility so that it actually works.  It must have been one od the patches that caused this to happen, as it work fine since it was first released, then all of a sudden it started malfunctioning.

[rsmin]

I was wondering about this.  It started happening on my desktop (wired) and my notebook (wireless) about a month ago, I guess.  I was getting a constant Windows connect/disconnect sound.  I just exited the utility, and made sure that it doesn't automatically start when I logon.  I haven't dealt with it since, as I only used it a few times with a USB thumbdrive.

It would be nice if D-Link would re-write this utility so that it actually works.  It must have been one od the patches that caused this to happen, as it work fine since it was first released, then all of a sudden it started malfunctioning.

I agree with you. Everyone has pretty much said that this was working fine and then it just started out of the blue. I am also concerned with the speed now of my wired connections. They have all seemed to have "slowed" down since going to 1.21.

Rusty

[funchords]

I have the Dlink Dir-655, and have installed V 1.21 of the firmware and am using the SharePort feature. on my Vista home premium laptop, everything works fine. on my XP pro SP2 PC, I can access files on the hard drive I plugged in, but after the PC goes into Standbye, and wakes up again, the shareport utility does not report that any device is available- therefore I cannot mount it and use it. turning the harddrive off and on again does not make it appear. Nor does "scan all devices" in device manager. rebooting the router does not help. Exiting the shareport utility and restarting it does not result in discovering the hard drive. The only thing that works is rebooting the PC.

Dlink said it was "a Windows problem"

I am hoping that someone has worked thru this already- what changes I need to make to the PC or the shareport utility to see this drive after the PC comes out of standbye. All this works properly on my other computer- a Vista home premium.

Thanks
Well after a lot of stumbling around, I think I figured it out myself. In the properties for the ethernet card, under the power management tab, there is an option
"Allow the computer to turn off this device to save power". I disabled this option and now the Shareport devices are available after a resume from Standbye.

homer_at_charter.com
I hope this helps some users tracking this thread... -- funchords

http://www.dslreports.com/forum/r21637828-Shareport-Stalls-after-XP-PC-goes-to-Standbye

[EddieZ]

As Dlink stated, it was a Windows issue 

[rsmin]

EddieZ,

You still having problems with Shareport? I haven't re-installed mine. Waiting to see if someone at D-Link or on this forum comes up with an answer?

Rusty

[EddieZ]

Nope, hasn't occured since the last reinstall. I wonder what the Dlink guys figureed out.