Troubleshoot InetDriver (Enterprise) connection
At times two or more InetSupervisor workstations need to communicate with each other to exchange data. For sake of this conversation we will label "Enterprise" the computer you are running the InetDriver on. The other computers we will call "Remote Rhea".
It happens often that you can import available points using the InetDriver Config but the actual driver does not read valid values, but instead it throws many security exceptions into the InetDriver log file. There are two potential issues:
- The remote Rheas are missing crossdomain files.
- Computers are not setup to authenticate with each other using Microsoft security.
Fix for item 1:
Place "clientaccesspolicy.xml" and the "crossdomain.xml" files in the "C:\inetpub\wwwroot" directory of the remote InetSupervisor or a Rhea. These files are available at the InetSupervisor download area.
Fix for item 2:
We have two options here: a) make both computers authenticate using Microsoft security, or b) disable the authentication.
- Make sure that the User Name and Password under which you are running on the Enterprise is the same (the account exists) as on the remote Rhea. If the Enterprise is running on a Vista machine we noticed that that's all that you need to do. Sometimes you need to put all computer on the same Domain and make them part of the Active Directory.
- To disable the authentication, therefore exposing the computer to potential attacks you need to take two steps.
- At the Remote Rheas you open the "C:\inetpub\wwwroot\hmi\web.config" in a text editor and search (ctrl + f) for "security mode". You should be able to find two or three instances of <security mode ="Message">. Change the mode to None as such: <security mode="None">
- At the Enterprise you open the "C:\LonWorks\Apps\Qci\InetDriver\InetDriver.exe.config" in a text editor and search for "security mode". You should be able to find two or three instances of <security mode ="Message">. Change the mode to None as such: <security mode="None">
If you want to refer to any online resources you can google for security mode ="Message" WCF
Email us with feedback. We would like to hear about your implementation.

0 Comments:
Post a Comment
Links to this post:
Create a Link
<< Home