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


  • Subject: RE: CA400 on Win/NT - setting up connections
  • From: Mark Welte <MWelte@xxxxxxxx>
  • Date: Mon, 10 Nov 1997 07:43:19 -0500

David,

The Client Access connection information is stored in an area called 
the registry. The settings in the registry can "travel" with the user 
to each PC that the user log into. This is call roaming profiles. 
There was a problem with using CA/NT and roaming profiles on service 
pack 2 of NT 4.0 but that was fixed with service pack 3 of NT 4.0. If 
you want to look at the registry, run the regedit command. WARNING: 
CHANGING SETTINGS IN THE REGISTRY CAN BE HAZARDOUS TO YOUR HEATH.

This is a really slick way to set users up if each NT workstation is 
configured with similar software installed locally on the workstation. 
The optimum is to have all of the software stored on the NT server. We 
have found, however, that CA/NT works much better if it is installed 
locally on each workstation.

To setup each user for CA/NT, our network administrator inserted the 
registry settings into each user's profile when the user was setup.

Mark


----------
From:  Kahn, David[SMTP:KAHN@tengizchevroil.com]
Sent:  Monday, November 10, 1997 11:45 AM
To:  'MIDRANGE list (conference)'
Subject:  CA400 on Win/NT - setting up connections

Our LAN is switching over to the dreaded Windows NT. We are using 
Client
Access over TCP/IP for our AS/400. The configuration is being stored 
on
the local hard drive of each PC. When a PC is initially configured
everything works fine. However, when a different user then logs on to
the same PC the message CWBEM0002 pops up. Text is "Could not find
system xxxxxx in CA/400's current AS/400 environment. Configure 
system
and retry the request." We then have to go back through the 
connection
wizard and from then on everything is OK for that user at that PC. 
This
has to be repeated every time any user logs on to any PC for the 
first
time.

Is there a way to set up the connections so that once a PC has been
configured the connection will hold good for every user who logs on?
Secondly, has anyone got a clue as to exactly where the connection
information is being stored?

Any help would be much appreciated.

Dave Kahn, TCO, Kazakstan
=========

kahn@tengizchevroil.com   (to November 25)
dkahn@cix.compulink.co.uk (from November 26)

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.