How to make a OPC Server "wide open"

I have a environment where security of OPC provided data is not really of concern. One station should read some data via OPC from another PC.

To simplify things with user accounts, domains, and all that other nasty security stuff, I like to make the OPC server component running on the "server" side as wide open as possible - means everybody with a windows machine who is able to ping that server should be able to read those provided data values with an appropriate client software.

Think of it as temperature and stocked amount of the coke vending machine - interesting to all, but not of security concern.

What do I need to do to rip such a security hole into the server ?
LVL 14
frankhelkAsked:
Who is Participating?
 
sfrancyCommented:
You can set your default DCOM permissions to add "Everyone" for both the launch and access permissioins.  Everyone does not mean anyone though.  This will work if the user can authenticate against your OPC server, meaning that user account must be recognized by the server.  If everything is in a domain, then you won't have a problem.  If you are using workgroups, then the user accounts of your clients must also exist on your server with the same passwords.

It is usually good to start this way (wide open), but after you have things working, you should refine your security to only the users who need access.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.