DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2008-02-25 19:10:12

mirceani
Member
Registered: 2007-06-07
Posts: 5

Print server issue with new firmware - pls HELP

Just upgraded my firmware from 1.03 to 1.04
Everything OK exept the print server which stopped working

Was working fine with the old firmware.

I've noticed a new directory on the root called   .system
It is read only and cannot acces that

Previously there was a directory called .lpd which is gone now



Anybody has any suggestions?



Thank you

Offline

 

#2 2008-02-25 20:07:10

acglj
Member
Registered: 2007-06-30
Posts: 9

Re: Print server issue with new firmware - pls HELP

I had similar problem after changing HDD. It seems that FW1.04 is not able to create new folder with printer queue. I resolved my case by creating the folder manually.
Check if the folder ".lpd" exists on your drive (right hand side i.e. /mnt/HD_a2).

Offline

 

#3 2008-02-27 06:09:00

briansailing
Member
Registered: 2008-01-15
Posts: 5

Re: Print server issue with new firmware - pls HELP

thanks
I had that problem after rebuilding a drive in a raid 1 dont know why it disappeared.  You have to make the folder in the web access in the folder permission section.

Offline

 

#4 2008-02-28 02:18:08

mirceani
Member
Registered: 2007-06-07
Posts: 5

Re: Print server issue with new firmware - pls HELP

I tried, but it is not working.
The moment when I type the . under the foledr name, the cursor automatically moves to the left
I can create a folder named \lpd, but not one named \.lpd

Bottom line, print server is dead.

Any more ideas?


Thank you

Offline

 

#5 2008-02-28 03:07:56

acglj
Member
Registered: 2007-06-30
Posts: 9

Re: Print server issue with new firmware - pls HELP

> Any more ideas?

Yes, use telnet, make directory .lpd on /mnt/HD_a2, and change the rights of dir to 777 (I think it is necessary that everyone is able to write/modify the content of dir, so everyone can send the file to printer)

Jacek

Offline

 

#6 2008-02-28 08:30:37

rap
Member
From: Reading - UK
Registered: 2008-02-28
Posts: 119

Re: Print server issue with new firmware - pls HELP

Thanks for this - I was having the same problem and this sorted it for me smile

RAP

Offline

 

#7 2008-02-28 09:17:14

knireis
Member
Registered: 2007-12-10
Posts: 231

Re: Print server issue with new firmware - pls HELP

acglj wrote:

> Any more ideas?

Yes, use telnet, make directory .lpd on /mnt/HD_a2, and change the rights of dir to 777 (I think it is necessary that everyone is able to write/modify the content of dir, so everyone can send the file to printer)

Jacek

For me as linux nono, i don't know how to create a directory with telnet. Could you specify the command? I have telnet available via fonz funplug.

Offline

 

#8 2008-02-28 09:50:01

acglj
Member
Registered: 2007-06-30
Posts: 9

Re: Print server issue with new firmware - pls HELP

here is the list

cd /mnt/HD_a2
mkdir .lpd
chmod 777 .lpd

should work....

Offline

 

#9 2008-02-28 10:20:06

sjmac
Member
Registered: 2008-01-21
Posts: 222

Re: Print server issue with new firmware - pls HELP

and then maybe
ls -ald .lpd
to check that the other commands have worked. It should look like this:

Code:

BusyBox v1.8.1 (2007-11-20 23:39:08 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/mnt/HD_a2 # ls -ald /mnt/HD_a2/.lpd
drwxrwxrwx    2 root     root         4096 Feb  3 21:48 /mnt/HD_a2/.lpd
/mnt/HD_a2 #

By the way, when I upgraded to firmware 1.04 and reformatted my drives as two separate"standard" drives, the .lpd directory seems to have been created automatically

=== edit ===

I did have to run the format twice because it seemed to "get stuck" the first time, and I upgraded from 1.03 via a prerelease version of 1.04, so maybe that made a difference?

Last edited by sjmac (2008-02-28 10:43:11)

Offline

 

#10 2008-03-02 21:41:53

fordem
Member
Registered: 2007-01-26
Posts: 1938

Re: Print server issue with new firmware - pls HELP

It seems the .lpd  directory is no longer required with fw 1.04.

I changed the configuration of my system to a pair of 250GB Seagates in a RAID1 array, and then recreated the print server as a local port named \\<dns-323-ip-address.\lp and it works without the .lpd directory.

Offline

 

#11 2008-03-02 22:30:56

HawaiiTom
New member
Registered: 2008-03-01
Posts: 1

Re: Print server issue with new firmware - pls HELP

I just got my DNS-323, and had the same problem. It shipped with FW 1.03 installed, and I read online that there was a new 1.04, so I upgraded to it after my initial setup, and before formatting. I then had two issues that I had to call D-Link tech support about. The first was that after formatting my dual Seagate 500's as RAID1, the status showed that I only had 7.5 megabytes worth of storage. At this time, my print server saw my DeskJet 950 and printed out a test page (solid proof!). When I called tech support, they said to just reformat the drives. When I did that, the storage showed up correctly as 460 GB (40 GB overhead on each drive? Yikes!) But then, the printer didn't work. The status screen still showed the Desk Jet installed, but sending anything to that printer died immediately. I noticed that I had a hidden folder (I turn on viewing of all files and folders) named .systemfile, but no .lpd.

The Boys in Bangalore were stumped, and I got escalated to different people twice, but they couldn't help me. When I came here and read this thread, I decided I needed to learn about Linux for the first time. I was able to set up FTP and port over all the right files to install Telnet, but never got it to work. I finally bit the bullet and downgraded back to FW 1.03, then reformatted the drives again. After three formatting failures of different types, I finally got the drives to read correctly and noticed that I now had the infamous .lpd hidden folder back, and installed the printer so it worked. Then I upgraded to FW 1.04 to see the results. (Heck, there was nothing on the drives... it was only time). This time, I got the .systemfile folder created and it left the .lpd file in place. The Printer still worked! And the bonus was, suddenly I could now get Telnet to work as well, following exactly the same procedures I had used before which had failed. Now I put in Twonky Vison, too, because did the built-in UPnP server was cutting off long movies after a half-hour

So the moral... before you put any info on your new drives, make sure the print server and the FTP both work, turn on your hidden files and folders so you can see if you have both folders, and only then, start to backup data.

Whew! I will say that, despite about 8 hours of frustration, it was a bit fun, for an old DOS command-line person, to learn a few simple Linux commands and also use the built in Command-line FTP and Telnet clients hidden deep in Windows.

Tom

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB