RE: Client access session

["Allen, Stuart" <sallen@xxxxxxxxxxxx>]

Me too!

Stuart


> -----Original Message-----
> From: John Bussert [SMTP:jbussert@stecnet.com]
> Sent: Friday, March 05, 1999 2:59 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: Client access session
> 
> If you don't mind, I would love to see your *.ws file.  It may give us
> some
> other ideas too.
> 
> Thanks,
> 
> john
> 
> > -----Original Message-----
> > From: owner-midrange-l@midrange.com
> > [mailto:owner-midrange-l@midrange.com]On Behalf Of Eric Sundell PMI
> > Sent: Thursday, March 04, 1999 1:08 PM
> > To: "John Bussert" ; "Midrange-L" ; MIDRANGE-L@midrange.com
> > Subject: Re:Client access session
> >
> >
> > If it is happening only on one PC then it sounds like the PCSWS.EXE or
> one
> > of
> > it's components are corrupted try Uninstall CA400 and reinstalling it,
> > including
> > the newest service pack. Then remake your connection to your
> > AS400 including
> > a
> > new *.WS file, we had the same problem when we installed 3.2 on
> > some of our
> > PC,
> > I could not get the WS file to give me a green screen, I finally had to
> > write
> > one my self, if you wish I could send it to you, I made a few
> > refinements to
> > it
> > as well, like the name of our system on the title bar, a keyboard that
> > mimics
> > the RUMBA keyboard map that we had before, etc.-EDS
> >
> > ____________________Reply Separator____________________
> > Subject:    Client access session
> > Author: "John Bussert" [SMTP:jbussert@stecnet.com]
> > Date:       3/3/99 3:11 PM
> >
> > I have a client that is running 3.2.  Using TCP/IP we can connect
> through
> > dialup to a LAN.  That works fine.  We can connect to the 400 just fine,
> > transfer files, but we cannot get a 5250 session or graphical
> > session going.
> > We have other PC's dialing and they are fine.  Any ideas as to where to
> > look?
> >
> > Thanks
> >
> > john
> >
> > John Bussert
> > jbussert@stecnet.com
> > Swift Technologies, Inc.
> > 847-289-8339
> > 847-289-8939 fax
> >
> > +---
> > | 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
> > +---
> > +---
> > | 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
> > +---
> >
> 
> +---
> | 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
> +---
+---
| 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
+---