Can a print server be hung right off of a router?

I'm thinking I many have to connect physically direct to my print server
first to make sure it's IP address is fixed/static (been a while since I
used my print server). I'm guessing this is a common practice thing but
I was looking for a confirmation.

Thanks

Net Resident wrote:

> I'm thinking I many have to connect physically direct to my print server
> first to make sure it's IP address is fixed/static (been a while since I
> used my print server). I'm guessing this is a common practice thing but
> I was looking for a confirmation.
>

WTF???

Perhaps if you asked a coherent question, we might be able to help you.

--

Fundamentalism is fundamentally wrong.

To reply to this message, replace everything to the left of "@" with
james.knott.

On Sun, 11 Jan 2004 16:18:22 GMT, Net Resident <(E-Mail Removed)> wrote:
> I'm thinking I many have to connect physically direct to my print server
> first to make sure it's IP address is fixed/static (been a while since I
> used my print server). I'm guessing this is a common practice thing but
> I was looking for a confirmation.

What print server mfr/model? Many have some way to print their config to
a connected printer. For example that is how I discovered that a
JetDirect, thought to be faulty, was actually hard coded with a 192.186..
IP (digits transposed). I just had to temporarily assign my nic an IP or
alias in that range to configure it.

Otherwise it may have a MAC address on it or coded into its serial number
that could allow you to manually add a local arp entry to associate an IP
with it (see -s in man arp, where 'hostname' can be an IP).

--
David Efflandt - All spam ignored http://www.de-srv.com/

David Efflandt wrote:
> On Sun, 11 Jan 2004 16:18:22 GMT, Net Resident <(E-Mail Removed)>
> wrote:
> > I'm thinking I many have to connect physically direct to my print
> > server first to make sure it's IP address is fixed/static (been a
> > while since I used my print server). I'm guessing this is a common
> > practice thing but I was looking for a confirmation.
>
> What print server mfr/model? Many have some way to print their
> config to a connected printer. For example that is how I discovered
> that a JetDirect, thought to be faulty, was actually hard coded with
> a 192.186.. IP (digits transposed). I just had to temporarily assign
> my nic an IP or alias in that range to configure it.
>
> Otherwise it may have a MAC address on it or coded into its serial
> number that could allow you to manually add a local arp entry to
> associate an IP with it (see -s in man arp, where 'hostname' can be
> an IP).

I think I can hang it off the router, it turns out the Netgear PS110
does have a MAC addy printed on the bottom. Did some googling and pulled
up some nice info. Just too tired to fiddle with it atm. Basically I was
trying to find out the issues before going out and getting a router.

http://www.linuxsa.org.au/mailing-list/2002-08/418.html

James Knott wrote:
> Net Resident wrote:
>
> > I'm thinking I many have to connect physically direct to my print
> > server first to make sure it's IP address is fixed/static (been a
> > while since I used my print server). I'm guessing this is a common
> > practice thing but I was looking for a confirmation.
> >
>
> WTF???
>
> Perhaps if you asked a coherent question, we might be able to help
> you.

Yeah sorry, I could have put that better.

Net Resident wrote:

> I'm thinking I many have to connect physically direct to my print server
> first to make sure it's IP address is fixed/static (been a while since I
> used my print server). I'm guessing this is a common practice thing but
> I was looking for a confirmation.
>
> Thanks

I guess you could bolt it right on the side. Just be carefull drilling the
holes. :P

> I'm thinking I many have to connect physically direct to my print server
> first to make sure it's IP address is fixed/static (been a while since I
> used my print server). I'm guessing this is a common practice thing but
> I was looking for a confirmation.

Yes, you should be able to attach your print server directly to your router
without an intermediate hub or switch, although you might have to use a
crossover cable. Whether doing that is the best choice would, of course,
depend on the situation, so you'll have to make that decision.

steve

Net Resident <(E-Mail Removed)> wrote:
> I'm thinking I many have to connect physically direct to my print server
> first to make sure it's IP address is fixed/static (been a while since I
> used my print server). I'm guessing this is a common practice thing but
> I was looking for a confirmation.

I'm having difficulty understanding what you're trying to say, so tell
me if I'm on the right track.

You have a router (I gathered that from your subject), and a printer.

I shall make some assumptions (please indicate if they are wrong)

* The printer is attached to a printer server (possibly embedded in the
printer itself).

* By attaching it to your router, you mean "can I hang an ethernet
printer server on one interface of a router." In which case, the
answer would be "Yes, certainly, but if you don't connect a switch,
you need to use a crossover cable"


If I have you right, you want to know how to query the printer so you
can find out its configuration, correct?

If that's the case, you've ommitted some important information.

* What is the Make/Model of the printer

* Does it have its embedded printer controller (does an ethernet cable
plug straight into it.

If it's not embedded, what is the Make/Model of the print controller.


Let's assume that its a Laser printer with an embedded printer
controller, say an HP LaserJet 2100L, a particularly horrid piece of
work because it doesn't have an LCD display.

If that's the case, a test page may print out more information,
otherwise, there are more possibilities.

Some printers (the 2100L does) have an embedded web server. Surf to the
address and you should be able to see the configuration.

Many printers have SNMP capabilities, you could query those, but only if
you know what you're looking for (you will need the correct MIB to find
anything interesting, although a Linux program called npadmin is
moderately useful).


If you don't know what the IP address is, then that's a bit harder. You
could try a broadcast ping, but most devices don't answer to those
(actually, Linux is the only OS I've seen exhibit that behaivour (mind
you, I've seen inside the guts of a very expensive printer controller
that runs Linux ;^)

ping -c 2 -b 255.255.255.255
ping -c 2 -b <subnet_broadcast_address>

If you start tcpdump and then restart the printer, you might see some
bootp packets, which would indicate that its configuring via DHCP. You
could write the packet capture to a file (tcpdump -w) and look at it
more closely with ethereal (ethereal /path/to/capturefile) to see what
address it was given.

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

Steve Wolfe wrote:

>> I'm thinking I many have to connect physically direct to my print server
>> first to make sure it's IP address is fixed/static (been a while since I
>> used my print server). I'm guessing this is a common practice thing but
>> I was looking for a confirmation.
>
> Yes, you should be able to attach your print server directly to your
> router
> without an intermediate hub or switch, although you might have to use a
> crossover cable. Whether doing that is the best choice would, of course,
> depend on the situation, so you'll have to make that decision.
>
> steve

Thanks, I'll keep that in mind. I have a custom made crossover test cable I
can throw it to test if the need arises.

Cameron Kerr wrote:

> Net Resident <(E-Mail Removed)> wrote:
>> I'm thinking I many have to connect physically direct to my print server
>> first to make sure it's IP address is fixed/static (been a while since I
>> used my print server). I'm guessing this is a common practice thing but
>> I was looking for a confirmation.
>
> I'm having difficulty understanding what you're trying to say, so tell
> me if I'm on the right track.
>
> You have a router (I gathered that from your subject), and a printer.
>
> I shall make some assumptions (please indicate if they are wrong)
>
> * The printer is attached to a printer server (possibly embedded in the
> printer itself).
>
> * By attaching it to your router, you mean "can I hang an ethernet
> printer server on one interface of a router." In which case, the
> answer would be "Yes, certainly, but if you don't connect a switch,
> you need to use a crossover cable"

OK thanks, I'll be mindful of that when testing.


> If I have you right, you want to know how to query the printer so you
> can find out its configuration, correct?

Yep, just haven't used it in a while. I plan to set it up temporary to the
computer to check data settings and function.


> If that's the case, you've ommitted some important information.
>
> * What is the Make/Model of the printer

HP Laserjet 6MP


> * Does it have its embedded printer controller (does an ethernet cable
> plug straight into it.

Nope, thats why I already have a print server.


> If it's not embedded, what is the Make/Model of the print controller.

Netgear PS110 (handles two printers)


> Let's assume that its a Laser printer with an embedded printer
> controller, say an HP LaserJet 2100L, a particularly horrid piece of
> work because it doesn't have an LCD display.
>
> If that's the case, a test page may print out more information,
> otherwise, there are more possibilities.
>
> Some printers (the 2100L does) have an embedded web server. Surf to the
> address and you should be able to see the configuration.
>
> Many printers have SNMP capabilities, you could query those, but only if
> you know what you're looking for (you will need the correct MIB to find
> anything interesting, although a Linux program called npadmin is
> moderately useful).
>
>
> If you don't know what the IP address is, then that's a bit harder. You
> could try a broadcast ping, but most devices don't answer to those
> (actually, Linux is the only OS I've seen exhibit that behaivour (mind
> you, I've seen inside the guts of a very expensive printer controller
> that runs Linux ;^)
>
> ping -c 2 -b 255.255.255.255
> ping -c 2 -b <subnet_broadcast_address>
>
> If you start tcpdump and then restart the printer, you might see some
> bootp packets, which would indicate that its configuring via DHCP. You
> could write the packet capture to a file (tcpdump -w) and look at it
> more closely with ethereal (ethereal /path/to/capturefile) to see what
> address it was given.
>

Thanks for taking the time to reply. That is interesting info that may come
in handy in the future =)