In the near term, we will be moving from an onsite IBM i to one in the
cloud. Our onsite IBM i has a 192.168.x.x address. The cloud system will
have a 10.x.x.x address.
We have an internal DNS entry that points myibmi.dilgardfoods.local to the
192.168.x.x address. When we make the move I will change that DNS entry to
point to the 10.x.x.x address.
In preparation for this I have gone around to every desktop with ACS and
made sure that all defined sessions (.hod files) are pointing to
myibmi.dilgardfoods,local so that when we make the move, I don't need to go
around to every desktop. (And that myibmi.dilgardfoods.local is defined in
the System Configurations.)
For some reason, on my desktop, the Destination Address within the session
definitions keep getting changed to a hardcoded 192.168.x.x address. I
have changed them /repeatedly/ to myibmi.dilgardfoods.local and they keep
getting changed back to the IP address. I have not determined exactly when
this is happening.
I have looked at 2 other desktops so far and this is /not/ happening at
those desktops. Their session definitions are staying at
myibmi.dilgardfoods.local. I do not see any difference in the System
Configuration from those desktops to mine.
Any idea what might be causing this?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.