Re: Client Access Sessions taking forever to bring up Signon Scre en

> It has been suggested that it has something to do with reverse DNS Lookup
>  and that I should tell the 400 what the addresses are.  The problem with
>  that is that they are dynamically assigned by the NT server and we are
>  talking at least 50 users.  Unless there is a way to generically tell the
>  400 about a range of addresses.

NT usage of generic addresses is the DEFAULT,

There are ways to have NT assign addresses that are always the same for some 
device or way into the 400.  I am not an NT person.  Our NT person found out 
on a 400 forum how to do this - I do not know the technique he used or which 
forum ... I had suggested a bunch that he might want to use & he also found 
some others on his own.

When I look at DSPLOG on NT sessions connecting to our 400, they come with a 
unique IP address, the device session name, the end user sign on, and QUSER 
is also present.

Our devices are identified by NT to 400 as 3 initials of end user name, then 
digits of session # on the device run by person with those initials,

We had to do this because it was the expedient way to talk to BPCS which uses 
sign-on session id for work areas of applications ... users needed to be able 
to get into the same work area in concurrent sessions & not be conflicting 
with other users whose QPDAV00 was the same prefix with last unique digits 
stripped off because of the application characters.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---