Re: System name weirdness -- MIDRANGE-L

× 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.

Subject: Re: System name weirdness
From: Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>
Date: Tue, 6 Jul 2010 18:27:27 +0200
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Tue, Jul 6, 2010 at 17:41, James H. H. Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:

Can anybody think of a reason why the user would think the system name
was different from what the system itself reported?

Maybe the user is talking about the DNS Hostname of the system? (might
be visible in go tcpadm/12, but it does not have to be configured to
work that way).

Or the User is talking about the NetBIOS Hostname of the System
(configured in Netserver)

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.