Re: Looking for view containing printer IP addresses

The original poster's real problem is that one set of experts is trying to figure away to communicate with another set of experts. That is, ExpertsA are dynamically looking to determine the IP Address of specific printers, as assigned by ExpertsB. That wheel has been invented. For this problem its called DNS. The DNS specifies the IP Address attached to a specific name. Standard stuff, easily configurable, understood by everyone involved. Why would anyone look to invent some new poorly understood solution? (I say poorly understood because its pretty clear from the various postings.)

200 lines of text?!?! Good grief!! I had no idea you would append that many lines to one of your responses, Chuck. In the future I will check your replies and remove the extraneous lines for you. Sorry; please accept my apologies.



On 7/17/2016 8:29 AM, CRPence wrote:

On 16-Jul-2016 21:56 -0500, Booth Martin wrote:

On 7/16/2016 6:06 PM, CRPence wrote:

<<SNIPped ~200 lines of text>>

What is the objection to using a DNS?

If that question is directed to me, well, I have no "objection to
using a DNS". Even if that inquiry as reply was directed to Troy, I
have no idea how that question assists or is in any way helpful to
progress the topic.? To what of those ~200 lines of text might that
question be applicable? I do not recall there were any concerns
expressed in that text
[http://archive.midrange.com/midrange-l/201607/msg00297.html], nor in
the Subject line, that would\could be resolved by the use of a DNS.
Perhaps clarification is of some value, for how, specifically, a DNS
would assist with [the issue being discussed in] this topic.?