RE: Aspen and WP70s

2001-07-11 Thread John Miller

Jim,
Try installing both the security client and server programs on the 70, then
set the ADSA Directory server to localhost.  Because of our network topology
that's what I had to do since my Aspen server is in its own workgroup and
all of the process engineers are on the main company domain.
Good luck with it,
John Miller
Hunt Refining Company
1855 Fairlawn Road
Tuscaloosa, AL 35401
voice:  205.391.3345
fax:  205.345.8769
[EMAIL PROTECTED]

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 9:04 AM
To: Foxboro DCS Mail List
Subject: Aspen and WP70s



We are trying to setup Aspen Tech's Process Explorer to run on 
a WP70.  Does anyone have experience with doing this?  Aspen 
security requires user Authentication via NT domain, and 
Foxboro only supports a workgroup setting. 

Any suggestions or experience tackling similar problems would 
be greatly appreciated. 

Jim
== 
Jim Murphy
Eli Lilly and Company
Phone: (317) 276-6859
Email: [EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with unsubscribe foxboro in the Subject. Or, send any mail to
[EMAIL PROTECTED]




RE: Aspen and WP70s

2001-07-11 Thread Johnson, Alex (Foxboro)

An except from my book. I hope it helps:

Windows NT
Preliminary Decisions
Before attaching a Windows NT based I/A Series AW or WP to a company
network, several decisions must be made:

*   Should the machine use the standard I/A Series Auto-login facility
or should each user login individually?
*   What services to they need from the network, e.g., access to
printers and file servers, individual e-mail?
*   Should the I/A Series machine to work as part of a domain within the
plant?

A domain-based solution is appropriate if individual user login is required
at the I/A Series workstations. If individual logins are not required, there
is probably no benefit to having the machine join the domain.


Workgroup Based Solutions
If they need access to network drives, the MapNetworks Drive option -
right mouse click on My Computer - can be used to access them. When user
of the machine tries to map the drive, the server will ask for a username
and password. The user name needs to include the user's domain, e.g.,
FOX_HOU\alex.johnson. 

After the password has been entered, access to the drive is transparent. 

If access to network printers is required, clicking on the
NetworkNeighborhood icon can lead to finding the desired printer. When the
domain that contains the printer is entered, the domain server will prompted
for a user name and password. Again, the user name must be entered with the
user's domain's name, e.g., FOX_HOU\alex.johnson. After that, access is
transparent.

If unque user logins are required, but it is not desired to be in a domain,
create a new user using standard techniques. Be sure that the new user
belongs to the same groups as the user 'fox'.

Use the I/A Series control panel and toggle auto login on and off. This will
cause the machine to reboot as the currently logged in user.


Domain Based Solutions
If a domain based solution is desired, the first step is to decide how
logins should be handled. 

The default behavior is to have the machine boot up completely as user fox.
If the default user 'fox' is to be retained, yet a domain is to be used, the
following must be done to have the machine boot up in a domain:

*   Open the Network control panel, 
*   Select Identification, 
*   Select Change, 
*   Pick Domain, 
*   Enter the Domain Name. 
*   If this machine isn't already part of the domain, and it won't be,
check Create a Computer Account in the Domain, and have your System
Administrator enter the required user name and password.  


Note: Be careful about this. The I/A Series software depends on all of the
machines being able to talk to each other. So, it defaults to having them
all in the same workgroup. If you change some machines, but not all, nothing
good will happen.  

If individual logins are required along with Domain membership, follow the
above steps and log in as that user.

Use the I/A Series control panel and toggle auto login on and off. This will
cause the machine to reboot as the currently logged in user.


Domain as Workgroup Based Solutions
Another alternative exists. In this case, the domain name is entered as the
workgroup name. In this configuration, the machines can see all domain
resources, but they cannot access them without a login. 

For example, mounting a drive will prompt for a username and password
belonging to the domain.

This is an interesting compromise because it allows the resources to be
accessed without having the machine join the domain.


Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 


-Original Message-
From:   [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent:   Tuesday, July 10, 2001 9:04 AM
To: Foxboro DCS Mail List
Subject:Aspen and WP70s


We are trying to setup Aspen Tech's Process Explorer to run on 
a WP70.  Does anyone have experience with doing this?  Aspen 
security requires user Authentication via NT domain, and 
Foxboro only supports a workgroup setting. 

Any suggestions or experience tackling similar problems would 
be greatly appreciated. 

Jim
== 
Jim Murphy
Eli Lilly and Company
Phone: (317) 276-6859
Email: [EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 

RE: Aspen and WP70s

2001-07-11 Thread Airhart, Chad M.

If you don't want to have to deal with the ADSA server problems you can
install version 2.5.1 or wait for version 4.0 which should have a supported
way around the ADSA server.

Chad Airhart
Senior Instrument, Electrical  Control Systems Engineer
Equistar Chemicals, LP.
Victoria, TX
Wk. (361) 572-2568
Pgr. (361) 270-2214 alpha messaging at  [EMAIL PROTECTED]
Fx. (361) 572-2541

 -Original Message-
 From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
 Sent: Tuesday, July 10, 2001 9:04 AM
 To:   Foxboro DCS Mail List
 Subject:  Aspen and WP70s
 
 
 We are trying to setup Aspen Tech's Process Explorer to run on 
 a WP70.  Does anyone have experience with doing this?  Aspen 
 security requires user Authentication via NT domain, and 
 Foxboro only supports a workgroup setting. 
 
 Any suggestions or experience tackling similar problems would 
 be greatly appreciated. 
 
 Jim
 == 
 Jim Murphy
 Eli Lilly and Company
 Phone: (317) 276-6859
 Email: [EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with unsubscribe foxboro in the Subject. Or, send any mail to
[EMAIL PROTECTED]