Re: [newbie] HP Jetdirect printing

2000-10-11 Thread Mark Weaver

Greg,

Take some canned air and blow the crap out-a the fan. Then put a few drops
of 3-in-1 oil on the fan shaft and no more noise. I've had to do this for
a few of the older PC's in our building and the users think I'm performing
some kind of magic! works great.

-- 
Mark

/*  I never worry about the to-jams.
 *  Once I've stuck my foot in my mouth
 *  it's already too late...just make sure
 *  you chew them thoroughly before swallowing!
 */ 
Registered Linux user #182496
 *   Pine 4.21   *

On Tue, 10 Oct 2000 11:00pm ,Greg Stewart spake passionately in a message:

  Besides the ipchains, there is a dnscache, dhcp, ssh, dhclient and
 portsentry (for
  grins).
 
 Aw, c'mon... you can fit an Apache Web Server, MySQL Database, and a hefty
 load of php scripts in there too!!!  :-)
 
  I opted for the easy way out and used the Linux Router Project, notably
 Charles Steinkulers
  diskimages.
 
 Actually, a friend of mine at work has just re-done his firewall, and built
 a disk-less linux router to handle firewalling and port-forwarding. He's
 booting from floppy on a modified kernel. I'm thinking of trying the same
 thing...the noise from the power supply fan on my P166 firewall/ftp server
 is just pissing me off.  :-)
 
 --Greg
 
 
 - Original Message -
 From: "Dennis Veatch" [EMAIL PROTECTED]
 
 
  I should have read your reply before sending mine off to Bascule. That was
  better than my point-point reply.
 
  The firewall as I have it set up does most all you mentioned. I opted for
  the
  easy way out and used the Linux Router Project, notably Charles
 Steinkulers
  diskimages.
 
  As for the bad form of running most all those things on one box. I agree,
  however, as you saw its just a couple of workstations and a printer.
 Besides
  the
  ipchains, there is a dnscache, dhcp, ssh, dhclient and portsentry (for
  grins).
 
  - Original Message -
  From: "Greg Stewart" [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Tuesday, October 10, 2000 7:04 PM
  Subject: Re: [newbie] HP Jetdirect printing
 
 
   Bascule,
  
   In his diagram, Dennis indicates that the two workstations are DHCP
  clients.
   Since he is on a private network, behind a firewall, and does not
 include
  a
   separate server for the DHCP provider service, the firewall itself could
   very well be the DHCP server--although he may have another server on his
   network doing the job.
  
   A firewall, can be simply that, a firewall, and nothing else. Or, it can
  be
   several things at the same time... in this case, possibly a DHCP server.
  It
   can also be a router...but not necessarily so.
  
   As a firewall that "masquerades" an internal, private network, it is
 doing
   some routing tasks, but not all. So, it is "sort of" a router, but not
   really. A true router will separate segments of a network by the subnet
   mask, and isolate network traffic that does not belong on the other
   segments, keeping the different segments nice and "quiet".
  
   A router can also act as a DHCP server if it is set up to do so. And, to
   complicate things even further, a router can also be a firewall. And, in
   fact, a router can be a DHCP serving, firewalling, packet-forwarding,
 DNS
   serer if you really, really, r-e-a-l-l-y, wanted it to be. But that's
  giving
   the poor machine a bit of work to do all at the same time, and if you're
  on
   a large internal network, it's not considered "good practice".
  
   Does that clear things up a bit? Or, have I successfully confused the
  issue
   beyond repair?  :-)
  
   --Greg
  
  
  
   - Original Message -
   From: "bascule" [EMAIL PROTECTED]
  
  
could i jump in and ask a couple of questions that might help me
understand your diagram? i can't help you i'm afraid but i think i
 might
learn something from any future answers to your query, does dhcp mean
that the box is being given it's ip address by a dhcp server? (or is
being a server - only one needed though right?) in which case which is
the dhcp server, the firewall? (is this what is called a  router?), is
your network printer configured via the network or by physical
 switches
etc.(i.e. how do you assign it an ip?)
i hope you don't mind my butting in but i am interested in networking
questions
   
bascule
   
  
  
  
 
 
  __
   Vous avez un site perso ?
   2 millions de francs à gagner sur i(france) !
   Webmasters : ZE CONCOURS !
 http://www.ifrance.com/_reloc/concours.emailif
  
  
  
 
 
 
  
 __
 Vous avez un site perso ?
 2 millions de francs à gagner sur i(france) !
 Webmasters : ZE CONCOURS ! http://www.ifrance.com/_reloc/concours.emailif
 
 
 
 





Re: [newbie] HP Jetdirect printing

2000-10-10 Thread bascule

could i jump in and ask a couple of questions that might help me
understand your diagram? i can't help you i'm afraid but i think i might
learn something from any future answers to your query, does dhcp mean
that the box is being given it's ip address by a dhcp server? (or is
being a server - only one needed though right?) in which case which is
the dhcp server, the firewall? (is this what is called a  router?), is
your network printer configured via the network or by physical switches
etc.(i.e. how do you assign it an ip?)
i hope you don't mind my butting in but i am interested in networking
questions

bascule

 
 Now that you got the picture, the obvious reason  for this message is
 the difficulty of getting the Linux box to sent print jobs to the
 laser printer.
 
 The printer is configured to use gateway 192.168.1.200 though I do not
 think this is correct. I have tired it with and without a gateway and
 neither works.
 
 One thing I am confused about is what to enter as the remote queue
 when using printtool. Which by the I can ping, telnet, run the
 printtool test pages and all works just fine.
 
 The only problem I am having is printing from any KDE appications
 including Netscape. When attempting to print nothing happens, that is
 to say, there are no errors that pop up and no port actvity for the
 printer.
 
 Any idea what I am doing wrong here? This should be a simple thing to
 do and yet it has me stumped. This should probably be on the experts
 list.
 
 TIA
 Dennis Veatch




Re: [newbie] HP Jetdirect printing

2000-10-10 Thread Greg Stewart

Bascule,

In his diagram, Dennis indicates that the two workstations are DHCP clients.
Since he is on a private network, behind a firewall, and does not include a
separate server for the DHCP provider service, the firewall itself could
very well be the DHCP server--although he may have another server on his
network doing the job.

A firewall, can be simply that, a firewall, and nothing else. Or, it can be
several things at the same time... in this case, possibly a DHCP server. It
can also be a router...but not necessarily so.

As a firewall that "masquerades" an internal, private network, it is doing
some routing tasks, but not all. So, it is "sort of" a router, but not
really. A true router will separate segments of a network by the subnet
mask, and isolate network traffic that does not belong on the other
segments, keeping the different segments nice and "quiet".

A router can also act as a DHCP server if it is set up to do so. And, to
complicate things even further, a router can also be a firewall. And, in
fact, a router can be a DHCP serving, firewalling, packet-forwarding, DNS
serer if you really, really, r-e-a-l-l-y, wanted it to be. But that's giving
the poor machine a bit of work to do all at the same time, and if you're on
a large internal network, it's not considered "good practice".

Does that clear things up a bit? Or, have I successfully confused the issue
beyond repair?  :-)

--Greg



- Original Message -
From: "bascule" [EMAIL PROTECTED]


 could i jump in and ask a couple of questions that might help me
 understand your diagram? i can't help you i'm afraid but i think i might
 learn something from any future answers to your query, does dhcp mean
 that the box is being given it's ip address by a dhcp server? (or is
 being a server - only one needed though right?) in which case which is
 the dhcp server, the firewall? (is this what is called a  router?), is
 your network printer configured via the network or by physical switches
 etc.(i.e. how do you assign it an ip?)
 i hope you don't mind my butting in but i am interested in networking
 questions

 bascule


 
__
Vous avez un site perso ?
2 millions de francs à gagner sur i(france) !
Webmasters : ZE CONCOURS ! http://www.ifrance.com/_reloc/concours.emailif






Re: [newbie] HP Jetdirect printing

2000-10-10 Thread bascule

no confusion, all was well put

thanks

bascule

Greg Stewart wrote:
 
 Bascule,
 
 In his diagram, Dennis indicates that the two workstations are DHCP clients.
 Since he is on a private network, behind a firewall, and does not include a
 separate server for the DHCP provider service, the firewall itself could
 very well be the DHCP server--although he may have another server on his
 network doing the job.
 
 A firewall, can be simply that, a firewall, and nothing else. Or, it can be
 several things at the same time... in this case, possibly a DHCP server. It
 can also be a router...but not necessarily so.
 
 As a firewall that "masquerades" an internal, private network, it is doing
 some routing tasks, but not all. So, it is "sort of" a router, but not
 really. A true router will separate segments of a network by the subnet
 mask, and isolate network traffic that does not belong on the other
 segments, keeping the different segments nice and "quiet".
 
 A router can also act as a DHCP server if it is set up to do so. And, to
 complicate things even further, a router can also be a firewall. And, in
 fact, a router can be a DHCP serving, firewalling, packet-forwarding, DNS
 serer if you really, really, r-e-a-l-l-y, wanted it to be. But that's giving
 the poor machine a bit of work to do all at the same time, and if you're on
 a large internal network, it's not considered "good practice".
 
 Does that clear things up a bit? Or, have I successfully confused the issue
 beyond repair?  :-)
 
 --Greg
 
 - Original Message -
 From: "bascule" [EMAIL PROTECTED]
 
  could i jump in and ask a couple of questions that might help me
  understand your diagram? i can't help you i'm afraid but i think i might





Re: [newbie] HP Jetdirect printing

2000-10-10 Thread Dennis Veatch


- Original Message -
From: "bascule" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 10, 2000 5:37 PM
Subject: Re: [newbie] HP Jetdirect printing


 could i jump in and ask a couple of questions that might help me
 understand your diagram? i can't help you i'm afraid but i think i might
 learn something from any future answers to your query, does dhcp mean
 that the box is being given it's ip address by a dhcp server?

Yes. The dhcp server is actually a 486 box I'm using as a firewall.

(or is
 being a server - only one needed though right?) in which case which is
 the dhcp server, the firewall? (is this what is called a  router?),

Not sure what you mean by that first part. If I understand you right, yes,
only one dhcp
server is needed. The primary function of the box IS to be a firewall. I
could have as
easily used static IPs instead of dynamic. Since RoadRunner uses dhcp for my
internet
address, I figured I would just carry on with dhcp.

is your network printer configured via the network or by physical switches
 etc.(i.e. how do you assign it an ip?)

With the Jetdirect, the printers IP can be done via HPs webjet software,
their
JetAdmin software or telnet from a workstation.

 i hope you don't mind my butting in but i am interested in networking
 questions


Not a problem.

 bascule

 
  Now that you got the picture, the obvious reason  for this message is
  the difficulty of getting the Linux box to sent print jobs to the
  laser printer.
 
  The printer is configured to use gateway 192.168.1.200 though I do not
  think this is correct. I have tired it with and without a gateway and
  neither works.
 
  One thing I am confused about is what to enter as the remote queue
  when using printtool. Which by the I can ping, telnet, run the
  printtool test pages and all works just fine.
 
  The only problem I am having is printing from any KDE appications
  including Netscape. When attempting to print nothing happens, that is
  to say, there are no errors that pop up and no port actvity for the
  printer.
 
  Any idea what I am doing wrong here? This should be a simple thing to
  do and yet it has me stumped. This should probably be on the experts
  list.
 
  TIA
  Dennis Veatch






Re: [newbie] HP Jetdirect printing

2000-10-10 Thread Dennis Veatch

I should have read your reply before sending mine off to Bascule. That was
better than my point-point reply.

The firewall as I have it set up does most all you mentioned. I opted for
the
easy way out and used the Linux Router Project, notably Charles Steinkulers
diskimages.

As for the bad form of running most all those things on one box. I agree,
however, as you saw its just a couple of workstations and a printer. Besides
the
ipchains, there is a dnscache, dhcp, ssh, dhclient and portsentry (for
grins).

- Original Message -
From: "Greg Stewart" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 10, 2000 7:04 PM
Subject: Re: [newbie] HP Jetdirect printing


 Bascule,

 In his diagram, Dennis indicates that the two workstations are DHCP
clients.
 Since he is on a private network, behind a firewall, and does not include
a
 separate server for the DHCP provider service, the firewall itself could
 very well be the DHCP server--although he may have another server on his
 network doing the job.

 A firewall, can be simply that, a firewall, and nothing else. Or, it can
be
 several things at the same time... in this case, possibly a DHCP server.
It
 can also be a router...but not necessarily so.

 As a firewall that "masquerades" an internal, private network, it is doing
 some routing tasks, but not all. So, it is "sort of" a router, but not
 really. A true router will separate segments of a network by the subnet
 mask, and isolate network traffic that does not belong on the other
 segments, keeping the different segments nice and "quiet".

 A router can also act as a DHCP server if it is set up to do so. And, to
 complicate things even further, a router can also be a firewall. And, in
 fact, a router can be a DHCP serving, firewalling, packet-forwarding, DNS
 serer if you really, really, r-e-a-l-l-y, wanted it to be. But that's
giving
 the poor machine a bit of work to do all at the same time, and if you're
on
 a large internal network, it's not considered "good practice".

 Does that clear things up a bit? Or, have I successfully confused the
issue
 beyond repair?  :-)

 --Greg



 - Original Message -
 From: "bascule" [EMAIL PROTECTED]


  could i jump in and ask a couple of questions that might help me
  understand your diagram? i can't help you i'm afraid but i think i might
  learn something from any future answers to your query, does dhcp mean
  that the box is being given it's ip address by a dhcp server? (or is
  being a server - only one needed though right?) in which case which is
  the dhcp server, the firewall? (is this what is called a  router?), is
  your network printer configured via the network or by physical switches
  etc.(i.e. how do you assign it an ip?)
  i hope you don't mind my butting in but i am interested in networking
  questions
 
  bascule
 




__
 Vous avez un site perso ?
 2 millions de francs à gagner sur i(france) !
 Webmasters : ZE CONCOURS ! http://www.ifrance.com/_reloc/concours.emailif








Re: [newbie] HP Jetdirect printing

2000-10-10 Thread Greg Stewart

 Besides the ipchains, there is a dnscache, dhcp, ssh, dhclient and
portsentry (for
 grins).

Aw, c'mon... you can fit an Apache Web Server, MySQL Database, and a hefty
load of php scripts in there too!!!  :-)

 I opted for the easy way out and used the Linux Router Project, notably
Charles Steinkulers
 diskimages.

Actually, a friend of mine at work has just re-done his firewall, and built
a disk-less linux router to handle firewalling and port-forwarding. He's
booting from floppy on a modified kernel. I'm thinking of trying the same
thing...the noise from the power supply fan on my P166 firewall/ftp server
is just pissing me off.  :-)

--Greg


- Original Message -
From: "Dennis Veatch" [EMAIL PROTECTED]


 I should have read your reply before sending mine off to Bascule. That was
 better than my point-point reply.

 The firewall as I have it set up does most all you mentioned. I opted for
 the
 easy way out and used the Linux Router Project, notably Charles
Steinkulers
 diskimages.

 As for the bad form of running most all those things on one box. I agree,
 however, as you saw its just a couple of workstations and a printer.
Besides
 the
 ipchains, there is a dnscache, dhcp, ssh, dhclient and portsentry (for
 grins).

 - Original Message -
 From: "Greg Stewart" [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Tuesday, October 10, 2000 7:04 PM
 Subject: Re: [newbie] HP Jetdirect printing


  Bascule,
 
  In his diagram, Dennis indicates that the two workstations are DHCP
 clients.
  Since he is on a private network, behind a firewall, and does not
include
 a
  separate server for the DHCP provider service, the firewall itself could
  very well be the DHCP server--although he may have another server on his
  network doing the job.
 
  A firewall, can be simply that, a firewall, and nothing else. Or, it can
 be
  several things at the same time... in this case, possibly a DHCP server.
 It
  can also be a router...but not necessarily so.
 
  As a firewall that "masquerades" an internal, private network, it is
doing
  some routing tasks, but not all. So, it is "sort of" a router, but not
  really. A true router will separate segments of a network by the subnet
  mask, and isolate network traffic that does not belong on the other
  segments, keeping the different segments nice and "quiet".
 
  A router can also act as a DHCP server if it is set up to do so. And, to
  complicate things even further, a router can also be a firewall. And, in
  fact, a router can be a DHCP serving, firewalling, packet-forwarding,
DNS
  serer if you really, really, r-e-a-l-l-y, wanted it to be. But that's
 giving
  the poor machine a bit of work to do all at the same time, and if you're
 on
  a large internal network, it's not considered "good practice".
 
  Does that clear things up a bit? Or, have I successfully confused the
 issue
  beyond repair?  :-)
 
  --Greg
 
 
 
  - Original Message -
  From: "bascule" [EMAIL PROTECTED]
 
 
   could i jump in and ask a couple of questions that might help me
   understand your diagram? i can't help you i'm afraid but i think i
might
   learn something from any future answers to your query, does dhcp mean
   that the box is being given it's ip address by a dhcp server? (or is
   being a server - only one needed though right?) in which case which is
   the dhcp server, the firewall? (is this what is called a  router?), is
   your network printer configured via the network or by physical
switches
   etc.(i.e. how do you assign it an ip?)
   i hope you don't mind my butting in but i am interested in networking
   questions
  
   bascule
  
 
 
 


 __
  Vous avez un site perso ?
  2 millions de francs à gagner sur i(france) !
  Webmasters : ZE CONCOURS !
http://www.ifrance.com/_reloc/concours.emailif
 
 
 



 
__
Vous avez un site perso ?
2 millions de francs à gagner sur i(france) !
Webmasters : ZE CONCOURS ! http://www.ifrance.com/_reloc/concours.emailif






[newbie] HP Jetdirect printing

2000-10-09 Thread Dennis Veatch



Here is my setup of things:

 | 
RoadRunner
|--
| Firewall |
||192.168.1.254 - Private 
Network
 |
 |
_
| 
|__
| 
Hub 
| 
|
|_|-- 
_
 
| 
| 
| 
|
 
|-- 
| LM 
7.1|
__ 
| Jet Direct 
| 
|_|
| 
| 
| HP LJ4Plus 
| 
DHCP
| Win98SE 
| 
||
|_| 
192.168.1.200
DHCP



Now that you got the picture, the obvious 
reason for this message is the difficulty of getting the Linux box to sent 
print jobs to the laser printer.

The printer is configured to use gateway 
192.168.1.200 though I do not think this is correct. I have tired it with and 
without a gateway and neither works.

One thing I am confused about is what to enter as 
the remote queue when using printtool. Which by the I can ping, telnet, run the 
printtool test pages and all works just fine. 

The only problem I am having is printing from any 
KDE appications including Netscape. When attempting to print nothing happens, 
that is to say, there are no errors that pop up and no port actvity for the 
printer.

Any idea what I am doing wrong here? This should be 
a simple thing to do and yet it has me stumped. This should probably be on the 
experts list.

TIA
Dennis Veatch


Re: [newbie] HP Jetdirect printing

2000-10-09 Thread Chris Slater-Walker



Try using the IP address of the printer for the 
host name, and a queue name of "raw" (no quotes). I have an HP LJ4M Plus with 
internal JetDirect card and it works fine for me. Note that the version of 
printtool supplied with 7.0 and 7.1 doesn't seem to work. Others have 
experienced this. If you can get hold of the printtool RPM from Red Hat 6.1 or 
6.2 and install it, you should be fine.

Chris Slater-Walker

  - Original Message - 
  From: 
  Dennis Veatch 
  
  To: [EMAIL PROTECTED] 
  Sent: Monday, September 18, 2000 1:46 
  PM
  Subject: [newbie] HP Jetdirect 
  printing
  
  Here is my setup of things:
  
   | 
  RoadRunner
  |--
  | Firewall |
  ||192.168.1.254 - Private 
  Network
   
  |
   
  |
  _
  | 
  |__
  | 
  Hub 
  | 
  |
  |_|-- 
  _
   
  | 
  | 
  | 
  |
   
  |-- 
  | LM 
  7.1|
  __ 
  | Jet Direct 
  | 
  |_|
  | 
  | 
  | HP LJ4Plus 
  | 
  DHCP
  | Win98SE 
  | 
  ||
  |_| 
  192.168.1.200
  DHCP
  
  
  
  Now that you got the picture, the obvious 
  reason for this message is the difficulty of getting the Linux box to 
  sent print jobs to the laser printer.
  
  The printer is configured to use gateway 
  192.168.1.200 though I do not think this is correct. I have tired it with and 
  without a gateway and neither works.
  
  One thing I am confused about is what to enter as 
  the remote queue when using printtool. Which by the I can ping, telnet, run 
  the printtool test pages and all works just fine. 
  
  The only problem I am having is printing from any 
  KDE appications including Netscape. When attempting to print nothing happens, 
  that is to say, there are no errors that pop up and no port actvity for the 
  printer.
  
  Any idea what I am doing wrong here? This should 
  be a simple thing to do and yet it has me stumped. This should probably be on 
  the experts list.
  
  TIA
  Dennis 
Veatch