For those who are abit anxious, as we were, I recommend you consider using
Rconsole from NT-server resource kit;  it gives you a robust cmd.exe
environment (ie, you can even run "edit.com" the full-screen MS-DOS editor).


We now use it instead of SMS, etc... this is a video- & keyboard-memory
mapped, cmd-line session, uses full/normal NT credentials for login  ---
kinda like NT's version of secureTelnet.  I run "dsmc" instead of web-client
if net-response is a slow connection;  also, dsmcutil and all its functions.
This is "way kool"!!!  Only serious (?) drawback is you cannot do
remote-shutdown... you'll have that with the remote-admin that comes in
Win2k-Server.

There are several (at least 4 in the NT reskits) solutions to getting
Telnet-like connection, this seems to be the *best* as it does not just
re-direct stdin/stdout, *and* uses current login credentials -- so security
risk is nil, other than normal NT risk.  The service allows up to ten
simultaneous connections, although there are reported problems when you
reach the 10th session... so, 1st nine work great!



Don France
Technical Architect, P.A.C.E.
EDS-Ph:  (707) 226-0640
Bus-Ph:   (408) 829-4611


> -----Original Message-----
> From: Matthew Glanville [mailto:matthew.glanville AT KODAK DOT COM]
> Sent: Tuesday, December 21, 1999 12:56 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Windows NT Client and PcAnywhere
>
>
> Jeff,
>   We have seen this problem on a few NT servers with
> PCAnywhere as well.
>
> Client 3.1.0.6 and 3.1.0.7.  Server 3.1.2.40 on Solaris 2.6
>
> The solution, dont use PC Anwywhere.
>
> This was acceptable to the NT folks because on the servers
> that had this
> problem, they do not
> do any restores.
>
> I too am not utilizing the Web client for the same reasons.  Hopefully
> when we migrate
> to TSM 3.7.x we will be using it.
>
> Jeff Connor wrote:
> >
> > Has anyone over noticed strange behavior when using
> PCAnywhere and the ADSM
> > Windows NT GUI
> >  backup client? We have experienced this problem where, if
> we don't keep moving
> > the mouse once an a while,
> >  the backup seems to freeze in a sendw state.  At first I
> thought PCAnywhere was
> > not detecting changes on
> >  the screen and the refreshed window would appear when you
> moved the mouse.
> > Today we started a restore
> > and walked away. An hour later the session had been in
> sendw status and hardly
> > any data was transfered.
> > As soon as we moved the mouse we could see the session
> start running from the
> > admin client. No prompt
> > from ADSM was displayed on the client like, do you want to
> replace files, etc.
> > The session just seemed to
> > be frozen. Wierd eh?  Anyone else using PCAnywhere
> experienced anything like
> > this and if so what did you
> > do to fix it? We are running ADSM NT client level 3.1.0.6
> with ADSM for MVS
> > V3.1.2.40. I also realize that
> > using the web client is an alternative but we didn't use it
> because there is a
> > bug at 3 1.0.6 with restoring an
> > entire inactive directory and all its files by clicking the
> selection box next
> > to the directory.
> >
> > Thanks
> > Jeff Connor
> > Niagara Mohawk Power Corp
>
> --
> matthew.glanville AT kodak DOT com
> (716) 477-9371
>