• June 30, 2022, 12:50:22 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Cannot print via SharePort  (Read 10169 times)

Guyton

  • Level 1 Member
  • *
  • Posts: 5
Cannot print via SharePort
« on: May 24, 2009, 10:14:34 AM »

Hi,

I just bought a DIR-655 and I am also having problems with SharePort and my printer.  Firstly, I love the idea of using the USB connector as a print hub, etc...  It works great with my new USB HDD, but I find that there isin't enough documentation on this nice feature.  Such as should I install the drivers that came witht the product before installing shareport or connecting the device with shareport?  also, do you need to install the drivers for the device, then plug that device into your pc and letting windows do it's plug and play magic before you plug the device into the shareport? 

When shareport sees the device and I connect to it, should windows then do it' plug and play magic?  because I don't see any balloon pop ups saying that windows found a new device...  how does windows know where to direct the data if it doesn't know where it's connected?  Also, can you use a USB hub?

Anyways, here is the problem I'm having...  I plug the HP printer into the SharePort connection on the d-link router, installed the SharePort utility on my pc, and installed the drivers for the printer on my pc.  The printer has never been physically connected to this pc.  but it doesn't seem to matter because I tried this on my other pc that has been connected to the printer and installed the drivers with it plugged in, and I'm still having problems with SharePort.

The printer shows up fine in the SharePort utility window, and says it's available.  But windows never detects it as a new device!  so how can I print to it?  I can connect to it, and it shows the green connected checkmark, but it goes away about 5-10 secs after being connected.

I tried right-clicking on the device in SharePort utility and clicking on properties, then the optional settings tab, and clicked the radio button beside Connect automatically before printing, then clicking the Configure button.  It says it's looking for drivers, but it just sits there...  the drivers are installed, HP allows you to install the drivers without having the printer connected.

Can someone please help me?

oh yeah, might be good to know...  Vista 64bit and tried Vista Home also.

Guy :) ???
« Last Edit: May 24, 2009, 10:16:11 AM by Guyton »
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494
Re: Cannot print via SharePort
« Reply #1 on: May 24, 2009, 01:25:49 PM »

Quote
The printer shows up fine in the SharePort utility window, and says it's available.  But windows never detects it as a new device!  so how can I print to it?
You already have installed the driver, so the device is not 'new' anymore...

I do not have an answer, but I 've noticed that a lot of HP printers have this issue.
Logged
DIR-655 H/W: A2 FW: 1.33

anon

  • Level 3 Member
  • ***
  • Posts: 263
Re: Cannot print via SharePort
« Reply #2 on: May 25, 2009, 01:18:13 AM »

Guyton, you are not alone with that problem...

http://forums.dlink.com/index.php?topic=5287.0

http://forums.dlink.com/index.php?topic=5467.0
Logged

Guyton

  • Level 1 Member
  • *
  • Posts: 5
Re: Cannot print via SharePort
« Reply #3 on: May 27, 2009, 04:33:53 PM »

You already have installed the driver, so the device is not 'new' anymore...

I do not have an answer, but I 've noticed that a lot of HP printers have this issue.

what I meant by windows not detecting my new device is that I don't hear the usual sound when windows detects a newly plugged usb device...  I hear it when I connect to my usb hard drive, but not my hp printer :(

as for the other posts...  I did read them, after I wrote this one...  I thought that this being a shareport issue, it would have been in this section.

I hope D-link will fix this somehow...  I'd be willing to assist anyway possible!  I wish I could go back a firmware release or two when this feature worked properly...  I'm stuck at 1.31NA :(
Logged