Re: Devices created automatically

depending on version of Synapse or Client Access, telnet is how those
products work.
CA Express is using telnet. If Synapse is a true tcp-ip product, it's
telnet.
Now in this attempt experienced this morning, even windows, going to "run"
and typing
"telnet xxx.xxx.xxx.xxx" will run a telnet.
jim

----- Original Message -----
From: "Chuck Lewis" <clewis@iquest.net>
To: <midrange-l@midrange.com>
Sent: Tuesday, April 02, 2002 10:55 AM
Subject: RE: Devices created automatically


> Jim,
>
> Sorry for this question, but want to be clear on what you are saying :-)
>
> I am assuming that an IP address from the person TELNETting in would show
> here as a Remote Address ?
>
> We are a private frame relay network and I do have some folks showing here
> but I know that they are "local" IP addresses...
>
> We attach PC's via TCP/IP and Synapse and I wonder why some of these (5
out
> of a TON) are showing here ? I know at least 2 of these users can barely
use
> a PC (I don't mean that as rude as it sounds !) and there is no WAY they
> would be doing Telnet (?)
>
> Chuck
>
> -----Original Message-----
> Jim Franz
>
> someone is using telnet to your 400, and the qautovrt is creating devices
> check system value QAUTOVRT.
> If you already have devices created that you need, count them up, and set
> this
> value so that no more are created.
> definitely not *nomax
> even though QUIT not a valid user id, os400 has to give a valid device so
> sign on attempt can be made
>
> The NETSTAT cmd & option 3 should show ip address of attempt
>
> jim
>
> (this may be innocent - user not knowing what to do) or a hack attempt
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>