|
midrange.com
Kenneth,
The fact that CA/400 uses DNS when available is not a fluke to CA400 but a
feature of TCP/IP networks setup using DNS. When doing an initial eval, you
would have caught the problem, had your network folks (or who ever) add your
/400 entry into DNS and your done. Now, when you go to the desktops, you
should have in your install script to check to verify you can ping
youras400.domain.com and if it fails, your user needs to be setup using DNS.
John
>>> "Graap, Ken" <keg@exchange.gasco.com> 03/15 10:51 AM >>>
Your have describe the problem!
The DNS resolution is performed "During Configuration". Then a hard coded IP
address is placed into the CA/400 configuration instead of a system name.
If the host system's IP address changes I still have to revisit each PC and
"reconfigure CA/400".
Why can't CA/400 store a "system name" instead of an IP address in it's
configuration and then resolve the IP address during the connection attempt?
If it did this then it wouldn't matter if the host system's IP address was
changed or not, CA/400 would still be able to find the system via DNS....
Kenneth
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
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.
