Print

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

[MikeMac]

I've searched the threads and simply can't find a fix for SharePoint not working. I get the same old same old that everyone seems to get ; IP Address of my dlink doesn't appear (on the client 1.14), Red Icon, SharePoint doesn't work, etc. (And yes there is no VMWare installed)

I have three laptops running Vista Ultimate and a XP sp2 machine. Of my machines, only the XP wired workstation works. None of the three laptops work. One of the laptops was freshly re-loaded with nothing other than Symantec End Point loaded on it (even disabling it doesn't change the outcome). 

Is or will there ever be a fix for this problem? One of the reasons I bought this router was a result of this awesome feature but I am disappointed that it was released without it being a rock solid product. Should I just call support (even if they can help)? Any direction would be appreciated.

[EddieZ]

Try setting it to load manually instead of automatically with Windows. Could be that Shareport is starting up sooner then the required network connection. And check if firewall isn't blocking traffic.

[lotacus]

bah! shareport is half a failure.

Just tried the updated beta today and while I get on average 3Mb/s xfer rates (wired). For some reason shareport wants to stay bound to eth0.. bah! ermm... oh! Local area network! hah. brain fart.

So get this. I originally installed it while using the wireless. Xfer rates were nearly worse than my downstream bandwidth on the wan side. Being about 768Kb/s. I popped out the dwa-160 took the lappy over to the dir655 plugged in the ethernet and away we go, doing some wired xfer tests. Then after finishing, I popped out the cat5 and shareport refused to bind to another adapter. It said that it was waiting for a connection, while I had the wireless adapter in again, and I connected, but it would not show up in the list of drives. It shows up in device manager, but causes Windows to freeze when trying to populate the disk manager. Not until I plug the ethernet back in, does it start to work as it supposed to. Restarting the computer didn't help, disabling/enabling the adapter didn't help.

The utility just wanted to stay friends with the ethernet. That's when I gave up on the utility for the 3rd time since they've introduced it. All Dlink has to do is use SAMBA or something EASY a little 4k memory in the router, big deal. They got's room for it if they've got room for other not so used stuff in that firmware. Get rid of share port. Plain and simple. it's less productive and costs more in dollars and labour than it would to impliment something tried, tested and true.

[EddieZ]

bah! shareport is half a failure.

Just tried the updated beta today and while I get on average 3Mb/s xfer rates (wired). For some reason shareport wants to stay bound to eth0.. bah! ermm... oh! Local area network! hah. brain fart.

So get this. I originally installed it while using the wireless. Xfer rates were nearly worse than my downstream bandwidth on the wan side. Being about 768Kb/s. I popped out the dwa-160 took the lappy over to the dir655 plugged in the ethernet and away we go, doing some wired xfer tests. Then after finishing, I popped out the cat5 and shareport refused to bind to another adapter. It said that it was waiting for a connection, while I had the wireless adapter in again, and I connected, but it would not show up in the list of drives. It shows up in device manager, but causes Windows to freeze when trying to populate the disk manager. Not until I plug the ethernet back in, does it start to work as it supposed to. Restarting the computer didn't help, disabling/enabling the adapter didn't help.

The utility just wanted to stay friends with the ethernet. That's when I gave up on the utility for the 3rd time since they've introduced it. All Dlink has to do is use SAMBA or something EASY a little 4k memory in the router, big deal. They got's room for it if they've got room for other not so used stuff in that firmware. Get rid of share port. Plain and simple. it's less productive and costs more in dollars and labour than it would to impliment something tried, tested and true.

We've already talked about the SAMBA impossibilities in another thread. Recap: Since the hardware is not equiped for SAMBA, the 'software' version will be equally bad in performance. If you want that functionality, you should have bought a different router. 
 
Over here Shareport works fine, it's an nice bonus since it was added much later to the router and basically the USB connector/hardware was not designed for more features other than WPS.

We can keep complaining but that would not help anyone...

[MikeMac]

I must have missed something since none of these responses on this thread has addressed the matter (I did say I read all the threads and did everything and more to get the darn thing working). The only statement that made sense is the fact that SharePort (and yes I typo'd SharePoint) was an after thought on the USB slot on the router. In my opinion, and no I ain't beatin' a horse to death here, is that if you can't do something right don't do it at all. Thanks to all who provided their two cents!

[EddieZ]

I must have missed something since none of these responses on this thread has addressed the matter (I did say I read all the threads and did everything and more to get the darn thing working). The only statement that made sense is the fact that SharePort (and yes I typo'd SharePoint) was an after thought on the USB slot on the router. In my opinion, and no I ain't beatin' a horse to death here, is that if you can't do something right don't do it at all. Thanks to all who provided their two cents!

My bets bet is that a non-working Shareport is related to a misconfigured network connection, either caused by a 'late' startup of networking components or a VMware app interfering.

So IMHO it's definitely client side issues that cause it to malfunction, the Shareport afterthought has really nothing to do with it.