D-Link Forums

Software => Shareport - Windows => Topic started by: tfkrato on December 26, 2009, 09:40:40 PM

Title: Another Shareport DIR 655 Victim
Post by: tfkrato on December 26, 2009, 09:40:40 PM
Running DIR-655 HW A4 and FW 1.32NA, and Shareport 1.1.0 R1.  Having similar problem others have reported - printer gets acquired, no print starts, and then Shareport goes into a loop of trying to acquire the printer. 

I've gotten this working perfectly a few times now with one hardwired Vista PC, and two wireless Win 7 PCs, and an Epson RX500 printer.  Then it will fail after varying periods of time.

Found now I can get it working by changing USB setting in router to WCN, rebooting, changing back to Shareport, and rebooting again.  Works fine until the next failure.  Nexttime I'll try just rebooting the router.

Any other ideas out there on a permanent fix?  May have to return this router and go another direction without a fix soon.
Title: Re: Another Shareport DIR 655 Victim
Post by: tfkrato on December 27, 2009, 07:21:21 AM
As noted above I tried printing again this morning from the Vista and one of the Win 7 PCs and it works flawlessly.  I expect it will begin to fail sometime later in the day.

In the hopes someone is monitoring this forum and passing information onto the D-Link developers, I wanted to pass on another observation.

When this fails I observed the "Enable auto connect" option in the Shareport utility Optional setting became unchecked and the "Auto Printer Connect can be used" lost the green check.  When I checked the "Enable auto connect" and clicked on Connect I got the message about insytalling drivers and the "Cancel" light - the process never completes with Cancel changing to OK like it does when this works.  I had to stop the Shareport untility because clicking Cancel does nothing.

Then, when I did the USB change / reboot sequence in my posting above I go back to the same PC, open the Shareport Utility, look at the Optional setting tab and everything is back to normal with "Enable auto connect" checked and the "Auto Printer Connect can be used" checked green.  Everything works until next failure.
Title: Re: Another Shareport DIR 655 Victim
Post by: tfkrato on December 28, 2009, 11:43:01 AM
All was working fine again for about a day.  Tried to print and it appeared to work, but as I was going to check the printer I noticed Shareport trying to acquire the printer again.  Found under Shareport Optional setting "Enable auto connect" was still checked, but "Auto Printer can be used" was yellow, not checked green.    Tried to change "Auto Printer can be used" but it failed with usual message about installing drivers.

This time I only rebooted the router.  Went back into Shareport on the same PC and was able to successfully enable "Auto Printer can be used".  Everything is now working fine again from all 3 PCs.

So, at least I can get this working with a simple router reboot but obviously this is not the solution.  Need D-Link to come up with a fix.
Title: Re: Another Shareport DIR 655 Victim
Post by: tfkrato on December 30, 2009, 08:22:12 AM
When print failed this last time I just cancelled the print job, stopped Shareport Utility to get it to stop trying to reconnect to the printer, rebooted the router, restarted Shareport, then reran the print.  Everything working fine again - until the next failure.

Wish D-Link would at least post a status update and prognosis.
Title: Re: Another Shareport DIR 655 Victim
Post by: satcomranger on December 30, 2009, 11:59:15 AM
I am right there with you  ..  when they first came with the latest shareport release I provided feedback on it .. and right now it appears to have just fallen by the wayside.... i for one would like to see a new shareport AND firmware  that honestly works  ..  all the reset ... reloads reflashes  .. reconfig ...etc  ...etc...has helped my shareport OR router work for more than 2 days without bombing out in some way or another ..
Title: Re: Another Shareport DIR 655 Victim
Post by: Ozzed5 on January 01, 2010, 01:13:41 PM
If anyone figures out an answer to this question, please post.
Title: Re: Another Shareport DIR 655 Victim
Post by: tfkrato on January 19, 2010, 06:09:57 PM
Figured I had nothing to loose so I uninstalled Shareport from my Vista desktop and 2 W7 laptops and replaced it with Silex SX Virtual Link v.3.4.0.  Worked fine for a couple days then had to reboot the router to get it working, just like with Shareport.  So, with Virtual Link I have to reboot the router every 2-3 days and with Shareport I had to reboot after less than a day.

I was hoping SX Virtual Link solved my problem after working for about 3 days initially without a reboot, but then the identical failure occurred.

Wonder if D-Link is even working this issue?  Why the hell does this work perfectly then suddenly fail to work?  It works perfect, then all PCs are put to sleep or turned off, then one PC is brought up and it work perfect again, then turn PC back off, then turn one on the next day and BOOM - same failure and the router must be rebooted - the everything starts working perfectly again after the reboot. 

Does D-Link or anybody have a suggestion?
Title: Re: Another Shareport DIR 655 Victim
Post by: PeaveyAxe on January 24, 2010, 07:02:40 PM
MY GOD, someone must have been able to figure this out by now!!  I too, along with thousands of other people, have been suffering with this problem. D-LINK, where the hell are you??  You haven't released a new version of firmware or shareport for over 6 months (betas don't count).  Hurry up and fix this mess.
Title: Re: Another Shareport DIR 655 Victim
Post by: #John on January 28, 2010, 02:40:50 AM
Sigh. I too am a victim. I also tried Silex SX, but with the same results. I've had to resort to plugging my shared resources (printer, backup drive) into one of my computers and just leaving it on all the time.
regards
#John
Title: Re: Another Shareport DIR 655 Victim
Post by: Tyrone Biggums on January 28, 2010, 04:07:34 PM
From My experience I disable the auto-connect for the device because I think it will auto connect regardless. Doesn't make sense but it works.
Title: Re: Another Shareport DIR 655 Victim
Post by: Sek on February 03, 2010, 11:40:14 PM
heh, I just replied in another thread about this same issue, and I am glad to find that others are having this issue with their 655.  Well, not glad its a problem, just that its not isolated to myself and a few others.

Earlier tonight, I went to the DIR-655 product page, and found that 1.33NA firmware is now released and available.  I just upgraded about an hour ago, and will observe this issue overnight.

Maybe if enough of us get to making noise, D-Link will take a look, because this bug renders the Shareport feature as useless, and its a problem in their firmware for the 655, not the utility or our OS's.
Title: Re: Another Shareport DIR 655 Victim
Post by: tvorgitch on February 04, 2010, 07:06:49 AM
I'm eager to hear your results, but this doesn't look promising:


Firmware: 1.33NA
Date: 01/28/10

1. Fixed:  Correct HNAP issue.
2. Fixed:  DNS relay issue ( WAN Slowdown )
3. Added:  Advanced DNS descriptions
Title: Re: Another Shareport DIR 655 Victim
Post by: rick0325 on February 04, 2010, 09:31:55 PM
This worked for me

DIR-655 Router with 1.33NA firmware  SharePort 1.1.0r1 Software

Windows 7 64 bit

Login to your router (type 192.168.0.1 in a web browser)

Go to Setup Tab, click USB Settings in left pane
Make sure USB Type is set to Shareport (if not set it and save)

Go to Advanced Tab, click Advanced Network in left pane
Go to bottom and make sure Enable Multicast Stream is checked (if not check and save)
If you had to change it will ask you to reboot, go ahead and let it reboot

Now in windows, click Start, Control Panel, System Security, Windows Firewall
Click Advanced Settings in Left pane
Click Inbound Rules in left pane
There will be 3 rules you need to change
2 are both called SharePort Utility and the 3rd is SXUPTP
Highlight the inbound rule and click properties
Click the Advanced Tab and make sure both public and private boxes are checked
Hit apply and ok
Do this for all 3 rules listed above

Open the SharePort Utility software
Click on the options button (looks like a wrench)
Click on Search for Device Servers Tab
Check the box by Enable Broadcast Addresses
Type 192.168.0.255 and hit add
Hit apply and OK

That should do it, good luck
Title: Re: Another Shareport DIR 655 Victim
Post by: PeaveyAxe on February 06, 2010, 01:16:54 PM
Where can I download Shareport utility 1.1.0r1?
Title: Re: Another Shareport DIR 655 Victim
Post by: PeaveyAxe on February 06, 2010, 01:22:58 PM
Never mind, I found out that's the latest one on the main site.
Title: Re: Another Shareport DIR 655 Victim
Post by: tvorgitch on February 06, 2010, 06:08:25 PM
I've had 1.33NA running for about 24 hours and so far, so good. I'm able to connect to from two different XP systems.
Title: Re: Another Shareport DIR 655 Victim
Post by: momcat1 on February 14, 2010, 02:05:40 PM
You've got to be kidding! I went through the firmware update to 1.33NA, a few bobbles in that process, but it's done, and everything is set back where I had it.

Then I tackled the Shareport upgrade. First problem, I installed 1.15 from this forum, which absolutely did not work. Went to dlink site and got 1.10, OK, since when is going from 1.14 to 1.10 and upgrade? Installed that. Magically it did recognize my Kodak printer. That's very good considering all I went through with 1.14. OK, I connected to it. That was real good too. I sent a test page to the printer, that's where the trouble started. As soon as I sent a test page to print, the router hung. So then I got the printer disconnected improperly popup. Five minutes later we finally got the router back. Yeah, five minutes. I tried a second time. Same thing. I installed Shareport 1.10 on a second PC, same scenario.

So the bottom line is, we can connect to the printer just fine, but we can't use the connection. This is progress? I did check to make sure Shareport was the USB connection on the router, when I could finally get back into it, and it is. I did also check the Windows Firewall ports even though the installation took care of the exceptions. They are just fine.

I'm not getting what exactly is freezing up the router.

Windows XP SP3 laptop and Windows Media Center desktop.
Title: Re: Another Shareport DIR 655 Victim
Post by: momcat1 on February 17, 2010, 05:37:07 PM
So I tried twice more to uninstall/reinstall Shareport, and while it sees the Kodak printer just fine, it will not connect. I then tried my USB external hard drive and the same thing happened. It's not Windows Firewall, that's setup as it should be, with the correct exclusions.

I'm done with Shareport. My next printer will be wifi on my network.
Title: Re: Another Shareport DIR 655 Victim
Post by: Pluripotent on February 21, 2010, 07:28:40 AM
rick0325,

I did what you said on my DIR-855 and so far, it worked.  I just completely disabled windows firewall.  I don't see much point in running a software firewall on top of the router firewall.  Some people having problems on these threads are running additional (known problematic) firewalls on top of windows firewall and their router firewall!  That's just asking for trouble.

Just curious if you could explain how you came about these settings, such as "Enable Broadcast Addresses
192.168.0.255" 
Title: Re: Another Shareport DIR 655 Victim
Post by: efalsken on February 24, 2010, 09:55:14 AM
If anyone figures out an answer to this question, please post.

On my DIR-628, my computer regularly cannot connect to my printer. Restarting SharePort and my computer has no effect. Even reinstalling SharePort. But I have found that restarting the router works 100% of the time (for me).

My printer is selected as "Connect automatically when needed" and the icon is green (means the drivers are installed correctly to detect items in the print queue).
Title: Re: Another Shareport DIR 655 Victim
Post by: purple_python_2 on February 28, 2010, 10:09:19 PM
Same problem here.    FW 1.32NA, SharePort 1.1.0.R1 with Enable Broadcast Address setting on SharePort, and clock sync'ed and Enable Multicast streams (as suggested by different people).

After rebooting the router, SharePort will see the USB device.    And it will connect without any problem.
But then the next day, observed two scenarios so far:
1) Cannot see the device any more, after I power on my USB Printer.    Then has to "toggle" the "Enable Broadcast Address".    Then it will show up.
2) Sometimes, it can see the device, but cannot connect.     I then "toggle" the "SAVE SETTINGS" for time on the router.     That does not require a reboot.    And then I can connect.     Two more times, I've experienced this scenario.   Toggling "SAVE SETTINGS" does NOT help at all.      So, this whole deal about time server in another posting is just a coincidence rather than correlation.  (3/1/10)

I will try couple more times to confirm those "toggling" actually consistent helps.    Maybe those togglings somehow trick the router and SharePort utility to go through some routine OR clear out some stale data on the router side or client side.      The unpredictability of whether SharePort will work today or not is just plain annoying.     I really don't want to unnecessarily reboot my router everyday!!!
Title: Re: Another Shareport DIR 655 Victim
Post by: htpw16 on March 05, 2010, 05:07:51 PM
Has there been a solution to this problem? I have been experiencing the same behavior where a router reboot fixes everything.
Title: Re: Another Shareport DIR 655 Victim
Post by: purple_python_2 on March 06, 2010, 10:10:54 AM
This is VERY DEPRESSING.     I tried the NEW SharePort 3.0.    Yes, when it first power up, no problem.    The problem, similar to the previous SharePort, occurs when the router has been up for a while.    Then, SharePort would no longer talk to the router.     I kept my router up for a few days.     This morning, I tried SharePort and it can no longer see my router any more.    And I had to reboot the router.     This router is behaving like Windows 95 (I promise you, this is NOT a praise!!!) that I have to reboot regularly.     

The software department of D-Link is VERY incompetent.    By now, there MUST be plenty of test cases that the software department can trace and reproduce this problem.    Should ALL the angry D-Link customers start posting nasty comments on Amazon.com, Buy.com, etc.. to get some attention from D-Link to fix this properly?!?!?!
Title: Re: Another Shareport DIR 655 Victim
Post by: sesca on March 08, 2010, 09:41:23 AM
I will work on reproducing the troubles you are seeing and reporting it.

I am going to lock this thread but for other users that are having trouble with SharePort 3.0 post them in the link below so that I can track them more easily.
http://forums.dlink.com/index.php?topic=11778.0 (http://forums.dlink.com/index.php?topic=11778.0)