×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Sometimes snipping doesn't help. I had to go back to deleted and sent
email to find out why address he was changing from.
I see now that he had a 172.16.* number. And you are saying that is a
known private range and it should be ok. Perhaps you are right. But
maybe they are like us and they will be assigning various locations
various ranges of numbers and want everyone to toe the line.
I've lost this battle myself. Having to change the IP addresses on all
your servers to fill the whim of a network consultant bites. It gets so
bad that I have to change from 10.10.1.x to 10.16.y.z for something that's
staying in the same room. Sometimes it's change from 10.10.1.x to
10.10.1.y just to free up an octet of numbers for some other purpose. When
it got to the point that him and I were about to argue like my kids over
whose turn it is to do the dishes I backed off and bit the bullet.
Sometimes it's better to give on some details as to not to appear
inflexible.
I have a coworker with 20+ years of service whose last day was today. He
has 7 kids of which 3 of them are in college. Sometimes it's best to just
try and get along.
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
