D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: cetoken on December 18, 2008, 08:22:36 PM

Title: Print Server - not working (after upgrade to 1.06)
Post by: cetoken on December 18, 2008, 08:22:36 PM
I just got my -323 and plugged in my HP DeskJet 1220C.  I can see it listed as "lp" under the NAS in My Network Places.  However, I cannot get it to print.

1.  Tried adding it as a Network Printer - it added, but wouldn't print.
2.  Tried adding a Local printer with new Local port named "\\192.168.1.201\lp" - got error "The network path was not found"
3.  Tried above again using "\\NameOfNAS\lp" - same result
4.  Tried adding new Local port to existing (local) printer entry with same result.

My NAS is running firmware v1.05.  Static IP address.  Connected to a LinkSys WRT54G router.  PC used is cable-connected to router, Windows XP Pro SP3.  Printer works fine when connected directly to PC.

I do not currently have a drive installed in the NAS (waiting patiently for that darn UPS truck).  I do not expect it to make much difference when I do.

My printer is a plain old deskjet USB printer.  I can't find anything on the D-Link site that would indicate it is not compatible with the NAS print server.  I sure hope it is, since the print server is the primary reason I chose the -323.

Any help will be greatly appreciated.
Title: Re: Print Server - not working
Post by: fordem on December 19, 2008, 04:52:03 AM
Wait for the drive and then try again - let me know if it doesn't work.

If you have no disks, there is no place for the print spooler to store the print job, so it won't work.
Title: Re: Print Server - not working
Post by: cetoken on December 19, 2008, 05:51:11 AM
I had a sneaking suspicion that was the case.  I'll wait for the drives and let you know how it goes.  Just had a little dose of "new toy" impatience!  ;D
Title: Re: Print Server - not working
Post by: jrbilodeau on December 19, 2008, 04:03:27 PM
pretty sure that its because when you print to a print server it send the file to be spooled by the print server. since there are no drive, there isn't a place to write this file.
Title: Re: Print Server - not working
Post by: fordem on December 19, 2008, 05:18:01 PM
Actually - it depends on the print server - I've used several that have no hard drive, however, this print server uses a spoolfile.

The reason I know about it is that D-Link made some partition structure changes from the 1.03~1.04 firmware versions and the location of the spool file was one of them - to get rid of that "network path not found" message we would manually create a folder called, I believe, /.lpd - I believe it may be documented in a post somewhere in the forum.
Title: Re: Print Server - not working
Post by: cetoken on December 23, 2008, 05:25:31 PM
Okay - got my drives today, plugged them in, formatted as RAID1.  Restarted, plugged in my printer, added a new printer on local port \\192.168.1.210\lp and sure as heck - it worked!

Thanks for the input!

EDIT:  Not working again, after updating to 1.06 firmware - see my next post.
Title: Re: Print Server - not working (after update to 1.06)
Post by: cetoken on December 31, 2008, 11:53:56 AM
So I upgraded the firmware from 1.05 to 1.06.  Now, when I try to print, the printer acts like it's going to start - blinking power light, printhead getting into alignment, etc - then it just stops and blinks the power light at me.  After several minutes the Page Feed light blinks, I hit it, and it prints the top inch of the first page and nothing else.

I've tried deleting the printer and the local port I set up (\\192.168.1.210\lp), then re-adding.  No joy.

I tried deleting the printer and port, restarting the DNS-323, reconnecting the USB cable, then re-adding.  No joy.

Each time, after re-adding the port and printer, it successfully printed a Windows test page.  After that, it gives the behavior described above.

I disconnected the printer from the DNS-323.  The "Printer information" on the Status page now says "none" for manufacturer and product.  However, when I browse to the DNS-323 in Windows Explorer, it's still showing a printer (lp, 0 documents, "ready", "USB printer").  Tried restarting the DNS-323 - after it came up, the "lp" printer is still showing in Explorer, and the Status page still shows "none" for manufacturer and product.

Tried "clear print queue(s)", with zero effect. 

At this point I've given up.  Printer is still disconnected from the DNS-323, but still present in Windows attached to port "\\192.168.1.210\lp".  (Note that I can connect the printer directly to the PC and it prints, whiz-bang, no problem, so long as I select the correct port.)

Guess I shouldn't have done that firmware update...

Any thoughts?
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: cetoken on January 01, 2009, 02:08:54 PM
I've tried some other stuff with no success.

- Reset to factory defaults
- Shut down DNS-323, removed drives, started -323, shut it down again, reinserted drives, started up.

Note that all this was done with the printer USB cable disconnected from the unit.

Status page still shows "None" for printer manufacturer and product.  Browsing to -323 in Win Explorer still shows "lp" printer in Printers and Faxes list.

Of course the problem still remains - the printer just "stalls".
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: cetoken on January 02, 2009, 04:23:10 PM
If nobody has any ideas about this, I'm going to box the thing up and send it back.  I can get an HP print server that will work, and stick with my old external drive for backing up.
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: drthorne on January 25, 2009, 07:37:15 PM
I just "upgraded" to firmware 1.06 and my printer doesn't work anymore either, I tried everything you did in your posts. My printer is a hp 5550
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: fordem on January 25, 2009, 07:52:48 PM
A couple of different things you could try.

1 - Reformat the disks - yes - I'm  serious, and then reinstall the printer.
2 - If you have telnet access to the device create a folder called /.lpd in /mnt/HD_a2
3 - If you don't have telnet access, see if you can do the above through ftp - it's theoretically possible although I haven't tried.

I know the above may sound a little crazy - but here's what's going on.

Print jobs are stored in a "spool" file or folder called lpd which is hidden - when the first character in a name is a ".", linux hides it, hence the /.lpd - with firmware versions prior to 1.04, the /.lpd folder was in Volume_1, which is the Windows name for what linux calls /mnt/HD_a2, it was moved to a different location in 1.04 & 1.05 and, whilst fooling around with some of the new features in 1.06, I think I saw it back in Volume_1.

If I'm right - and I'm not 100% sure on this - simply creating the folder will fix the problem.

I could probably take a closer look tomorrow (it's just short of midnight here) and verify.

I guess I was mistaken - the /.lpd folder is still in /mnt/HD_a4 where it was moved to in ver 1.04 - and it still works for me.
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: cetoken on January 26, 2009, 05:46:09 AM
Thanks for your reply, but it's too late - already packed it up and sent it back.  I'm not interested in spending half my life reformatting drives and fooling with TelNet.  Will spend a few more bucks and get something that actually works.
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: fordem on January 26, 2009, 06:32:22 AM
Do remember to let us know what you got, how much you paid - and more importantly - how well it works.
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: ECF on January 27, 2009, 03:17:42 PM
I guess that works. However you do not have to update the firmware if 1.05 was working. If the printer server function is broken in the 1.06 firmware it will be fixed in the next release. However this has not been verified as it seems to be working fine so far I have not seem any issues.

If you were running any anti-virus or personal firewall software you may have wanted to disable that and see if it works.

Another thing after updating the firmware you will want to reset the DNS-323 to factory defaults and reconfigure also delete your printer from you system and setup the printer again.   
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: kd2pm on January 27, 2009, 06:20:11 PM
Ditto here with my canon i9900. 1.06 has issues with the print server.

But just in case, I will try the reset to factory defaults and then raid it again.  I thought I did everything right when I took it out of the box and did the FW upgrade before adding the drives.  That way when I did format them, the spool file would be in the right place.  Go figure....
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: escaramujo on January 31, 2009, 05:35:22 PM
Hi there,

After many hours I finally made the printer work with DNS-323 with this procedure:
1. Map "Quicken Pdf printer" to LPT1: {you will have to try other options here!}
2. Map  "lp" to LPT1: (make this the default printer)
3. map "Samsung ML-1430 Series" with location "\\192.168.1.105"
     to a "Standar TCP/IP Port" with IP address "192.168.1.105"  "raw protocol"

I hope this will help relieve the strain of setting up printers. Good luck.  8)
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: ensign rickey on February 04, 2009, 02:32:27 PM
I have two DNS 323.  Each act as a printer server.  HP960C for general use and a Canon Pixma 6000D for photos.

1.06 doesn't work!  If you have upgraded, put 1.05 back in, it works.

Roughly, to install the printer proceed as follows (XP):

Start menu
   Printers and Faxes
Add a printer
Select "a network printer, or a printer attached to another printer"
Select "browse for a printer"
double click DNS 323
Select lp
yes, ok, have disk
navigate to driver location (usually on CD)
Select xxxxx.inf  (the printer inf file)
Open
ok
Select the printer name
ok
wait while driver installs
Print a test page to be sure.

Install any other s/w needed from the CD, e.g. manuals.



Sometimes the first page is slow to start, if the file is large or the disks have gone to sleep.

Hope this helps

Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: osuchwa on February 09, 2009, 06:42:21 PM
The upgrade to 1.06 broke printing for me too.
The symptoms are:
 - the printer is in "Paused" state. Selecting "Resume Printing" trigger "Access denied" alert box
 - none of the ports are selected on the "Ports" tab of the Properties. "Add Port" and "Configure Port" buttons are disabled.

2 hour later:
Ok made it work.  After setting up telnet and running:

/usr/local/LPRng/sbin up
/usr/local/LPRng/sbin start

I can print again,  even after restarting the DNS-323

Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: Mickey3D on February 15, 2009, 01:20:05 PM
Same problem with my Epson RX425.. After uninstall driver printer , switch off DNS, switch on with no printer, install driver printer, connect printer to USB, print test page and hurrahhh !! ;-)
(With 2 pc: XP and 2000) too difficult..
Bye
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: Parafly9 on February 15, 2009, 07:19:13 PM
I've got a multifunction printer, is it possible to hook it up so that I can print and scan without doing anything *too* complicated :D
Title: Re: Print Server - not working (after upgrade to 1.06)
Post by: fordem on February 16, 2009, 05:48:21 AM
I've got a multifunction printer, is it possible to hook it up so that I can print and scan without doing anything *too* complicated :D

That would depend on what you consider *too* complicated.

Out of the box the DNS-323 will not support scanning from a multi-function device, making it happen will involve quite a bit of work and is not supported by D-Link - printing, on the other hand, should not be too difficult - however I will point out, that not all multi-function devices work well with printservers, so when I say should, I mean should, you literally have no guarantees.