D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: dns323-0849a1 on February 10, 2011, 07:04:23 PM
-
My DNS-323 print server has stopped working and I can't make it go. Any help?
Timeline:
Over a year ago, I bought new DNS-323 w/ 2x 1TB drives, plugged into my home LAN, attached to old Linksys WRT54G. Firmware v1.07. Attached printer HP 3840 series to USB port and it worked OK. I occasionally had to power cycle the printer to make it responsive, but everything ultimately worked. Successful client OSs include Vista Home, XP Media Center, Vista Pro, XP Pro.
A few weeks ago, I replaced the WRT54G with DIR-655 but left everything else the same. DNS-323 print server still worked.
Then I unplugged the printer from the DNS-323 and plugged it into the DIR-655, thinking that would be cool, before I realized I would have to deal with some additional software (Shareport) so I undid that connection. The DNS-323 print server stopped working at this point.
Since then, I have
- intalled DNS-323 firmware v 1.09
- power cycled printer, DNS-323, router, all client computers, numerous times...
- uninstalled/reinstalled the printer on two clients
- confirmed the printer is still functional via direct connect to one of the client PCs.
So... a solution through the DNS-323 would be great, and preferable, but...
If someone wants to point me to SharePoint through the DIR-655 I am not thrilled but I will entertain the solution. But PLEASE tell me exactly where I can get this software. I no longer have the discs that came with the router, and all discussions I have seen so far concerning download of SharePoint tell me to go to either nonexistent pages or look at nonexistent links. Searching DLink's "support" for SharePoint is useless. This can't just be me.
-
One thing missing from your list of things done is clearing the print queue - have you tried that?
-
Yes. Add to my "done" list:
- cleared print queue using the DNS config page
- physically unplugged printer data cable from DNS, rebooted DNS, reattached printer
-
Hmm - uninstalled/reinstalled the printer on two clients - how are you doing this?
I would normally install the drivers with the printer directly attached to the client and then edit the port settings to point to the DNS-323 at \\<ip address of NAS>\lp .
If all else fails you can find the shareport utility & clients at ftp://ftp.dlink.com/Multimedia/dns323/Apps/ (http://ftp://ftp.dlink.com/Multimedia/dns323/Apps/)
-
I "unin/reinstalled" the printers in the printer control panel, thinking that would resolve any port mismatches. FWIW, Windows finds the printer on the DNS, sets it up on a Print Server port with the correct IP for the DNS ("/lp" is nowhere in the name though... should it be? I tried adding /lp to the IP addy with no luck).
Anyway I've gotten really good at restarting the spooler service, and clearing the queue both on my PC and the DNS. And I've given up on the DNS print server, for now at least.
I've installed SharePort on two PCs to give it a try. My biggest concern is how to kick another user off the printer when they are not physically present and the desktop is locked. There doesn't seem to be any way to do this, and it's will be a short time before this causes a problem. Any thoughts?
I appreciate the help.
-
Never mind my Q about kicking off other users. I found the "Enable auto connect" setting that seems to work.
This might be OT here but SharePort users should realize there is a difference between "Enable auto connect" and "Automatically connect newly discovered USB devices". Understandably, this could be confusing, not only because the verbiage is similar, but the settings are in completely different menu dialogs.
In summary, my DNS print server is still nonfunctional despite all attempts. SharePort + DIR-655 is a functional work-around. I'm not crazy about the need for yet-another-background-process (SharePort), but this is free as opposed to buying a dedicated print server.
Thanks for reading.
-
You need to create a port - if you search the forum there are threards where I've posted the exact steps required.