Slashdot Mirror
Networked Printing on a DI-707P Router?
Feztaa asks: "I've recently purchased a D-Link DI-707P wired router, which comes equipped with a parallel port, so that you can share your printer with all computers on the local network without having to rely on somebody's computer to be on for the printer to work. Unfortunately, the router only ships with print drivers for windows. The D-Link support website basically says 'for Linux printing support, go ask the Open Source community'. I've been googling for the past few days, but most searches that include 'DI-707P' just return sites trying to sell me one. Here's what I know so far: The router's web-based config system provides no configuration for the printer, it just tells me if there's a printer plugged in and turned on or not. I portscanned the router and found that port 515 is open. I know that's LPD, but I don't know how to configure that on my system. I'm using Red Hat 9, and the GUI tools will allow me to configure a networked printer using LPD, but I can't get the thing to actually print (it asks for the IP of the printer and the name queue; I don't know how to find out the name of the queue). The printer I'm using is a BJC-250. I've had absolutely no trouble printing on this printer when it was plugged into my parallel port, so I know the printer works fine. Does anybody have any experience with this router (or similar D-Link routers), and if so, what did you have to do to get your Linux system printing with it?"
I have no clue how to use Usenet newsgroups or IRC. On your next slow news day, could you post a question on your front page asking how? It might be good to post it a couple times throughout the next few days to be sure people see it.
Thanks!
# For "Device URI" use "lpd://(hostname)/lp"
Found on http://homepage.usask.ca/~dkm560/713p.html via a Google search for "linux D-Link lpd queue".
On my Siemens router the lpd queue name is lpt1. Had to figure that out from the Windows configuration section of the manual, as the UNIX setup section said the name is lp which does not work.
foo(bar(baz(fum())));
It's been a while, but I believe the default queue name is 0 - but it depends on the LPR device.
Did you 'just try it' with different queue names?
"I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
Not wishing to be a Troll - however if it is only shared on the local network (as you stated), then why not just share it on a local machine? This would provide much better control over the printer and its current jobs etc and much less heart ache! Is there a reason why you cannot do the above? Allways nice when you can get that piece of hardware working ..... I know =) ..... but do you really need to?
What the hell is this?
/. today? It's slower than a salivating turtle.
Type "DI-707P" in the google box and hit "I'm feeling lucky".
There you go. Your fucking queue name is called "lp". Now, with that and a nice little man page, you should be ready to go.
I mean, Goddamn, can't you use Google?
And WTF is it with
If tits were wings it'd be flying around.
If you'll notice, he asks what the queue name is, not what driver to use.
Queue Name Tab
Name : DeskJet842C
Description : My Printer
Queue Type Tab
Queue Type : Networked UNIX (LPD)
Server : 192.168.0.1 (default)
Queue : lp (default)
I know that the RAW queue works fine on HP JetDirect EX printservers. Works great.
I want to delete my account but Slashdot doesn't allow it.
That is asked in a tangential fashion, but the primary question is about drivers, based on these quotes:
...Unfortunately, the router only ships with print drivers for windows...
...The router's web-based config system provides no configuration for the printer, it just tells me if there's a printer plugged in and turned on or not...
...The printer I'm using is a BJC-250. I've had absolutely no trouble printing on this printer when it was plugged into my parallel port...
I rest my case.
I've not used this device, but I've done lots of work with various lpd network adaptors...
The most comon queue names are:
PRINT, RAW, LP, and LPT1
I would expect one of those to work.
Two things here.... First, your type of attitude is one of the reasons many newbies give up on Linux. When they have a problem they look to experienced people and get told they are morons.... that does'nt help. Try to be a little more constructive, its not that hard to do. Really. Second, read the whole question. Understand the question. Then realize that all he was asking was about was LPR queue name that the router used. Sure he might of added irrelevant info, but the core question is there. /rant
The Que name for the one that I was working with was LPT1.
Try PORT1 for the queue name.
Slashdot isn't exactly the place to look for this type of information.
There are no trails. There are no trees out here.
And as I pointed out the queue name is not the core question. :)
He's already said he looked on D-Link's site (although not that hard because the answer to the queue name question is right here).
Yes, the attitude is one thing, but y'know what? This isn't a site for newbies! It's "News for NERDS etc.
But it's a slow news day, so what can ya do?
Yeah, I posted this about a week ago, I've figured it out since then. I wasn't expecting slashdot to actually approve this.
The queue name was 'lp'. Now go to hell, you bastards.
cal 2003 | netcat -s your.ip.address.here -p 515
:-)
If it prints a calendar you are in business
Seriously everything you need to print is text right?
To print out a file just replace "cal 2003" with "cat your.file" what could be simpler?
Wang33
PAGERANK++ Robsell.com
Yeah, I posted this about a week ago, I've figured it out since then. I wasn't expecting slashdot to actually approve this.
You asked a lpd 101 question that could easily have been Googled, which is an invitation for flames. But, you submitted a question to askSlashdot, with the intent of it NOT being posted? That's asinine.
If you didn't want it posted, you should not have submitted it. The fact that you are getting flamed now is your own fault and telling people to "go to hell" is just inviting more flames.
But, then again, maybe you have pulled off the ultimate troll. If so, you got me.
Turn OFF a computer?
ARE YOU INSANE???
If you are too stupid to understand what the options are in the moderation, then DON'T FUCKING MODERATE!! There's a bunch of negative moderations here that are marked Redundant, like someone else made the same joke.
If you want to moderate something down, and don't want to worry about the reason, just use Overrated. Sure, it's the pussy way out, and isn't subject to M2, but at least it would make more sense than using a moderation option that isn't even remotely close to why the post needs modded down.
Mod this down as -1 Redundant too. I don't give a shit. I have Karma coming out my ass like this guy
Overrated / Underrated : Moderation
Pulled the PDF manuals from their home website, D-Link TW, and in both firmware versions of the 707, the queue name is lp.
All I know about Bush is I had a job when Clinton was president.
And the real reason why you know so little, is the patriot act. BTW, are you watching the spying that is going on the democratic by the FBI?
When you ask a pack of 20,000 geeks a question, YOu can pretty much expect that at least one of them is gonna be a dork that flames you for the question. This is not to justify the abusive response. I'm just pointing out that it was statistically probable dork response.
Free Software: Like love, it grows best when given away.
Why not just use windows? Plug and Play baby!
I have an older D-Link that is a wired/wireless router with a 25pin parallel port for a printer. I can connect any DHCP aware OS behind it and my GW and DNS are that of my router. Same for the printer. Basically, just plug the thing in and power cycle the router. Then connect your client to it by IP. I personally started with my wife's WinXP box... just told it I had a network printer on TCP/IP and gave it the IP of my router (the private IP), then installed the driver. Then I did the same thing on my Linux boxes... used RH9's printer GUI... set it up on IP and loaded the driver.