• November 01, 2024, 03:37:36 AM
  • 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: DIR 655 Printer worked... then stopped.  (Read 4430 times)

adamz

  • Level 1 Member
  • *
  • Posts: 3
DIR 655 Printer worked... then stopped.
« on: January 16, 2010, 01:19:06 PM »

Hi all,

I was enlisted to set up a friend's router and everything went swimmingly, Shareport functionality included, until the next day.  When I left, Shareport was working on two laptops; both could print wirelessly on the attached Samsung ML 1710 printer.  The next morning it ceased to function.

I came over a few days later and noticed a few quirks.  Shareport recognized the printer as active and available even when unplugged, the program could not find the installed driver and when I plugged in a USB drive it was not recognized.  

I believe that the firmware on the router is 1.21 (but I am not 100% sure).  All computers involved are running Windows 7 and I checked the printer - it's working fine with a direct connection.

Any thoughts? I suppose 10 hours of functionality is better than nothing, but my friend was so excited about this feature, I'd love to get it working again.  I am tempted to go to 1.32, but I am not convinced it will help.

Thanks!
Logged

tfkrato

  • Level 1 Member
  • *
  • Posts: 9
Re: DIR 655 Printer worked... then stopped.
« Reply #1 on: January 25, 2010, 08:09:12 PM »

Join the party.  You will probaly find if you reboot the router everything will start working fine for awhile.  D-Link is not responding to posts, calls to their support are useless, and they apparently cannot figure out how to fix the problem.
Logged

adamz

  • Level 1 Member
  • *
  • Posts: 3
Re: DIR 655 Printer worked... then stopped.
« Reply #2 on: January 26, 2010, 05:13:17 AM »

Well, it's nice to know I'm not alone on this one.  I took a more thorough look at this forum after I posted; your post tfkrato and a few others convinced me it wasn't just my incompetence causing the problem. 

Here's hoping for a magic firmware update!
Logged