What's the trick to make Ethernet work on an HP 2100TN printer?

[Misha]

Sure it would. It will use the same address as before unless there is a
reason not to (eg that address is in use by something else).

Ah. I see. I start at 192.168.1.2 and let DHCP assign the addresses.
I don't have 16 PCs and phones, so, I guess there's nothing stopping
the printer from keeping its old address (from another home) of
192.168.1.16 then. Even with DHCP.

 

[Misha]

BTW: That's a HP Jetdirect 600n and the last Firmware is Version =
G.08.49 Your Telnet session shows; "G.07.20" so it could be upgraded.
However it isn't too important and you are just learning about HP
JetDirect Print Servers.

Thanks for that foreknowledge.

I'll probably keep the "JetDirect" at the current version unless I know
of a reason to change it. I don't want to have to reconfigure the windows
machines if I don't have to. I'm not sure what's transparent and what
isn't, to the windows and Linux machines.

BTW, I think "this" is the JetDirect box on the side of the printer:
http://i40.tinypic.com/25r166w.gif

Right?

 

[Misha]

So many folks just update for the sake of update's and getting into
trouble.

I can't count the number of times I've worried that I've bricked
a device simply upgrading it to the latest firmware.

So I don't disagree with you.

 

[Misha]

Yes, it is. It was created only a month, maybe two months ago.

Ah, that might explain it then.
Thanks!

 

[Jasen Betts]

Just in case others need this, here is the sequence that finally worked
to be able to print to a networked printer for my first time, using
Windows XP and Linux (on deck is Windows 7 and Android).

0. Connect HP 2100TN printer ethernet to your home broadband router.
2. Configure Windows XP (also wired to the router) to print to it:
http://i41.tinypic.com/vi39lt.jpg
3. Configure Linux (wirelessly connected to the router) to print to it:
http://i42.tinypic.com/rjl37s.jpg

Since this was all hunt-and-peck, I post these to help others and for
folks (who actually know what they're doing) to tell me whether I could
have configured WinXP and Linux an easier way to print to a networked
printer.

Your linux method looks near optimal.

 

[Jasen Betts]

You're not kidding there's no feedback!
I had to reboot the computer to kill the session!

to end a stuck telnet session: ctrl-] Q enter

 

[David H. Lipman]

Thanks for that foreknowledge.

I'll probably keep the "JetDirect" at the current version unless I know
of a reason to change it. I don't want to have to reconfigure the windows
machines if I don't have to. I'm not sure what's transparent and what
isn't, to the windows and Linux machines.

BTW, I think "this" is the JetDirect box on the side of the printer:
http://i40.tinypic.com/25r166w.gif

Right?

Yes, inside that metal cage and under that plastic door.

 

[David H. Lipman]

I can't count the number of times I've worried that I've bricked
a device simply upgrading it to the latest firmware.

So I don't disagree with you.

Well I have upgraded hundreds of JetDirects with no sequalae. Either using HP Download
Manager or via HP Web JetAdmin over TCP/IP or with the printer connected via USB or
parallel port. I keep HP Download Manager on my notebook with all the JetDirect Firmware
files so I can download the latest Firmware to client printers as needed.

If the printer has power and you leave it alone for the time it takes to download the
Firmware to the printer, it will work as expected.

 

[David H. Lipman]

Is the "JetDirect" print server this "box" sticking out the
side of the printer?
http://i40.tinypic.com/25r166w.gif

Or is the JetDirect just firmware running on the motherboard?

It's the BIOS that sits on the JetDirect card that plugs into certain HP printers such as
LaserJet, DesignJet, etc.

Shown below are the 610n and 615n. Yours is the 600n but is looks generally the same.
http://multi-av.thespykiller.co.uk/other/JetDirect-6xx.jpg

 

[SC Tom]

Ah, that might explain it then.
Thanks!

I'm showing posts as early as January 2013 on Eternal September, so it's
been around for a few months anyhow.

 

[Gene E. Bloch]

It wasn't intuitive, but, I was able to set up the printer
to print to the networked printer from all three platforms
(except Android):

Windows XP ==> http://i41.tinypic.com/vi39lt.jpg
Windows 7 ==> http://i40.tinypic.com/2hoba78.jpg
Linux ==> http://i40.tinypic.com/2r4ika8.jpg

If anyone has a clue how to print using Android on WiFi,
please let me know as I don't know where to start.

My useless reply:

I got a networked Epson printer, and its installation was effortless on
W7 and Android.

One penalty for that is that, unlike you, I had no chance to *learn*
anything. I'm not kidding - I seriously feel that difficulties like
yours are a way to learn.

This reply is more meant to indicate that the situation varies for
different manufacturers, in case anyone else wants to set up a networked
printer.

One disclaimer: I have no idea if other Epson printers install as
easily. This one is an Expression Premium XP-800 all-in-one.

 

[Rick Jones]

Yep. Unless/until it is powered-off long enough and Misha has 115 or
so other devices request IP addresses of the DHCP server on his home
gateway

What's interesting is that it kept the same IP address from one
house to another, under different networks (both using 191.168.1.1
as the gateway).

More or less luck that both you and your friend's home gateways
defaulted to useing 192.168.1.0/16 as the default private IP address
space for the home network. 192.168.1.0/16 is a fairly common
convention among such devices, though one probably shouldn't come to
depend on that.

Likely as not, the printer "remembered" it had 192.168.1.116, and when
it sent the DHCP request it, in essence, asked "May I still use this
IP address?" and the DHCP server function said "Yes."

While the odds of something else attaching to your network and getting
192.168.1.116 as its IP address are probably pretty low, it might be a
Good Idea (tm) to go into the configuration of your home gateway, and
see where its dynamically assigned IP range ends and the static range
begins. At some point you may need/want to configure the printer with
a static IP, though that will require reconfiguring the machines
you've already configured to print to it. If that day comes, altering
the dynamic range so that 192.168.1.116 isn't in it, and statically
configuring the printer to use 192.168.1.116 might be the way to go.

rick jones
despite my email address, I actually know very little about HP
printers themselves...

 

[Rick Jones]

Yep. Unless/until it is powered-off long enough and Misha has 115
or so other devices request IP addresses of the DHCP server on his
home gateway

Or, perhaps, if the printer is reset to factory defaults.

More or less luck that both you and your friend's home gateways
defaulted to useing 192.168.1.0/16 as the default private IP address
space for the home network. 192.168.1.0/16 is a fairly common
convention among such devices, though one probably shouldn't come to
depend on that.

Make that 192.168.1.0/24 (probably). I've had a particular /16
network on the brain for the last couple of days.

rick jones

 

[Misha]

to end a stuck telnet session: ctrl-] Q enter

Thanks! Who would have known it's control Q and not control C or escape!

 

[Misha]

Shown below are the 610n and 615n. Yours is the 600n but is looks
generally the same.
http://multi-av.thespykiller.co.uk/other/JetDirect-6xx.jpg

Ah, I see, It *is* the card itself.
Thanks.

 

[unruh]

to end a stuck telnet session: ctrl-] Q enter

Thanks! Who would have known it's control Q and not control C or escape!

It is not either. It is control ] followed by Q for Quit.
control ]
(that is hold down the control key while typing ]) puts telnet into
command mode, and then the command is Q for quit.

 

[Misha]

(that is hold down the control key while typing ]) puts telnet into
command mode, and then the command is Q for quit.

Yikes. Even less intuitive. I'd better save that one in my command file!
Thanks.

 

[unruh]

(that is hold down the control key while typing ]) puts telnet into
command mode, and then the command is Q for quit.

Yikes. Even less intuitive. I'd better save that one in my command file!
Thanks.

Well since telnet tells you when it first connects how to go into
command mode, it is not clear that "intuition" is needed.
"Escape character is '^]'"
is what telnet says once you connect.
And then you have to remember Q for Quit.

 

[Jasen Betts]

(that is hold down the control key while typing ]) puts telnet into
command mode, and then the command is Q for quit.

Yikes. Even less intuitive. I'd better save that one in my command file!
Thanks.

Well since telnet tells you when it first connects how to go into
command mode, it is not clear that "intuition" is needed.
"Escape character is '^]'"
is what telnet says once you connect.
And then you have to remember Q for Quit.

you don't even have to remeber that.
after ^] press enter and you get a prompt

telnet>

type help and press enter again