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



I believe that you will find the Telnet Initialization Exit Point to not be sufficient. First, the telnet user may not pass a user profile name when initializing the session. Second, even if they do pass a user profile name they can pass/initialize with a "safe" ID, signoff once allowed access to the system, and then signon on (with no new initialization) with the "not considered safe" ID.

Bruce Vining


Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> wrote:
Assuming these are green screen applications, you can add a telnet exit
program that retrieves the ip address of the workstation. You should be
able to determine from that whether the request is coming from inside or
outside and compare the user with the authorized user list. The return
code of the exit program determines whether the session is allowed.

I have a working telnet exit program that I'd be happy to share with you
off-list.

John Allen wrote:
Thanks for the quick reply,

They want this to be real easy thing to do (disable/enable)
because it will be done quite often, don't want to
continually have to go into Active Directory to make the
changes if there is an easier way.

We do not want to disable User profile because they are
still allowed to use System i while in the office, just want
to stop the remote access.

My initial thought was some type of Subfile program that
displays all of the User Profiles and set a flag Allow
Remote Access Y/N.

But once I have the User Profile and the flag value I guess
I could write a program to run as there initial program and
if they are attempting remote access end the job.

Not sure how I can tell if they are coming in remotely
versus locally (in the office)

I was also hoping I did not have to write a program if
someone else already has, or if there is an inexpensive
solution available.

Thanks
For your suggestion about Active Directory, I will have to
see if that is possible solution

John




-----Original Message-----
From: David Wright [mailto:opendave@xxxxxxxxx]
Sent: Saturday, November 08, 2008 12:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: How can I easily enable/disable remote access
by User

What sort of VPN hardware are you using?

Some grant/deny VPN access through Active Directory and some
through
internal user lists.

But if access to the i is the only thing you need to
restrict, couldn't you
just enable/disable user profiles on the i?

On Sat, Nov 8, 2008 at 9:03 AM, John Allen
wrote:

We have some employees that access our System i remotely
(through a VPN)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.