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


  1.  Home
  2. MIDRANGE-L
  3. April 2020

Re: Telnet came from where

Ah, now I understand. Force the WSID on the Target system to the be the same as the WSID on the Source system. Hmm, that is a definite possibility. The only snag I can see is if the Source WSID is already in use on the Target system.

Thanks for the idea.

~TA~



On 4/29/2020 2:06 PM, Stefan Tageson wrote:
Correct, but if the device name is the same on the target system you know what it is on source system .....


Best regards,

Stefan Tageson
TietoEVRY
mobile +46 732 369934


Sensitivity: Internal

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of ~TA~
Sent: den 29 april 2020 21:01
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Telnet came from where

This would set the device name on the TARGET system.
What I need to know is the workstation ID of the session that initiated the telnet on the SOURCE system.

Thanks.

~TA~



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.