D-Link Forums

The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Europe DIR-655 => Topic started by: Loek Rots on January 08, 2009, 12:54:26 AM

Title: Shareport problems with Printer beiing interrupted
Post by: Loek Rots on January 08, 2009, 12:54:26 AM
So I have another problem with the shareport function which I use to connect an usb printer (canon pixma). On both pc's (vista and xp) the icon in the system tray is green and they are able to connect. The problem is that when printing a document the print window of the printer gives me a connection error. It tells me to deselect the 'print interupt' (don't know the correct words since I have a dutch OS) in the printer jobs window. Indeed that option is marked in the print window and the details of the printer say it is interrupted. But I cannot deselect the print interupt thing since it is greyed out!

What to do?
Title: Re: Shareport problems with Printer beiing interrupted
Post by: Loek Rots on January 08, 2009, 01:09:55 AM
Okay I have checked some more and it has definitly to do something with the fast user switching (http://forums.dlink.com/index.php?topic=3554.0).. I can change the interrupt setting on the other account on the laptop but it will flip back automaticly... argh!

I have managed to fix it by deleting the printer on the vista laptop. I connected the printer directly to the laptop, installed the drivers, and connected the printer back to the router. I hope this will last.. if not, I'll post here.
Title: Re: Shareport problems with Printer beiing interrupted
Post by: EddieZ on January 08, 2009, 10:17:24 AM
Told you that Fast User switching causes a lot of problems...
Title: Re: Shareport problems with Printer beiing interrupted
Post by: Loek Rots on January 11, 2009, 07:52:52 AM
yes indeed, you did...

though I think this feature is used by many so I would advise dlink to fix the problems..
Title: Re: Shareport problems with Printer beiing interrupted
Post by: EddieZ on January 11, 2009, 01:19:49 PM
Let's see if one of the techs can axplain why this is not that easy (as I suspect with my basic knowledge of the Windows driver system).