RE: All printers and their IP Addresses -- MIDRANGE-L

Or they install a new door in receiving between doors 1 and 2 :)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: Tuesday, June 11, 2013 1:23 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: All printers and their IP Addresses

I always named them, and used static IP's in DHCP, but had the same naming issue.

IBM example name: RcvDock1
Windows example name: The_Printer_At_The_Receiving_Dock_3rd_Door_Left_Side

Worse was when the network guys decided to name devices by division_dept.
Worked great until the first divisional reorg.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Tuesday, June 11, 2013 10:08 AM
To: Midrange Systems Technical Discussion
Subject: RE: All printers and their IP Addresses

That is also true - and today I learned something. That you can use a name on a remote outq. We have always used the IP but the IP was a static assigned DHCP address so never changes. Now if I could only get the server group to name printers with 10 character names. Then the OUTQ name and DNS name and the Windows queue name would all match :)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, June 11, 2013 1:03 PM
To: Midrange Systems Technical Discussion
Subject: Re: All printers and their IP Addresses

True, but even so, if you hard-code the IP address into your DEVD or RMTOUTQ, you've defeated the point behind using DHCP in the first place.

On 6/11/2013 11:52 AM, Mike Cunningham wrote:

DHCP does not need to mean dynamic. DHCP can assign a static based in
MAC

address. So the printer would always get the same IP every time it boots.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, June 11, 2013 12:49 PM
To: Midrange Systems Technical Discussion
Subject: Re: All printers and their IP Addresses

I've done many printers using DHCP -- never had a problem in 20+ years.

It's obviously important that if you use this scenario, you use DDNS
to update the host name to point to the proper IP address, and that
you don't ever hard-code the IP address into anything (which, you
shouldn't ever do, anyway... that would be piss-poor administration
if you hard coded an IP address into anything aside from a DNS
server.)

The DEVD or RMTOUTQ needs to point to the host name, of course, in DNS

rather than the IP address.

On 6/11/2013 10:48 AM, rob@xxxxxxxxx wrote:

I may be off base here, but do printers ever use DHCP? If so,
wouldn't their IP address be rather, well, dynamic?

Why is it important to know their IP address? I could imagine the
network admin wanting to segregate printers on to their own subnet,
or only allow the printer subnet to do certain things. Like I think
some barcode printers used ftp to download labels and someone may
want to only allow ftp from some particular addresses.

Rob Berendt

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.