Re: Fixed device names for incoming Telnet connections?

From: Wilm Boerhout (w.boerhoutOLD_at_PAINTplanet.nl)
Date: 10/06/03 

Date: Mon, 06 Oct 2003 18:23:26 +0200

labadie wrote:
> "Wilm Boerhout" <w.boerhoutOLD@PAINTplanet.nl> wrote in message
> news:blk26u$75e$1@reader08.wxs.nl...
>
>>Way back when, I used to think up solutions for customers on VMS
>>systems. Nowadays, I seem to be back in the field. For one of these
>>solutions, the following question:
>>
>>Can I tweak UCX to generate fixed TNAn: device names for incoming
>>connections based on, say, the IP address of the originating interface?
>>I used to do this for incoming LAT connections.
>>
>>If Yes to the above, can I have alternae controller names, in order to
>>generate TNBn: and TNCn: device names? SYSGEN CONNECT TNB0 /WHATEVER,
>>and of course specify the Whatever and anything else to tell the Telnet
>>server that for some IP addresses, TNBn: or TNCn: is to be used
>>
>>Wilm Boerhout
>>
>
> Hello
>
> I am not sure about what you want to achieve, but, you can do, for example
>
> $ telnet/create alpha1 23 6121
> this will create on node alpha1 a device tna6121
>
> When you have ended, you should do something similar to
> $ telnet/delete 6121
> to delete the device tna6121
>
> Look at
> $ telnet
> help create
>
> regards
>
> Gérard
>
>
I'm trying to extend the life of an 20 yr old application whose users
get part of the functionality based on terminal names (TXA3:) that is
looked up in a table. Table entries may be changed, but are restricted
to 4 characters.

Users logging in freely via Telnet, would eventually wind up getting
TNA10: as login device, and the application method would break.

So, creating the TNAn: is possible (provided n <> 0 I presume). How
could I force an incoming connection to attach to this particular device?

And, I need more than 9 devices. Is the assumption that I can create and
attach to TNBn: worth investigating?

I am also investigating other scenarios, involving logical names.
Assuming that physical device TXB$: is not present in the system, DEFINE
TXA4: as the login device.

Thnks,
Wilm

w.boerhoutOLD@PAINTplanet.nl
<remove OLD PAINT from address to reply>

Relevant Pages

  • Re: Cant connect to port 25 from another system
    ... port 25 and did a make to update sendmail.cf. ... restarted sendmail. ... When I attempt to telnet to port 25 the connection fails. ... on where outbound smtp connections are okay but smtp sessions ...
    (Fedora)
  • Re: Cant connect to port 25 from another system
    ... Maybe there is a strict definition on which connections ... I have sendmail running ... Both netstat and nmap confirm that the system *is* listening on port ... When I attempt to telnet to port 25 the connection fails. ...
    (Fedora)
  • Re: Moving to SMTP Email Connection
    ... I have now managed to get access via telnet, whilst connected to the router, by forwarding the port on the ISA server, so that at least now looks ok. ... I have set up one of my domains to have it's MX records adjusted at the ISP and connecting to that address also works now on telnet. ... My feeling at this point is that there may be two separate issues, one of getting into the network on port 25 from outside, and possibly an ISA one, though it's also possible that ISA is by default supposed to refuse connections from machines in the 'outer' network. ...
    (microsoft.public.windows.server.sbs)
  • Telnet connection closes immediately upon connecting
    ... I have a legacy application that I have running on a couple of RHEL AS ... servers that requires telnet connections. ...
    (RedHat)
  • Re: Data::Dumper for java
    ... network rules about which machines attach to which, ... connections as well.. ... debugging a problem without an adequate debugging harness. ... that you can attach a debugger. ...
    (comp.lang.java.programmer)