Re: [foxboro] Remote DM Using DHCP- Fixed

Andreas,

Here is what I did to get DHCP working. Assuming, of course you have a =
DHCP server setup.  We use Novell in this case but it should be the same =
for MicroSoft.

1.  Setup the /etc/resolv.conf file with the following entries.  I had to =
create the file

    domain escocompany.com  =20
    nameserver 192.168.1.1  =20

2.  Modify the /etc/nsswitch.conf=20
     from:  hosts:      files
     to:       hosts:      files dns=20

Basically add 'dns' (no quotes) after the host: files entry in the =
nsswitch.conf file.


3.  Setup the dmcfg file.  I had to use lower case for the PC name (that =
was the forehead slap part).  That's the PC name in the General tab of the =
PC System Properties.  The friendly name of the PC. =20
The itadmin entry in the SCREEN line of the dmcfg file is the key.  That =
sets up the users that are allowed to access the View_Client which later =
on in the file is assigned a display manager.  In this case WPDM02 and =
WPDM03.
 The cool thing about this is that the friendly PC name shows up in the =
eXceed Finger utility if you use that and also in the DM_Usage display.

dmcfg file:

SCREEN View_Client  itadmin
#--------------------------------------------------------------------------=
--
# TYPE <type>    <window attributes>  <class>         <environment>
#
TYPE  Operator          -              B               Proc_Op_Env
TYPE  AuxillaryOper     QLRSM          O               Proc_Op_Env
TYPE  RemoteOperator    -              O               Proc_Op_Env
TYPE  Engineer          -              E               Proc_Eng_Env
TYPE  View_Only         -              V               Remote_Env
#--------------------------------------------------------------------------=
--
#
# AMTYPE <type>    <class>         <environment>
#
AMTYPE  Operator          B               Proc_Op_Env
AMTYPE  AuxillaryOper     O               Proc_Op_Env
AMTYPE  RemoteOperator    O               Proc_Op_Env
AMTYPE  Engineer          E               Proc_Eng_Env
AMTYPE  View_Alarms       V               Remote_Env
#--------------------------------------------------------------------------=
--
#
# NAME <lbug>      <dmname>       <dedicated monitor(s)>  <type>
#
NAME   WP0001       WP0001            .0            Operator
NAME   WP0001       WPDM01            -             Operator
NAME   WP0001       WPDM02            $View_Client  View_Only
NAME   WP0001       WPDM03            $View_Client  View_Only

end dmcfg file.

Rick Mol
ESCO Company
IT/Automation Admin.
231.727.6409
rdmol@xxxxxxxxxxxxxxx

>>> "Weiss, Andreas" <Andreas.Weiss@xxxxxxxxx> 3/19/2005 11:44:43 AM >>>
Hi,

would you be so kind to send me your dmcfg?

I would like to understand it better.

Regards,
Andreas
=20

-----Urspr=FCngliche Nachricht-----
Von: Rick Mol [mailto:rdmol@xxxxxxxxxxxxxxx]=20
Gesendet: Freitag, 18. M=E4rz 2005 19:50
An: foxboro@xxxxxxxxxxxxx=20
Betreff: Re: [foxboro] Remote DM Using DHCP- Fixed

Whap! That's the sound of a forehead slap.

The case for the entry in the dmcfg file needs to be all lower.  I had
used the case that was on the PC, mixed upper and lower.  Silly me.

Thanks to all those who replied.

Regards,


Rick Mol
ESCO Company
IT/Automation Admin.
231.727.6409
rdmol@xxxxxxxxxxxxxxx=20

>>> rdmol@xxxxxxxxxxxxxxx 3/18/2005 11:59:49 AM >>>
Greetings, All Wise and All Knowing List,

This topic has been beaten to death, I know, but I'm still having a
slight problem.

I need to change our PCs from fixed to dynamic IP addresses, and have
some of the PC connect to a dedicated DM.
The PC was able to connect to the appropriate DM when it had a fixed
address and an entry in the hosts file.

DHCP is setup on the network. The appropriate modifications have been
made to the WP, resolv.conf and nsswitch.conf files.
The WP can ping the machine by name.
The DM start method from the PC is default, log in as ia.

The PC is unable to connect with the dedicated DM.

Thoughts?

Regards,



Rick Mol
ESCO Company
IT/Automation Admin.
231.727.6409
rdmol@xxxxxxxxxxxxxxx=20
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys
Process
Systems (formerly The Foxboro Company). Use the info you obtain here
at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html=20

=20
foxboro mailing list:             http://www.freelists.org/list/foxboro=20

to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin=
=20

to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave=
=20

=20
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html=20
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro=20
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin=
=20
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave=
=20
=20
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: